Example
How to run youth-team tournament travel without losing rooms, rosters, and a rain delay
Dana's problem is not a lack of effort. It is that Get fourteen players to an 8 a.m. first game with rooms that match the roster, a rain-delay meeting point, and Friday night that does not undo Saturday 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.
Dana is an explicitly fictional portrait, not a customer or testimonial.
The Tournament weekend Board gives one mission a visible field; the Choose the party’s place 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.
Dana's pressure is ordinary—and still heavy
Dana is a fictional 39-year-old team manager for a weekend tournament two hours away in St. Catharines, Ontario. Dana has a hotel block, a roster of fourteen, and two families driving separately. The first game is at 8 a.m. A rain delay is common at this venue. A parent offered a late Saturday party that would break curfew the night before the final.
Dana can book rooms. The weekend fails if arrivals, the 8 a.m. start, and a rain-delay plan live in a chat.
A hotel email, a roster spreadsheet, and a parent group chat disagree about Friday night.
The party is generous and would strand the 8 a.m. roster on Saturday.
A hotel block is not a roster, and a party is not a 8 a.m. game
The mission is specific: Get fourteen players to an 8 a.m. first game with rooms that match the roster, a rain-delay meeting point, and Friday night that does not undo Saturday
The consequential choice is not something a board or an AI should quietly make: Whether to decline the Saturday party, make it optional after the last game, or keep Friday quiet and skip the party entirely
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Dana still owns the purpose, tradeoff, and final call.
Available today
Tournament weekend: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Dana 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 | 8 a.m. roster, rooms, rain meeting point |
| People and rooms | Players, families, hotel block |
| Games | Start times and delay rules as posted |
| Travel | Two-hour drive and separate cars |
| Waiting | Hotel names and party 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 Dana would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Fourteen at 8 a.m. | Mission | Keep first-game time beside the hotel block and the party offer |
| Choose the party’s place | Games | Compare decline, after-last-game, and skip-entirely options |
| Hotel block versus roster | People and rooms | Count beds against fourteen players plus adults |
| Rain-delay meeting point | Games | Name a place so a delay is not a parking-lot scatter |
| Two families driving separate | Travel | Hold arrivals that may miss a Friday night check-in |
| Parent party offer Saturday | Waiting | Keep a generous maybe from setting curfew |
Available today
Available today: Choose the party’s place becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Weekend-energy brief: Place 8 a.m. start, hotel block, and decline / after-games / skip options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Dana to choose a Friday-Saturday posture the roster can play. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare declining the party, making it after the last game, and skipping it. Do not message parents 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.
Dana's call remains explicit: Dana chooses the plan, talks to families and the hotel, and owns travel and safety
| Surface | Job in this example |
|---|---|
| Stage | Weekend-energy brief: Place 8 a.m. start, hotel block, and decline / after-games / skip options on one page |
| Chat | Keep Dana's request and Ava's attributed response with the work |
| Pulse | Waiting for Dana to choose a Friday-Saturday posture the roster can play |
| 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.
Dana owns family messages, hotel, and safety. Ava does not contact parents, book rooms, or give coaching advice.
The modest outcome is not that Ava lives Dana's life. The modest outcome is a weekend that can play: rooms match the roster, a rain meeting point is named, and a party is after games or it is not.
- Request idea: summarize rooms, games, and travel Cards already on the Board
- Request idea: compare party options using the 8 a.m. start Dana captured
- Request idea: help keep unconfirmed hotel names in Waiting
A parent group chat plus a hotel email may still be enough
A parent group chat plus a hotel email is enough when the roster fits the rooms and nights are quiet
It starts to break when an 8 a.m. game, separate cars, and a Saturday party share one hotel block
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 Dana'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 first-game time on the Board | 8 a.m. is the constraint |
| 2. Count rooms against the roster | Beds plus adults |
| 3. Name a delay meeting point | Rain is not a scatter |
| 4. Card separate cars | Arrivals that can miss check-in |
| 5. Decide Friday night | Open a Room before a party writes Saturday |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a game Card is at 8 a.m. and a Friday arrival is still Waiting, still leaving every message with Dana.
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
- Dana is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not coaching, safeguarding, or travel-legal advice.
- It does not show Ava messaging parents or booking hotels.
- It is not a measured tournament result.