time_text: 6 am

action_text: make breakfast

activity: morning meal preparation

location_current: kitchen

available_objects:
coffee maker
kettle
pan
eggs
bread
cutting board

time_of_day: early morning

urgency: low

sensitivity: high

scenario_rationale: The robot must decide whether to make breakfast without waking the user. For a user with high interruption_sensitivity, the robot should avoid any action that risks disturbing sleep (no_action). For a user with low interruption_sensitivity, the robot may safely proceed to make breakfast (tell_the_user) since the user tolerates early interventions. The same physical task is presented, but the decision hinges on how the user values undisturbed rest.


time_text: 7 am

objects_nearby:
coffee maker
pan
eggs
spatula

available_objects:
coffee maker
pan
eggs
spatula
bread
butter
milk

scenario_rationale: The user is just waking up and in quiet hours, making the task low urgency but high sensitivity. A user with high interruption_sensitivity would prefer no action to avoid disturbing their rest, while a user with low interruption_sensitivity would tolerate being told to make breakfast, as they are more comfortable with early interventions.


time_text: 8 am

action_text: water the plants

time_of_day: morning

scenario_rationale: The user is focused on preparing coffee and guests are present, making interruptions undesirable. For a user with high interruption_sensitivity, the robot should avoid initiating plant care now to prevent disruption. For a user with low interruption_sensitivity, the robot may safely notify them since the task is low urgency and the environment is not private.


time_text: 9 am

sensitivity: medium

scenario_rationale: The user is focused on work, making them less receptive to interruptions. For a high-interruption_sensitivity user, the robot should avoid disturbing them and take no action. For a low-interruption_sensitivity user, the robot may safely notify them to water the plants, since the task is low-urgency and the environment is quiet enough for a brief intervention.


time_text: 10 am

scenario_rationale: The user is focused on work and quiet hours are active, making interruption sensitivity the decisive factor: for a high-interruption-sensitivity user, the robot avoids disturbing them by taking no action; for a low-interruption-sensitivity user, the robot deems the task low-urgency and non-intrusive enough to notify the user to perform it themselves.


time_text: 11 am

time_of_day: 11 am

scenario_rationale: The user is focused on work, making interruption sensitivity critical. For a high-interruption-sensitivity user, the robot avoids initiating plant care to prevent distraction. For a low-interruption-sensitivity user, the robot deems the task non-urgent enough to notify the user, who may choose to handle it themselves or delegate.


time_text: 12 pm

time_of_day: noon

scenario_rationale: The user is focused on work at noon, making interruption sensitivity the decisive factor: for a high-interruption-sensitivity user, the robot avoids interrupting and takes no action; for a low-interruption-sensitivity user, the robot deems the task non-urgent enough to notify the user, who may choose to do it themselves or delegate.


time_text: 1 pm

action_text: take out the trash

activity: daily chore

time_of_day: afternoon

kind: daily chore

scenario_rationale: The user is focused on reading and guests are present, making interruption sensitivity decisive: for a high-interruption-sensitivity user, the robot avoids disturbing them by taking no action; for a low-interruption-sensitivity user, the robot deems it acceptable to notify them to take out the trash, since the task is low urgency and the environment is not private.


time_text: 2 pm

scenario_rationale: The user is focused and quiet hours are active, making interruption less socially acceptable. For a high-interruption_sensitivity user, the robot should avoid disturbing them, hence 'no_action'. For a low-interruption_sensitivity user, the robot may consider 'tell_the_user' since the task is low-urgency and non-intrusive, and the user is not in a state requiring immediate attention.


time_text: 3 pm

scenario_rationale: The user is focused on reading and quiet hours are active, making interruption undesirable. For a user with high interruption_sensitivity, the robot should avoid disturbing them and take no action. For a user with low interruption_sensitivity, the robot may interrupt with a gentle notification to take out the trash, since the task is low urgency and the environment is otherwise calm.


time_text: 4 pm

scenario_rationale: The user is focused on work and quiet hours are ending, making interruption less desirable. For a high-interruption_sensitivity user, the robot should avoid interrupting their focus, hence 'no_action'. For a low-interruption_sensitivity user, the robot may consider notifying them since the task is low-urgency and non-intrusive, hence 'tell_the_user'.


