How to produce a community arts festival without losing acts, permits, or the close of day

Fiona is a fictional 40-year-old volunteer producer of a one-day street festival in Charlottetown, Prince Edward Island. Fiona has twelve acts, a street-closure permit in process, and a stage loan that depends on a dry forecast. Two food vendors need power. A headline act asked to go last, which collides with a city generator pickup time, so Fiona has already asked public works for a later pickup.

A lineup spreadsheet, a permit email, and a public-works pickup window are three clocks.

Rain would move acts indoors to a hall that holds fewer people than the street.

In You.one's Superboard view, Fiona can give “Run one day with a lineup that fits permit, power, and pickup times, and a rain plan that is a place rather than a hope” a Board of its own. That Board connects community promises, volunteer capacity, local evidence, and human authority; opening “Choose the last-hour plan” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Run one day with a lineup that fits permit, power, and pickup times, and a rain plan that is a place rather than a hope.

The consequential choice is not something a board or an AI should quietly make: Whether to keep the headline last outdoors if the permit, dry forecast, and later pickup confirm, move the headline earlier outdoors if the permit and dry forecast confirm, or book the smaller hall now and run the headline indoors.

You.one can keep the work, evidence, live dependency, and “Choose the last-hour plan” decision visible through its Superboard view. The Owner boundary stays explicit: Fiona chooses the lineup, talks to the city and acts, and owns permits and safety.

The Festival day Board gives this mission one durable operating picture. Fiona can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Fiona's situation: “Choose the last-hour plan” is the live choice, “Headline wants last set” holds evidence, and “Street-closure permit in process” names something genuinely in motion outside Fiona's control. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Close-of-day brief: Place permit status, dry-forecast stage loan, pickup window, headline ask, two vendor power draws, indoor capacity, and the three options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Fiona will choose how the day ends.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Close-of-day brief and this Card Room's visible notes and left “Choose the last-hour plan” with Fiona.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare keeping the headline last outdoors if the permit, dry forecast, and later pickup confirm; moving the headline earlier outdoors if the permit and dry forecast confirm; and booking the smaller hall now for an indoor day. Do not contact the city, book the hall, 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.

Fiona's call remains explicit: Fiona chooses the lineup, talks to the city and acts, and owns permits and safety.

These requests use the visible supported context inside the “Choose the last-hour plan” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Fiona 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 Fiona, watch other Lists, or act outside this Card Room.

Fiona owns bookings, permits, and safety. Ava does not contact the city, acts, or vendors.

A day that can end: the headline is placed on purpose, vendor power is counted, and the permit is not assumed done.

• Request idea: using only the context visible in this Card Room, compare keeping the headline last outdoors if the permit, dry forecast, and later pickup confirm; moving the headline earlier outdoors if the permit and dry forecast confirm; and booking the smaller hall now for an indoor day. Do not contact the city, book the hall, or choose for me.
• Request idea: use only the Close-of-day 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 lineup spreadsheet plus permit email is enough when the street is already closed and power is simple.

It starts to break when a headline last set, a pickup window, and two vendor draws share one generator.

The Festival day Board earns its place only when the familiar tool—a lineup spreadsheet plus permit email—can no longer keep the reason, Close-of-day brief, conversation, current state, decision, and history connected.

Fiona should rename every List or Card that feels artificial. This recipe succeeds when “Choose the last-hour plan” 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 lineup Card sits after a pickup window, still leaving every booking with Fiona.

A future unified You.one experience could carry relevant context from “Choose the last-hour plan” 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.

• Fiona is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This is not permitting, electrical, or safety advice.
• It does not show Ava contacting the city or booking acts.
• It is not a measured attendance result.