Example
How a mobile mechanic can run a workflow without losing parts, miles, or promises
Cole can diagnose. A day that ignores the parts-store clock and the first job’s address becomes a string of apology texts.
Run tomorrow with a route that hits the parts-store clock, promised arrival windows, and no untimed quick look hiding in the middle
Parts-store clock and promised windows
Keep closing time and promised windows on the same mission as the work
Each vehicle with address and promise
Hold address and the window already texted
Keep the second paid job visible with its address and promised window
Mark an unbounded ask sitting between paying jobs
What is in the van versus what must be bought
Count on-hand parts so a store run is not automatic
Order of the day, including drive time
Compare three complete day orders that resolve the no-start, brake job, quick look, and 5 p.m. parts hold
Customer replies and parts counter holds
Keep the possible no-start pickup tied to the real 5 p.m. counter clock without implying diagnosis or purchase
Cole is an explicitly fictional portrait, not a customer or testimonial.
The Tomorrow’s van Board gives one mission a visible field; the Choose tomorrow’s order Room keeps its evidence, conversation, state, and decision together.
Current You.one provides the Superboard structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Why Tomorrow’s van needs an operating picture
Cole is a fictional 38-year-old mobile mechanic working from a van in Red Deer, Alberta. Cole books jobs by text and voicemail. Tomorrow has a no-start across town, a brake job near home, and a parts store that closes at 5. A customer asked for a “quick look” that last time became three hours.
Voicemail, a parts-counter photo, and a paper invoice pad do not share a route.
A “quick look” has no time cap and is currently sitting between two paying jobs as if it were twenty minutes.
In You.one's Superboard view, Cole can give “Run tomorrow with a route that hits the parts-store clock, promised arrival windows, and no untimed quick look hiding in the middle” a Board of its own. That Board connects customer promises, operating evidence, capacity, and the owner's judgment; opening “Choose tomorrow’s order” creates a Room for its evidence, discussion, state, and decision.
Miles and parts closing time are the real calendar
The mission is specific: Run tomorrow with a route that hits the parts-store clock, promised arrival windows, and no untimed quick look hiding in the middle.
The consequential choice is not something a board or an AI should quietly make: Whether to run no-start then brakes and decline the quick look, run brakes then no-start and decline the quick look, or run no-start then a capped quick look and reschedule the brake job.
You.one can keep the work, evidence, live dependency, and “Choose tomorrow’s order” decision visible through its Superboard view. The Owner boundary stays explicit: Cole chooses the route, texts customers, and owns diagnosis, safety, and invoices.
Available today
Tomorrow’s van: one Board shape to adapt
The Tomorrow’s van Board gives this mission one durable operating picture. Cole can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.
Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.
| List | What belongs here |
|---|---|
| Mission | Parts-store clock and promised windows |
| Jobs | Each vehicle with address and promise |
| Parts | What is in the van versus what must be bought |
| Route | Order of the day, including drive time |
| Waiting | Customer replies and parts counter holds |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Cole's situation: “Choose tomorrow’s order” is the live choice, “No-start across town” holds evidence, and “Parts counter hold until 5” names something genuinely in motion outside Cole's control. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Hit the parts-store clock | Mission | Keep closing time and promised windows on the same mission as the work |
| Choose tomorrow’s order | Route | Compare three complete day orders that resolve the no-start, brake job, quick look, and 5 p.m. parts hold |
| No-start across town | Jobs | Hold address and the window already texted |
| Brake job near home | Jobs | Keep the second paid job visible with its address and promised window |
| Brake pads in the van | Parts | Count on-hand parts so a store run is not automatic |
| Quick look with no time cap | Jobs | Mark an unbounded ask sitting between paying jobs |
| Parts counter hold until 5 | Waiting | Keep the possible no-start pickup tied to the real 5 p.m. counter clock without implying diagnosis or purchase |
Available today
Available today: Choose tomorrow’s order becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Route brief: Place both paid jobs, the uncapped quick look, addresses, the 5 p.m. parts hold, and the three complete day orders on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Cole will choose tomorrow’s route.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Route brief and this Card Room's visible notes and left “Choose tomorrow’s order” with Cole.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare no-start then brakes with the quick look declined, brakes then no-start with the quick look declined, and no-start then a capped quick look with the brake job rescheduled. Do not text customers, assume a time cap, or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.
Cole's call remains explicit: Cole chooses the route, texts customers, and owns diagnosis, safety, and invoices.
| Surface | Job in this example |
|---|---|
| Stage | Route brief: Place both paid jobs, the uncapped quick look, addresses, the 5 p.m. parts hold, and the three complete day orders on one page |
| Chat | Keep Cole's request and Ava's attributed response with the work |
| Pulse | Open decision: Cole will choose tomorrow’s route |
| Activity | Ava compared the options in Card Chat using the Route brief and this Card Room's visible notes and left “Choose tomorrow’s order” with Cole |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose tomorrow’s order” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Cole must provide the relevant facts and check the result.
Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Cole, watch other Lists, or act outside this Card Room.
Cole owns diagnosis, safety, pricing, and customer messages. Ava does not text customers, buy parts, or repair vehicles.
A tomorrow that can be driven: the parts clock is on the Board, the quick look is a yes or no, and promised windows have an order.
- Request idea: using only the context visible in this Card Room, compare no-start then brakes with the quick look declined, brakes then no-start with the quick look declined, and no-start then a capped quick look with the brake job rescheduled. Do not text customers, assume a time cap, or choose for me.
- Request idea: use only the Route brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously
Voicemail plus a paper invoice pad may still be enough
Voicemail plus a paper invoice pad is enough when one job and parts already in the van.
It starts to break when two addresses, a 5 p.m. counter, and a quick look all claim the afternoon.
The Tomorrow’s van Board earns its place only when the familiar tool—voicemail plus a paper invoice pad—can no longer keep the reason, Route brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Cole should rename every List or Card that feels artificial. This recipe succeeds when “Choose tomorrow’s order” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Write the clock | Parts-store hours on the Mission Card |
| 2. Card each job | Address and promised window |
| 3. Count van parts | Store runs are work |
| 4. Mark unbounded asks | Quick looks need a time cap or a no |
| 5. Choose tomorrow’s order | Open a Room the night before the route |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a job Card sits after a parts-store closing time, still leaving every route call with Cole.
A future unified You.one experience could carry relevant context from “Choose tomorrow’s order” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.
What this realistic example does not claim
- Cole is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not mechanical, safety, or pricing advice.
- It does not show Ava contacting customers or buying parts.
- It is not a measured job or revenue result.