Example
How to run a youth sports season without losing games in a group chat
Carla's problem is not a lack of effort. It is that Run the remaining season with games, rides, and weather backups visible, and treat the tournament as a roster-true yes or a no 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.
Carla is an explicitly fictional portrait, not a customer or testimonial.
The U12 remaining season Board gives one mission a visible field; the Choose the tournament weekend 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.
Carla's pressure is ordinary—and still heavy
Carla is a fictional 38-year-old volunteer coach of a U12 soccer team in Ann Arbor, Michigan. Carla has a season schedule, a field that floods, and a group chat where last-minute changes disappear. Two families share rides. A tournament invite lands on a weekend a third of the team already has a band trip.
Carla can coach. She cannot currently see who needs a ride, which weekends are already lost, and whether the tournament is a yes.
A league PDF, a group chat, and two carpool texts all hold different kickoff times.
The tournament is flattering and would leave seven players on a bus for band.
A chat is not the season; a flooded field is not a surprise if it has a Card
The mission is specific: Run the remaining season with games, rides, and weather backups visible, and treat the tournament as a roster-true yes or a no
The consequential choice is not something a board or an AI should quietly make: Whether to decline the tournament, go with a short roster, or ask the league about a friendly instead on a clearer weekend
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Carla still owns the purpose, tradeoff, and final call.
Available today
U12 remaining season: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Carla 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 | Season aims and the roster-true rule |
| Games | Dates, fields, and backups |
| People | Players, rides, and absences |
| Weather and fields | Flood history and cancellation sources |
| Waiting | League and family 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 Carla would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| A season the roster can actually play | Mission | Keep absences beside invites |
| Choose the tournament weekend | Games | Compare decline, short roster, and league-friendly options |
| Band trip: seven players out | People | Count a known absence before saying yes |
| Home field flood backup | Weather and fields | Name the alternate field instead of discovering it in the chat |
| Saturday ride: two families | People | Make carpool a Card with names |
| League: friendly date? | Waiting | Keep an unasked alternative from counting as a plan |
Available today
Available today: Choose the tournament weekend becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Weekend-roster brief: Place band absences, rides, and decline / short-roster / friendly options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Carla to choose a weekend that matches the roster. 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 tournament, going short, and asking for a friendly. Do not message families 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.
Carla's call remains explicit: Carla chooses the weekend, talks to families and the league, and owns coaching and safety
| Surface | Job in this example |
|---|---|
| Stage | Weekend-roster brief: Place band absences, rides, and decline / short-roster / friendly options on one page |
| Chat | Keep Carla's request and Ava's attributed response with the work |
| Pulse | Waiting for Carla to choose a weekend that matches the roster |
| 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.
Carla owns coaching, family messages, and safety. Ava does not contact the league, message parents, or cancel games.
The modest outcome is not that Ava lives Carla's life. The modest outcome is a weekend that matches the roster: absences are counted, a flood backup is named, and the tournament is a chosen yes or no.
- Request idea: summarize games, absences, and ride Cards already on the Board
- Request idea: compare tournament options using the seven-player absence Carla captured
- Request idea: help keep unasked league alternatives in Waiting
A group chat plus a league PDF may still be enough
A group chat plus a league PDF is enough when the roster is stable and the field never floods
It starts to break when a tournament, a band trip, and a flood backup all live in different threads
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 Carla'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 remaining games on the Board | Dates and fields |
| 2. Card known absences | Band trips are constraints |
| 3. Name rides | Carpools with people |
| 4. Write field backups | Floods should not be a chat surprise |
| 5. Decide extras | Open a Room before a tournament yes strands seven players |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a game Card has no ride coverage, still leaving every message with Carla.
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
- Carla is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not coaching, medical, or safeguarding advice.
- It does not show Ava messaging families or the league.
- It is not a measured season result.