Example
How to choose a mobile coffee route when the busiest stop is not the best morning
Foot traffic counts people, not setup time, menu mix, repeatability, or the drive between stops.
AI assistance helped shape this fictional example from a structured editorial brief. It was reviewed for usefulness, distinctness, accessibility, and product truth.
Build a repeatable morning route that keeps one strong promise instead of chasing every crowd
The result Farah is trying to create—not every possible task
Keep one repeatable morning promise inside the eleven-o'clock stop
The current choice, preparation, and other owned next moves
Compare construction, office, and school-first routes
Time setup and teardown once at the current stop
Evidence for the live choice, drawn from the situation's actual sources
Record construction-site volume and service conditions
Record office-plaza food margin and repeat-customer value
Compare margin with the construction site's volume
Record when the school stop earns or loses its place in the route
A separate place for operating constraints without inventing a Waiting state
Hold the host-access windows and drive constraints that limit setup
Keep setup, driving, and service inside the actual morning
Farah is an explicitly fictional portrait, not a customer or testimonial.
The Morning route Board gives one mission a visible field; the Construction, office, or school-first route 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 Morning route needs an operating picture
Farah is a fictional 30-year-old owner-operator of a mobile coffee cart in Ottawa, Ontario. A construction site offers volume, an office plaza buys higher-margin food, school traffic peaks earlier, and the cart cannot serve all three before eleven.
The construction site offers volume, but every setup and drive consumes minutes from a morning that ends at eleven.
The office plaza sells higher-margin food while the school peaks earlier, so raw foot traffic cannot tell Farah which route is repeatable.
In You.one's Superboard view, Farah can give “Build a repeatable morning route that keeps one strong promise instead of chasing every crowd” a Board of its own. That Board connects customer promises, operating evidence, capacity, and the owner's judgment; opening “Construction, office, or school-first route” creates a Room for its evidence, discussion, state, and decision.
Morning route has one live choice: Construction, office, or school-first route
The mission is specific: Build a repeatable morning route that keeps one strong promise instead of chasing every crowd.
The consequential choice is not something a board or an AI should quietly make: Whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu.
You.one can keep the work, evidence, and “Construction, office, or school-first route” decision visible through its Superboard view. The Owner boundary stays explicit: Farah chooses the route, drives and operates the cart, handles food and money, and owns every host and customer promise.
Available today
Morning route: one Board shape to adapt
The Morning route Board gives this mission one durable operating picture. Farah can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.
Its Cards deliberately distinguish actions, evidence, and decisions while keeping unsent questions in owned work. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.
| List | What belongs here |
|---|---|
| Route promise | The result Farah is trying to create—not every possible task |
| Stops to test | The current choice, preparation, and other owned next moves |
| Service evidence | Evidence for the live choice, drawn from the situation's actual sources |
| Operating constraints | A separate place for operating constraints without inventing a Waiting state |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Farah's situation: “Construction, office, or school-first route” is the live choice, “Construction site” holds evidence, and “Host-access windows” is still work Farah controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Morning route | Route promise | Keep one repeatable morning promise inside the eleven-o'clock stop |
| Construction, office, or school-first route | Stops to test | Compare construction, office, and school-first routes |
| Construction site | Service evidence | Record construction-site volume and service conditions |
| Office plaza | Service evidence | Record office-plaza food margin and repeat-customer value |
| Host-access windows | Operating constraints | Hold the host-access windows and drive constraints that limit setup |
| Time setup and teardown at the current stop | Stops to test | Time setup and teardown once at the current stop |
| Office plaza food margin | Service evidence | Compare margin with the construction site's volume |
| School demand peaks earlier | Service evidence | Record when the school stop earns or loses its place in the route |
| Eleven-o'clock hard stop | Operating constraints | Keep setup, driving, and service inside the actual morning |
Available today
Available today: Construction, office, or school-first route becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Route-choice brief: Place sales mix, setup, travel, host access, waste, and repeat-customer value together. Live choice: Whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu.. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Farah will decide whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu.” Activity can preserve this attributed receipt: “Ava separated facts, assumptions, and unanswered questions in Card Chat using the Route-choice brief and this Card Room's visible notes and left “Construction, office, or school-first route” with Farah.”
A useful Card Chat request would be: “Help me prepare for Construction, office, or school-first route using only this Card Room and the Route-choice brief. Separate facts, assumptions, and unanswered questions; stop before the final call.” 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.
Farah's call remains explicit: Farah chooses the route, drives and operates the cart, handles food and money, and owns every host and customer promise.
| Surface | Job in this example |
|---|---|
| Stage | Route-choice brief: Place sales mix, setup, travel, host access, waste, and repeat-customer value together. Live choice: Whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu. |
| Chat | Keep Farah's request and Ava's attributed response with the work |
| Pulse | Open decision: Farah will decide whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu |
| Activity | Ava separated facts, assumptions, and unanswered questions in Card Chat using the Route-choice brief and this Card Room's visible notes and left “Construction, office, or school-first route” with Farah |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Construction, office, or school-first route” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Farah 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 Farah, watch other Lists, or act outside this Card Room.
Farah chooses the route, drives and operates the cart, handles food and money, and owns every host and customer promise. Ava does not operate the cart, navigate, sell, or contact anyone.
Farah finishes “Time setup and teardown at the current stop,” keeps “Construction site” beside “Construction, office, or school-first route,” and does not treat “Host-access windows” as completed or sent before doing the work.
- Request idea: help me prepare for Construction, office, or school-first route using only this Card Room and the Route-choice brief. Separate facts, assumptions, and unanswered questions; stop before the final call.
- Request idea: use only the Route-choice brief and notes the Owner has placed in this Card Room to name the missing evidence for each option
- Request idea: name which visible Room note could most change the facts / assumptions / unanswered-questions split; do not watch other Lists or follow up autonomously
A sales total sheet may still be enough
A sales total sheet is enough when “Office plaza” and “Host-access windows” no longer change the “Construction, office, or school-first route” choice.
It starts to break when “Construction site” and “Host-access windows” must inform the same choice.
The Morning route Board earns its place only when the familiar tool—a sales total sheet—can no longer keep the reason, Route-choice brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Farah should rename every List or Card that feels artificial. This recipe succeeds when “Construction, office, or school-first route” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Write the mission | Build a repeatable morning route that keeps one strong promise instead of chasing every crowd |
| 2. Open the live choice | Put “Construction, office, or school-first route” in a Room of its own |
| 3. Attach the evidence | Route-choice brief: Place sales mix, setup, travel, host access, waste, and repeat-customer value together. Live choice: Whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu. |
| 4. Keep the work owned | Keep “Host-access windows” in owned work and name the next visible move |
| 5. Take the first owned action | Time setup and teardown at the current stop |
Direction
Direction, not a current promise
Over time, Ava may connect evidence produced by “Host-access windows” with the Route-choice brief, summarize what moved inside “Construction, office, or school-first route,” and stop before the named Owner decides.
A future unified You.one experience could carry relevant context from “Construction, office, or school-first route” 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
- Farah is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This fictional example is not food-safety, traffic, site-access, licensing, pricing, or local-permit advice; the operator verifies every real route and operating requirement.
- It does not show Ava completing external actions or contacting anyone for Farah.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.