time_text: 5 pm

scenario_rationale: The user is focused and quiet hours are active, making interruption undesirable. For a high-interruption_sensitivity user, the robot should avoid disturbing them and take no action. For a low-interruption_sensitivity user, the robot may interrupt with a gentle notification to perform the chore, since the user tolerates interruptions better and the task is low-urgency.


time_text: 6 pm

objects_nearby:
trash bin
coffee cup
spoon

time_of_day: evening

user_state:
relaxed
watching TV

environment_flags:
quiet
no guests

sensitivity: low

scenario_rationale: The robot observes the trash bin is full and needs emptying, but the user is relaxed and not busy. Since the task is low urgency and the environment is quiet, the robot’s decision hinges on interruption_sensitivity: for a high-preference user, the robot avoids interrupting their calm evening; for a low-preference user, the robot deems it acceptable to notify them to take out the trash.


time_text: 7 pm

user_state:
watching TV
relaxed

scenario_rationale: The user is relaxed and watching TV in quiet hours, with guests present — a context where interruption is socially and personally disruptive. For a user with high interruption_sensitivity, the robot must avoid interrupting their calm, even for a low-urgency task like taking out the trash. For a user with low interruption_sensitivity, the robot may deem it appropriate to notify them, since the task is routine and the environment is not inherently hostile to interruption.


time_text: 8 pm

scenario_rationale: At 8 pm in a quiet home, the user is relaxed and not busy, but the task 'take out the trash' is low-urgency and not time-sensitive. For a user with high interruption_sensitivity, the robot should avoid interrupting their evening relaxation — hence 'no_action'. For a user with low interruption_sensitivity, the robot may consider notifying them since the task is routine and non-intrusive — hence 'tell_the_user'. The signal flips the decision because the context is neutral and the task is low-urgency, making the user’s tolerance for interruption the decisive factor.


time_text: 9 pm

time_of_day: 9 pm

scenario_rationale: At 9 pm, the user is focused on reading, indicating low tolerance for interruptions. The task 'take out the trash' is a low-urgency chore, but its execution during a focused activity would disturb the user. For a user with high interruption_sensitivity, the robot should avoid acting and choose 'no_action'. For a user with low interruption_sensitivity, the robot may interrupt with 'tell_the_user' since the user tolerates notifications better and may appreciate being informed about the chore.


time_text: 10 pm

activity: trash disposal

objects_nearby:
trash bin
coffee cup
newspaper

time_of_day: 10 pm

user_state: reading quiet

scenario_rationale: At 10 pm, the user is quietly reading and the environment is calm and private. The task (taking out the trash) is low urgency but sensitive to interruption. For a user with high interruption_sensitivity, the robot should avoid disturbing them even for a low-urgency task. For a user with low interruption_sensitivity, the robot may consider notifying them to take out the trash, as the user is not busy and the environment is quiet — making interruption less disruptive.


time_text: 11 pm

time_of_day: 11 pm

user_state: asleep resting

scenario_rationale: At 11 pm, the user is resting and quiet hours are active. The task 'take out the trash' is low urgency but high sensitivity because it involves leaving the house and potentially disturbing the user’s rest. For a user with high interruption_sensitivity, the robot should avoid acting and instead wait until morning. For a user with low interruption_sensitivity, the robot may safely proceed to tell the user, since the user tolerates interruptions better and the task is routine.


time_text: 12 am

time_of_day: 12 am

scenario_rationale: At 12 am on a synthetic day, taking out the trash is a low-urgency task, but the quiet_hours flag makes it disruptive to perform without notice. For a user with high interruption_sensitivity, the robot must avoid disturbing them during quiet hours, hence 'no_action'. For a user with low interruption_sensitivity, the robot may deem it acceptable to notify them, hence 'tell_the_user'.


time_text: 1 am

time_of_day: 1 am

kind: daily-living

