How to run a family reunion weekend without losing beds, food, and the one hard conversation

Alistair is a fictional 54-year-old cousin hosting a three-day family reunion in Brandon, Manitoba. Alistair offered his town. A community hall is booked Saturday. Beds are a mix of spare rooms and a motel block. Two relatives need a quiet hour that is not on the loud schedule. Someone wants a slide show that would eat the only indoor evening.

A group email, a motel hold, and a hall invoice do not show who is actually sleeping where.

The slide show is beloved and would strand two people who already asked for a short outdoor walk instead.

In You.one's Superboard view, Alistair can give “Host three days with named beds, meals that match notes, and one indoor evening that is not accidentally a two-hour slideshow” a Board of its own. That Board connects the shared purpose, logistics, preferences, and decisions people still own; opening “Choose the slideshow’s place” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Host three days with named beds, meals that match notes, and one indoor evening that is not accidentally a two-hour slideshow.

The consequential choice is not something a board or an AI should quietly make: Whether to keep the slideshow short before dinner, move it to a voluntary Saturday night, or skip it and print a photo table.

You.one can keep the work, evidence, and “Choose the slideshow’s place” decision visible through its Superboard view. The Owner boundary stays explicit: Alistair chooses the schedule, talks to relatives, and owns spending and housing.

The Reunion three days Board gives this mission one durable operating picture. Alistair can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, and decisions while keeping unsent questions in owned work. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Alistair's situation: “Choose the slideshow’s place” is the live choice, “Motel block hold” holds evidence, and “Hall Saturday invoice” is still work Alistair controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Indoor-evening brief: Place quiet-hour ask, hall hours, and short / voluntary / photo-table options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Alistair will choose an indoor evening that leaves a quiet hour.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Indoor-evening brief and this Card Room's visible notes and left “Choose the slideshow’s place” with Alistair.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare a short slideshow before dinner, a voluntary Saturday night, and a photo table. Do not email relatives or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.

Alistair's call remains explicit: Alistair chooses the schedule, talks to relatives, and owns spending and housing.

These requests use the visible supported context inside the “Choose the slideshow’s place” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Alistair must provide the relevant facts and check the result.

Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Alistair, watch other Lists, or act outside this Card Room.

Alistair owns invitations, housing, and money. Ava does not email relatives, book motels, or mediate family history.

A weekend with beds and an evening choice: the quiet hour stays visible, the motel block is counted, and a slideshow is not the whole indoor night by default.

• Request idea: using only the context visible in this Card Room, compare a short slideshow before dinner, a voluntary Saturday night, and a photo table. Do not email relatives or choose for me.
• Request idea: use only the Indoor-evening brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
• Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

A group email plus a motel hold is enough when everyone fits in one house.

It starts to break when a slideshow, a quiet-hour ask, and uncounted beds share Saturday.

The Reunion three days Board earns its place only when the familiar tool—a group email plus a motel hold—can no longer keep the reason, Indoor-evening brief, conversation, current state, decision, and history connected.

Alistair should rename every List or Card that feels artificial. This recipe succeeds when “Choose the slideshow’s place” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, Ava may help this Board notice when a person Card has no bed, still leaving every booking with Alistair.

A future unified You.one experience could carry relevant context from “Choose the slideshow’s place” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.

• Alistair is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not event-planning or family-mediation advice.
• It does not show Ava contacting relatives or booking rooms.
• It is not a measured gathering result.