Example
How to plan a cross-country road trip without losing miles, overnight stops, and a repair buffer
Sage's problem is not a lack of effort. It is that Cross in five days with named overnight towns, a service plan for the belt, and extra miles treated as a chosen trade 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.
Sage is an explicitly fictional portrait, not a customer or testimonial.
The Five-day crossing Board gives one mission a visible field; the Choose belt, skip loop, or sixth day 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.
Sage's pressure is ordinary—and still heavy
Sage is a fictional 31-year-old driver planning a five-day crossing with a friend in Omaha, Nebraska. Sage has five days of leave. The car is due for a belt soon. A friend wants to add a national-park loop that adds 200 miles. Overnight stops are still “we’ll see how far we get.”
Sage can drive. The crossing fails if overnight towns, a service appointment, and an extra loop never share a day count.
A maps app, a leave calendar, and a mechanic voicemail are three clocks.
The park loop is the point of the trip for one person and a day-killer for the belt.
We’ll see how far we get is not a bed, and a belt is not optional scenery
The mission is specific: Cross in five days with named overnight towns, a service plan for the belt, and extra miles treated as a chosen trade
The consequential choice is not something a board or an AI should quietly make: Whether to service the belt before leaving, skip the park loop, or add a sixth unpaid day the job may not allow
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Sage still owns the purpose, tradeoff, and final call.
Available today
Five-day crossing: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Sage 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 | Five days, overnight towns, and the belt |
| Days | Each driving day with a stop |
| Car | Service and spare |
| Extras | Park loop and other add-ons |
| Waiting | Mechanic and friend’s leave |
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 Sage would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Named towns, five days | Mission | Keep overnight stops beside the belt and the extra loop |
| Choose belt, skip loop, or sixth day | Car | Compare service-first, skip-park, and unpaid-sixth-day options |
| Belt due soon | Car | Hold a mechanical fact so scenery cannot overwrite it |
| Park loop plus 200 miles | Extras | Name the add-on in miles and hours |
| Night two: no town named | Days | Mark a we’ll-see that is not a reservation |
| Mechanic appointment maybe Thursday | Waiting | Keep an unconfirmed service from counting as done |
Available today
Available today: Choose belt, skip loop, or sixth day becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Crossing-path brief: Place leave days, belt, extra miles, and service-first / skip-loop / sixth-day options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Sage to choose a crossing that matches the car and the calendar. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare servicing the belt first, skipping the park loop, and adding a sixth day. Do not book shops 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.
Sage's call remains explicit: Sage chooses the route, talks to the friend and a shop, and owns driving and safety
| Surface | Job in this example |
|---|---|
| Stage | Crossing-path brief: Place leave days, belt, extra miles, and service-first / skip-loop / sixth-day options on one page |
| Chat | Keep Sage's request and Ava's attributed response with the work |
| Pulse | Waiting for Sage to choose a crossing that matches the car and the calendar |
| 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.
Sage owns driving, safety, and bookings. Ava does not book hotels, contact shops, or give mechanical advice as authority.
The modest outcome is not that Ava lives Sage's life. The modest outcome is a crossing with named nights: the belt is a decision, the park loop is a trade, and we’ll-see is no longer a bed.
- Request idea: summarize days, car service, and extra miles already on the Board
- Request idea: compare path options using the belt and leave limit Sage captured
- Request idea: help keep unconfirmed shop times in Waiting
A maps app plus a leave calendar may still be enough
A maps app plus a leave calendar is enough when the car is fresh and nights are booked
It starts to break when a due belt, a 200-mile extra, and unnamed nights share five days
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 Sage'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. Write the day count | Leave is finite |
| 2. Name overnight towns | We’ll-see is not a bed |
| 3. Put car service on the Board | The belt is a fact |
| 4. Measure extras in miles | Loops cost days |
| 5. Decide the trade | Open a Room before scenery writes the route |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a driving day still has no overnight town, still leaving every go-call with Sage.
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
- Sage is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not mechanical, weather, or safety-authority advice.
- It does not show Ava booking lodging or contacting a shop.
- It is not a measured trip result.