Example
How to produce a community arts festival without losing acts, permits, or load-in
Fiona's problem is not a lack of effort. It is that 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 has outgrown scattered reminders, tabs, and memory. This fictional playbook shows a concrete Board, the Cards inside it, one consequential Room, and the line Ava does not cross.
This fictional example was created with AI assistance from a structured editorial brief and reviewed by the You.one Editorial Team for usefulness, distinctness, and product truth.
Fiona is an explicitly fictional portrait, not a customer or testimonial.
The Festival day Board gives one mission a visible field; the Choose the last-hour plan Room keeps its evidence, conversation, state, and decision together.
Current Superboard provides the durable structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Fiona's pressure is ordinary—and still heavy
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.
Fiona can book acts. The day fails when the last set is scheduled after the generator must leave.
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.
A lineup is not a day if power, permit, and pickup times disagree
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 and ask for a later pickup, move the headline earlier, or split the last hour to the indoor hall
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Fiona still owns the purpose, tradeoff, and final call.
Available today
Festival day: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Fiona does not have to convert life into project-management jargon or decide the perfect taxonomy first. Lists separate kinds of attention; Cards keep each meaningful item visible and movable.
The Cards are deliberately mixed. Some are tasks, some are decisions, some hold a person or promise, and some are reference points. Current Superboard supports that flexibility without flattening the mission into one long to-do list.
| List | What belongs here |
|---|---|
| Mission | Day, street hours, and rain-place rule |
| Lineup | Acts with sets and technical needs |
| City and power | Permit, generator, pickup |
| Vendors | Food and power draws |
| Waiting | Permit and public-works replies |
Available today
The Cards make the operating picture concrete
A Board becomes useful when the Card titles sound like the actual situation. These are not generic placeholders; they show what Fiona would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| A day that ends before pickup | Mission | Keep generator return time beside the headline ask |
| Choose the last-hour plan | Lineup | Compare later-pickup ask, earlier headline, and indoor split |
| Headline wants last set | Lineup | Hold the ask against the pickup window |
| Generator pickup window | City and power | Make public-works time a hard Card |
| Two vendors needing power | Vendors | Count draws so the stage is not the only load |
| Street-closure permit in process | Waiting | Keep an unreturned city step from counting as closed streets |
Available today
Available today: Choose the last-hour plan becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Close-of-day brief: Place pickup window, headline ask, 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 Waiting for Fiona to choose how the day ends. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare asking for later pickup, moving the headline, and splitting indoors. Do not contact the city or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported context and can make limited reversible product changes. She does not deeply reason over the whole Board by default, and 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
| Surface | Job in this example |
|---|---|
| Stage | Close-of-day brief: Place pickup window, headline ask, indoor capacity, and the three options on one page |
| Chat | Keep Fiona's request and Ava's attributed response with the work |
| Pulse | Waiting for Fiona to choose how the day ends |
| Activity | Preserve attributed Card changes and the supported record around the request |
What to ask Ava—and what not to assume
These are useful requests to adapt, not claims that current Ava automatically surveys the whole Board, prepares every comparison, or follows up on her own. The relevant facts must be present in supported Board/Card context, and the human still checks the result.
Fiona owns bookings, permits, and safety. Ava does not contact the city, acts, or vendors.
The modest outcome is not that Ava lives Fiona's life. The modest outcome is a day that can end: the headline is placed on purpose, vendor power is counted, and the permit is not assumed done.
- Request idea: summarize lineup, power, and waiting permit items already on the Board
- Request idea: compare last-hour options using pickup time Fiona captured
- Request idea: help keep in-process permits in Waiting
A lineup spreadsheet plus permit email may still be enough
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
Superboard earns a place only when the responsibility needs a durable picture around the list: the reason, artifact, conversation, current state, decision, and history.
A starter recipe to adapt, not obey
Use the names that already make sense in Fiona's world. The recipe is successful when the Board reduces remembering and exposes the real decision—not when every Card is perfectly categorized.
| Step | Action |
|---|---|
| 1. Put city clocks on the Board | Permit and pickup |
| 2. Card acts with needs | Last set is a request |
| 3. Count vendor power | The stage is not the only load |
| 4. Name the rain place | Capacity included |
| 5. Decide the last hour | Open a Room before the generator leaves mid-set |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a lineup Card sits after a pickup window, still leaving every booking with Fiona.
The unified You.one and Superboard runtime, cross-product personalized Memory Spine, broad proactive coordination, realtime shared editing, and general external execution are not available today. Future actions would still require the applicable capability, connection, grant, and human authority.
What this realistic example does not claim
- 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.