Example
How to plan a music-festival weekend without turning every set into an obligation
The lineup has become a completeness challenge instead of a shared weekend. The friends must stay for Sunday’s headliner, leave earlier together, or split departures while keeping meeting points and each person’s safety choices explicit.
See the artists that matter, protect transport and recovery, and let friends split without losing each other
Why this mission matters and what it must not consume
Hold the mission and boundary: see the artists that matter, protect transport and recovery, and let friends split without losing each other
The small set of work that can change this mission now
Hold the live choice—whether to stay for Sunday's headliner, leave earlier together, or split departures—so Cole can decide from the evidence in this Room
Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed
Complete this as owned preparation; if another person must answer, keep it as an unsent draft until it is actually sent
Use the result of the first owned action to update the Sunday-departure brief; record the finding, not merely the effort
What Cole knows, where it came from, and what remains uncertain
Supply the evidence for the Sunday-departure brief: place artist priority, campsite travel, drivers, recovery, and split logistics together. Live choice: Whether to stay for Sunday's headliner, leave earlier together, or split departures.
Ground stay, leave, or split in the actual departure logistics
In You.one’s Superboard view, the Festival energy Board separates the weekend promise, sets to consider, travel evidence, friends’ replies only after asking, and plans the group has actually confirmed.
Open Stay, leave together, or split departures as the consequential Card Room. Start by marking only two must-see sets per person and naming driver-recovery and campsite travel time.
After an explicit request, Ava can compare visible preferences and logistics. Ava cannot message friends, book, buy, navigate, assess weather or crowd safety, or choose for anyone; each person owns plans, money, travel, and safety.
Festival energy has one live choice: Stay, leave, or split
The mission is specific: See the artists that matter, protect transport and recovery, and let friends split without losing each other.
The consequential choice is not something a board or an AI should quietly make: Whether to stay for Sunday's headliner, leave earlier together, or split departures.
You.one can keep the work, evidence, and “Stay, leave, or split” decision visible through its Superboard view. Authority does not move to the software: Cole, as the festivalgoer coordinating a four-person trip, owns the preparation and the decision about whether to stay for Sunday's headliner, leave earlier together, or split departures.
Available today
Festival energy: the working map
The Festival energy Board gives this mission one durable operating picture. Cole can use familiar language instead of translating the situation into project-management jargon. Its three Lists separate the kinds of attention this situation actually requires.
The Lists separate what Cole can move now, what is evidence, what is already waiting on a named person or event, and what still needs a decision.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Weekend promise | Why this mission matters and what it must not consume |
| Sets next | The small set of work that can change this mission now |
| Travel evidence | What Cole knows, where it came from, and what remains uncertain |
Available today
Open one decision: Stay, leave, or split
Opening the Card gives the visible item durable depth. Stage can hold Sunday-departure brief: Place artist priority, campsite travel, drivers, recovery, and split logistics together. Live choice: Whether to stay for Sunday's headliner, leave earlier together, or split departures. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Cole will decide whether to stay for Sunday's headliner, leave earlier together, or split departures.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Stay, leave, or split” from the visible evidence. Ava can work from the context Cole deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Cole's call remains explicit: Cole, as the festivalgoer coordinating a four-person trip, owns the preparation and the decision about whether to stay for Sunday's headliner, leave earlier together, or split departures.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Sunday-departure brief: Place artist priority, campsite travel, drivers, recovery, and split logistics together. Live choice: Whether to stay for Sunday's headliner, leave earlier together, or split departures |
| Chat | Keep Cole's request and Ava's attributed response with the work |
| Pulse | Open decision: Cole will decide whether to stay for Sunday's headliner, leave earlier together, or split departures |
Useful Ava requests, with the boundary intact
These requests stay with the facts Cole has made visible around “Stay, leave, or split.” Cole supplies the evidence, checks Ava's work, and decides what belongs in the Room.
Current Ava can prepare help after an explicit request. She cannot make the choice, represent Cole, watch other work on her own, or contact anyone.
Cole, as the festivalgoer coordinating a four-person trip, owns the preparation and the decision about whether to stay for Sunday's headliner, leave earlier together, or split departures. Ava may help only inside this Card Room; she cannot decide, represent anyone, contact people, or act elsewhere.
Cole finishes “Mark only two must-see sets per person,” keeps “Four must-see maps” beside “Stay, leave, or split,” and does not treat “Draft the departure request” as completed or sent before doing the work.
- Request idea: from this Room only, draft a neutral comparison for Stay, leave, or split. Cite only notes visible in this Room, name missing evidence, and do not decide or contact anyone.
- Request idea: use only the Sunday-departure brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Stay, leave, or split,” show which visible fact could reverse the current choice
The limit of a saved lineup
A saved lineup can be enough while the situation stays simple: two-must-see maps, the distant campsite, driver recovery, and the Sunday drive already settle stay, leave, or split.
It starts to break when the owned departure request, driver recovery, campsite travel, and Sunday headliner must inform the same departure choice; no friend reply is implied before the request is sent.
The Festival energy Board earns its place only when the familiar tool—a saved lineup—can no longer keep the reason, Sunday-departure brief, conversation, current state, decision, and history connected.
A practical way to start the Festival energy Board
Cole should rename every List or Card that feels artificial. This recipe succeeds when “Stay, leave, or split” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
Swipe or scroll sideways to see every column.
| Step | Action |
|---|---|
| 1. Write the mission | See the artists that matter, protect transport and recovery, and let friends split without losing each other |
| 2. Open the live choice | Put “Stay, leave, or split” in a Room of its own |
| 3. Attach the evidence | Sunday-departure brief: Place artist priority, campsite travel, drivers, recovery, and split logistics together. Live choice: Whether to stay for Sunday's headliner, leave earlier together, or split departures. |
| 4. Keep the work owned | Keep “Draft the departure request” in owned work and name the next visible move |
| 5. Take the first owned action | Mark only two must-see sets per person |
Where this example stops
- This is a fictional example, not a customer story.
- This fictional example is not travel, substance-use, medical, weather, crowd-safety, or event advice; each person owns their safety and current plans.
- It does not show Ava completing external actions or contacting anyone for Cole.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.