Example
How to run co-parenting weekly logistics without using a Board as a referee
Chris's problem is not a lack of effort. It is that Give Chris one maintained picture of this week’s handoffs, activities, and exceptions to use in real conversations—without implying the other household accesses the Board or treating it as a referee or legal record 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.
Chris is an explicitly fictional portrait, not a customer or testimonial.
The This week’s shared logistics Board gives one mission a visible field; the Choose the Thursday exception 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.
Chris's pressure is ordinary—and still heavy
Chris is a fictional 37-year-old parent sharing a weekly schedule with another household in Victoria, British Columbia. Chris and the other household already have an agreed week-on pattern. What fails is the weekly layer: soccer location changes, a prescription pickup listed on a bottle, and a Thursday work trip. Texts turn into a second argument about who saw the change.
Chris is not asking software to parent. They need one picture of this week’s handoff, kit, and exceptions so a location change is not discovered at the field.
The school app, a team email, and two phone calendars currently all hold a different pickup time.
A work trip is approved. The swap ask has not been sent, and the bag still lives in the other hallway.
The Board holds the week; it does not adjudicate the relationship
The mission is specific: Give Chris one maintained picture of this week’s handoffs, activities, and exceptions to use in real conversations—without implying the other household accesses the Board or treating it as a referee or legal record
The consequential choice is not something a board or an AI should quietly make: Whether to ask for a Thursday swap, offer Saturday instead, or keep the pattern and use a neighbor already on the pickup list
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Chris still owns the purpose, tradeoff, and final call.
Available today
This week’s shared logistics: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Chris 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 | This week’s pattern and the line that the Board is not a referee |
| Handoffs | Times, places, and bags |
| Activities | Practices, school events, and location changes |
| Exceptions | Work trips and other breaks in the usual week |
| Waiting | Swap asks and confirmations |
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 Chris would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| One week Chris can scan | Mission | Keep the agreed pattern visible for the one Owner maintaining this Board; judgment and communication stay with the parents |
| Choose the Thursday exception | Exceptions | Compare swap, Saturday offer, and neighbor pickup |
| Wednesday soccer location change | Activities | Hold the new field from the team email on the same Board as pickup |
| Thursday work trip | Exceptions | Show the travel that breaks the usual handoff |
| Handoff bag checklist | Handoffs | Keep kit, school notes, and the bottle-label pickup date in one list |
| Swap ask not yet sent | Waiting | Prevent an unsent message from counting as a plan |
Available today
Available today: Choose the Thursday exception becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Exception brief: Place the work trip, soccer change, and the swap / Saturday / neighbor options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Chris to choose how Thursday is covered. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare a Thursday swap, a Saturday offer, and neighbor pickup. Do not message anyone 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.
Chris's call remains explicit: Chris owns the message to the other household, any neighbor ask, and every parenting judgment. The Board does not adjudicate.
| Surface | Job in this example |
|---|---|
| Stage | Exception brief: Place the work trip, soccer change, and the swap / Saturday / neighbor options on one page |
| Chat | Keep Chris's request and Ava's attributed response with the work |
| Pulse | Waiting for Chris to choose how Thursday is covered |
| 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.
Chris and the other parent own agreements, messages, and care. Ava does not give legal advice, send messages, or act as an authority.
The modest outcome is not that Ava lives Chris's life. The modest outcome is a week Chris can scan and communicate clearly: the field change is on the Board, Thursday has a chosen path, and software has not been asked to referee or act as a shared calendar.
- Request idea: summarize handoffs, activities, and exceptions already on the Board
- Request idea: compare Thursday options using the work trip and activity Cards Chris captured
- Request idea: help keep unsent swap asks in Waiting
Two phone calendars plus text may still be enough
Two phone calendars plus text is enough when the week has no exceptions
It starts to break when a field change, a work trip, and an unsent swap all disagree
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 Chris'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. State the line | The Board is a weekly picture, not a referee |
| 2. Card handoffs | Times, places, and bags |
| 3. Add this week’s activities | Including location changes from team or school notes |
| 4. Mark exceptions | Work trips and breaks in the usual pattern |
| 5. Decide coverage | Open a Room before an unsent text becomes the plan |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when an exception Card has no coverage, still leaving every message with the parents.
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
- Chris is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not legal, custody, or parenting advice, and it is not an official record.
- It does not show Ava messaging the other household or deciding a schedule.
- It is not a measured family outcome.