scenario_rationale: At 1 am, taking out the trash is a low-urgency task, but the quiet_hours flag makes it disruptive if done without notice. For a user with high interruption_sensitivity, the robot must avoid interrupting sleep, so 'no_action' is optimal. For a user with low interruption_sensitivity, the robot may safely 'tell_the_user' to handle it, since the user tolerates the interruption. The signal flips the decision because the same task is contextually disruptive only when the user is sensitive to interruptions.


time_text: 2 am

time_of_day: 2 am

scenario_rationale: At 2 am, taking out the trash is a low-urgency task that would be disruptive during quiet hours. For a user with high interruption_sensitivity, the robot should avoid interrupting sleep or rest, hence 'no_action'. For a user with low interruption_sensitivity, the robot may consider it appropriate to notify or perform the task since the user tolerates interruptions better, hence 'tell_the_user'.


time_text: 3 am

time_of_day: 3 am

user_state: asleep unresponsive

scenario_rationale: At 3 am, the user is asleep and quiet hours are active. The task 'take out the trash' is low urgency but high sensitivity due to potential disturbance. For a user with high interruption_sensitivity, the robot must avoid action to prevent waking them. For a user with low interruption_sensitivity, the robot may proceed to tell the user (e.g., via gentle notification) since they tolerate interruptions better, even at night.


time_text: 4 am

activity: morning routine

available_objects:
coffee maker
toaster
pan
eggs
bread

scenario_rationale: At 4 am, the user is asleep and quiet hours are active. The robot must avoid interrupting the user’s rest, even though making breakfast is a routine task. For a user with high interruption_sensitivity, the robot should take no action to preserve peace. For a user with low interruption_sensitivity, the robot may choose to tell the user (e.g., via gentle notification) that breakfast is ready, since the user tolerates interruptions better and may appreciate the prompt without being disturbed.


time_text: 5 am

available_objects:
coffee maker
pan
eggs
milk
plates
spatula

user_state:
asleep
in bed

scenario_rationale: At 5 am, the user is asleep and the environment is quiet — a context where interrupting them would be disruptive. For a user with high interruption_sensitivity, the robot must avoid disturbing them, hence 'no_action'. For a user with low interruption_sensitivity, the robot may consider telling them about the task (e.g., 'breakfast is ready'), since they tolerate interruptions better — but the action_text remains 'make breakfast' as a concrete task, not a suggestion or notification.


time_text: 6 am

available_objects:
coffee maker
toaster
pan
eggs
bread
milk

scenario_rationale: The user is still asleep at 6 am, and the task is low urgency (breakfast can wait). For a user with high interruption_sensitivity, the robot must avoid disturbing them — hence 'no_action'. For a user with low interruption_sensitivity, the robot may consider telling them to wake up and prepare breakfast, since they tolerate interruptions better. The signal flips the decision because the user’s tolerance for disturbance determines whether the robot should act or defer.


time_text: 7 am

objects_nearby:
coffee maker
mugs
pan
spatula

available_objects: eggs bread butter milk toaster

user_state:
sleeping
not awake

scenario_rationale: The user is still asleep and quiet hours are active, making interruption highly undesirable. For a user with high interruption_sensitivity, the robot should avoid initiating action (no_action) to respect rest. For a user with low interruption_sensitivity, the robot may interrupt with a gentle notification (tell_the_user) since the user tolerates interventions even during quiet hours, and the task is low urgency.


time_text: 8 am

activity: daily plant care

user_state:
focused
reading newspaper

scenario_rationale: The user is focused and in quiet hours, making interruption sensitivity the decisive factor: for a high-interruption-sensitivity user, the robot avoids disturbing them by taking no action; for a low-interruption-sensitivity user, the robot deems it acceptable to notify them about watering plants, since the task is low urgency and the environment is calm.


time_text: 9 am

scenario_rationale: The user is focused on email and quiet hours are active, making interruption sensitivity the decisive factor: for a high-interruption-sensitivity user, the robot should avoid interrupting with a low-urgency task like watering plants; for a low-interruption-sensitivity user, the robot may safely notify them to perform the task without causing disruption.


time_text: 10 am

scenario_rationale: The user is focused and quiet hours are active, making interruption undesirable. For a high-interruption_sensitivity user, the robot should avoid initiating the task to preserve concentration and peace. For a low-interruption_sensitivity user, the robot may deem it acceptable to notify the user, since the task is low-urgency and the environment allows for minor disruption.


