Example
How to plan a group camping trip without losing permits, gear, and a weather call
Quinn's problem is not a lack of effort. It is that Run two nights with sites, tents, and food that match the weather—or delay using the park’s written change window 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.
Quinn is an explicitly fictional portrait, not a customer or testimonial.
The Two-night camp Board gives one mission a visible field; the Choose keep, delay, or Friday only 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.
Quinn's pressure is ordinary—and still heavy
Quinn is a fictional 36-year-old friend organizing a two-night group camp in Bend, Oregon. Quinn reserved two sites. Six people said yes. Two have never camped. A storm window moved into Saturday night. The car with the big tent is also the car with a maybe-cancellation.
Quinn can pack. The weekend fails if gear, cooking, and a storm call live in a chat that already said yes.
A park confirmation, a group chat, and a gear closet photo do not share Saturday night.
Canceling feels dramatic. Sleeping six people through a storm in one remaining tent is also a decision.
A reservation is not a trip if the tent car is a maybe
The mission is specific: Run two nights with sites, tents, and food that match the weather—or delay using the park’s written change window
The consequential choice is not something a board or an AI should quietly make: Whether to keep Saturday and bring a second borrowed tent, delay to the following weekend, or drop to a one-night trip Friday only
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Quinn still owns the purpose, tradeoff, and final call.
Available today
Two-night camp: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Quinn 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 | Sites, tents, and a weather call |
| People and cars | Who is coming and what they can carry |
| Gear | Tents, cook kit, and what is borrowed |
| Weather and park | Forecast, permit, change window |
| Waiting | Maybe-car and borrowed-tent 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 Quinn would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Tents that match the night | Mission | Keep storm Saturday beside the maybe tent car |
| Choose keep, delay, or Friday only | Weather and park | Compare second-tent, delay-weekend, and one-night options |
| Two site reservations | Weather and park | Attach confirmation numbers and the change window as written |
| Car with the big tent: maybe | People and cars | Name the cancellation risk that the chat already treated as coming |
| Two first-time campers | People and cars | Keep skill mix visible without stereotyping anyone as helpless |
| Borrowed tent ask | Waiting | Keep an unconfirmed extra tent from being the storm plan |
Available today
Available today: Choose keep, delay, or Friday only becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Weather-call brief: Place storm window, tent-car maybe, park change window, and keep / delay / Friday-only options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Quinn to choose a weather posture that matches tents. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare bringing a second tent, delaying a week, and Friday only. Do not message the group 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.
Quinn's call remains explicit: Quinn chooses the dates, talks to the group and park, and owns safety and spending
| Surface | Job in this example |
|---|---|
| Stage | Weather-call brief: Place storm window, tent-car maybe, park change window, and keep / delay / Friday-only options on one page |
| Chat | Keep Quinn's request and Ava's attributed response with the work |
| Pulse | Waiting for Quinn to choose a weather posture that matches tents |
| 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.
Quinn owns safety, bookings, and group messages. Ava does not contact the park, message friends, or give outdoor-safety advice as authority.
The modest outcome is not that Ava lives Quinn's life. The modest outcome is a trip with a weather call: the maybe car is named, the park change window is on the Board, and a second tent is real or the date moves.
- Request idea: summarize people, gear, and park constraints already on the Board
- Request idea: compare keep / delay / Friday-only using the tent-car maybe Quinn captured
- Request idea: help keep borrowed-tent asks in Waiting
A group chat plus a park confirmation email may still be enough
A group chat plus a park confirmation email is enough when the tent car is certain and the sky is quiet
It starts to break when a storm Saturday, a maybe car, and six yeses share two sites
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 Quinn'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. Attach park confirmations | Change windows as written |
| 2. Card cars and tents | Maybes are not gear |
| 3. Note first-timers as planning facts | Without turning them into a joke |
| 4. Park borrowed asks | Waiting until confirmed |
| 5. Decide weather | Open a Room before Saturday night |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a storm Card has no tent coverage, still leaving every go-call with Quinn.
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
- Quinn is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not wilderness, weather, or safety authority advice.
- It does not show Ava contacting a park or messaging the group.
- It is not a measured trip result.