Example
How a pet sitter can handle holiday bookings without promising overlapping houses
Casey wants to be reliable. Reliability here is geography, keys, and overnight needs—not a cheerful yes in a text.
Cover holiday bookings that one person can actually reach, with keys and printed care notes attached, without stacking two overnights
Ten-day capacity and the no-two-overnights rule
Keep geography and overnight limits beside booking appetite
Each home with nights versus drop-ins
Hold a true overnight so a drop-in cannot pretend to fit those nights
Keep the second accepted house-sit visible in the ten-day route
Keep the third and farthest accepted house-sit visible in the ten-day route
Printed times, feeding, and vet contacts as written
Keep label times visible without turning them into veterinary advice
Keys, codes, and parking
Make access a job, not a notes-app title
Requests Casey has not accepted or declined
Compare decline-both, near-side-only, and across-bridge-only options against the same three house-sits
Hold the higher-rate far request as one open option, not accepted work
Hold the near-side request as the other open option, not accepted work
Casey is an explicitly fictional portrait, not a customer or testimonial.
The Holiday coverage Board gives one mission a visible field; the Choose the remaining inquiries 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 Holiday coverage needs an operating picture
Casey is a fictional 27-year-old independent pet sitter heading into winter holidays in Tampa, Florida. Casey already has three house-sits over the same ten days. Two more clients want drop-ins. One dog needs medication at times printed on a label. Keys and alarm codes currently live in a notes app titled “don’t lose.”
Texts, a notes app of codes, and a paper calendar do not show travel time between houses.
A client said “just whenever.” The medication label has times. Those are not the same instruction.
In You.one's Superboard view, Casey can give “Cover holiday bookings that one person can actually reach, with keys and printed care notes attached, without stacking two overnights” a Board of its own. That Board connects customer promises, operating evidence, capacity, and the owner's judgment; opening “Choose the remaining inquiries” creates a Room for its evidence, discussion, state, and decision.
Ten days cannot hold five households if two of them need nights
The mission is specific: Cover holiday bookings that one person can actually reach, with keys and printed care notes attached, without stacking two overnights.
The consequential choice is not something a board or an AI should quietly make: Whether to keep the three house-sits and decline both drop-ins, accept only the near-side drop-in, or accept only the higher-rate across-bridge drop-in.
You.one can keep the work, several kinds of evidence, and “Choose the remaining inquiries” decision visible through its Superboard view. The Owner boundary stays explicit: Casey chooses bookings, picks up keys, and owns animal care and client messages.
Available today
Holiday coverage: one Board shape to adapt
The Holiday coverage Board gives this mission one durable operating picture. Casey 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, multiple kinds of evidence, and decisions. 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 |
|---|---|
| Mission | Ten-day capacity and the no-two-overnights rule |
| Houses | Each home with nights versus drop-ins |
| Care notes | Printed times, feeding, and vet contacts as written |
| Keys and access | Keys, codes, and parking |
| Inquiries | Requests Casey has not accepted or declined |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Casey's situation: “Choose the remaining inquiries” is the live choice, while “Overnight: Davis house Dec 22–26 morning handoff” and “Overnight: Ortiz house Dec 29 afternoon–31” hold different facts that can change it. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Ten days, one person, no stacked nights | Mission | Keep geography and overnight limits beside booking appetite |
| Choose the remaining inquiries | Inquiries | Compare decline-both, near-side-only, and across-bridge-only options against the same three house-sits |
| Overnight: Davis house Dec 22–26 morning handoff | Houses | Hold a true overnight so a drop-in cannot pretend to fit those nights |
| Overnight: Lee house Dec 26 afternoon–29 morning | Houses | Keep the second accepted house-sit visible in the ten-day route |
| Overnight: Ortiz house Dec 29 afternoon–31 | Houses | Keep the third and farthest accepted house-sit visible in the ten-day route |
| Medication times as printed | Care notes | Keep label times visible without turning them into veterinary advice |
| Spare key pickup Thursday | Keys and access | Make access a job, not a notes-app title |
| Drop-in inquiry across the bridge | Inquiries | Hold the higher-rate far request as one open option, not accepted work |
| Drop-in inquiry near the Davis route | Inquiries | Hold the near-side request as the other open option, not accepted work |
Available today
Available today: Choose the remaining inquiries becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Capacity map brief: Place all three accepted overnights, both drop-in inquiries, travel, and decline-both / near-only / bridge-only options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Casey will choose holiday capacity.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Capacity map brief and this Card Room's visible notes and left “Choose the remaining inquiries” with Casey.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare declining both drop-ins, accepting only the near-side inquiry, and accepting only the higher-rate across-bridge inquiry. Do not message clients 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.
Casey's call remains explicit: Casey chooses bookings, picks up keys, and owns animal care and client messages.
| Surface | Job in this example |
|---|---|
| Stage | Capacity map brief: Place all three accepted overnights, both drop-in inquiries, travel, and decline-both / near-only / bridge-only options on one page |
| Chat | Keep Casey's request and Ava's attributed response with the work |
| Pulse | Open decision: Casey will choose holiday capacity |
| Activity | Ava compared the options in Card Chat using the Capacity map brief and this Card Room's visible notes and left “Choose the remaining inquiries” with Casey |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose the remaining inquiries” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Casey 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 Casey, watch other Lists, or act outside this Card Room.
Casey owns animal care, keys, and client conversations. Ava does not give veterinary advice, message clients, or hold keys.
A ten-day map one person can walk: overnights are exclusive, keys have pickup jobs, and extra drop-ins are a chosen yes or no.
- Request idea: using only the context visible in this Card Room, compare declining both drop-ins, accepting only the near-side inquiry, and accepting only the higher-rate across-bridge inquiry. Do not message clients or choose for me.
- Request idea: use only the Capacity map 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
A notes app of codes plus texts may still be enough
A notes app of codes plus texts is enough when one house and no medication times.
It starts to break when three overnights and a far drop-in all look like friendly yeses.
The Holiday coverage Board earns its place only when the familiar tool—a notes app of codes plus texts—can no longer keep the reason, Capacity map brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Casey should rename every List or Card that feels artificial. This recipe succeeds when “Choose the remaining inquiries” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Write the overnight rule | Two nights in two houses is not coverage |
| 2. Card each house | Nights versus drop-ins, with travel |
| 3. Attach printed care notes | Times as written, contacts as written |
| 4. Make keys a job | Pickup dates, not a folder named don’t lose |
| 5. Choose the remaining inquiries | Open a Room before a text yes stacks the map |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when two overnight Cards share a date, still leaving every booking with Casey.
A future unified You.one experience could carry relevant context from “Choose the remaining inquiries” 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
- Casey is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not veterinary, legal, or insurance advice.
- It does not show Ava messaging clients or providing animal care.
- It is not a measured booking result.