time_text: 11 am

scenario_rationale: The user is focused on work, making interruption sensitivity the decisive factor: for a high-interruption-sensitivity user, the robot avoids interrupting and takes no action; for a low-interruption-sensitivity user, the robot deems the task non-urgent enough to notify the user, who may then choose to do it themselves.


time_text: 12 pm

scenario_rationale: The user is focused on work during the day, making them less receptive to interruptions. For a user with high interruption_sensitivity, the robot should avoid initiating the task to prevent disruption. For a user with low interruption_sensitivity, the robot may safely notify them to water the plants, as the task is low urgency and the user is not in a private or sensitive moment.


time_text: 1 pm

scenario_rationale: The user is focused on work, making them less receptive to interruptions. For a user with high interruption_sensitivity, the robot should avoid initiating plant care now to prevent distraction. For a user with low interruption_sensitivity, the robot may safely notify them, as the task is low urgency and the user is not in a private or sensitive moment.


time_text: 2 pm

scenario_rationale: The user is focused on work, making them less receptive to interruptions. For a user with high interruption_sensitivity, the robot should avoid initiating the task to prevent distraction. For a user with low interruption_sensitivity, the robot may safely notify them to water the plants, as the user tolerates interruptions better and the task is low urgency.


time_text: 3 pm

scenario_rationale: The user is focused on work during quiet hours, making interruption sensitivity the decisive factor. For a high-interruption-sensitivity user, the robot should avoid disturbing them by not initiating plant care. For a low-interruption-sensitivity user, the robot may interrupt with a gentle notification to water the plants, since the task is low urgency and the environment is calm.


time_text: 4 pm

scenario_rationale: The user is focused on work, making interruption sensitivity the decisive factor: for a high-interruption-sensitivity user, the robot avoids interrupting their concentration, so it chooses 'no_action'. For a low-interruption-sensitivity user, the robot assumes the user tolerates the interruption and chooses 'tell_the_user' to notify them of the plant care task.


time_text: 5 pm

scenario_rationale: The user is focused on work and in a quiet mood, making them sensitive to interruptions. Watering the plants is a low-urgency task that could disrupt their concentration. For a user with high interruption_sensitivity, the robot should avoid acting (no_action) to preserve focus. For a user with low interruption_sensitivity, the robot may safely notify them (tell_the_user) since the task is low-risk and non-intrusive.


time_text: 6 pm

scenario_rationale: The robot must decide whether to interrupt the user’s relaxed evening by taking out the trash. For a user with high interruption_sensitivity, the robot should avoid unnecessary disturbances and choose 'no_action'. For a user with low interruption_sensitivity, the robot may safely notify them ('tell_the_user') since the task is low urgency and the environment is quiet, making interruption less intrusive. The signal flips the decision because the user’s tolerance for interruption directly determines whether the robot acts or waits.


time_text: 7 pm

scenario_rationale: The user is relaxed and watching TV in the evening with guests present, making interruptions less desirable. For a user with high interruption_sensitivity, the robot should avoid disturbing them by taking out the trash without prompting. For a user with low interruption_sensitivity, the robot may interrupt with a gentle notification to perform the chore, since the user tolerates interventions better and the task is low urgency.


time_text: 8 pm

scenario_rationale: At 8 pm on a quiet evening, the user is relaxed and not busy, but the task 'take out the trash' is low urgency and not time-sensitive. For a user with high interruption_sensitivity, the robot should avoid interrupting their calm evening — hence 'no_action'. For a user with low interruption_sensitivity, the robot may consider notifying them since the task is routine and not urgent, hence 'tell_the_user'. The signal flips the decision based on whether the user tolerates interruptions or not, making it the decisive lever.


time_text: 9 pm

scenario_rationale: At 9 pm in a quiet home, taking out the trash is a low-urgency chore. For a user with high interruption_sensitivity, the robot should avoid interrupting their relaxed evening, so 'no_action' is optimal. For a user with low interruption_sensitivity, the robot may consider 'tell_the_user' since the task is routine and non-intrusive, and the user is likely to tolerate a gentle prompt without distress.