Example
How to run a faith-community service project without losing meals, rides, or the signup sheet
Miriam's problem is not a lack of effort. It is that Deliver this year’s meals with a current household list, enough drivers, and a kitchen schedule—without doubling volume by slogan 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.
Miriam is an explicitly fictional portrait, not a customer or testimonial.
The December meals Board gives one mission a visible field; the Choose count versus drivers 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.
Miriam's pressure is ordinary—and still heavy
Miriam is a fictional 58-year-old volunteer organizing a week of meal delivery from a congregation in Richmond, Virginia. Miriam’s community delivers meals each December. The kitchen is booked, fourteen cooks signed up, and two drivers dropped out. A list of recipient households from last year may be stale. Someone suggested doubling the number of meals.
Miriam can cook. Delivery fails when the signup sheet is treated as a fleet and the household list is treated as current.
A paper signup, a kitchen calendar, and last year’s address list do not share Tuesday.
Doubling meals sounds generous and would strand food if drivers stay at the reduced number.
A last-year list is not this year’s households, and cooks are not drivers
The mission is specific: Deliver this year’s meals with a current household list, enough drivers, and a kitchen schedule—without doubling volume by slogan
The consequential choice is not something a board or an AI should quietly make: Whether to keep last year’s household count, reduce stops to match two fewer drivers, or recruit two drivers before changing the meal count
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Miriam still owns the purpose, tradeoff, and final call.
Available today
December meals: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Miriam 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 year’s count and the cooks-are-not-drivers rule |
| Kitchen | Cooks, shifts, and the booked room |
| Delivery | Drivers, routes, and cars |
| Households | Current addresses versus last year’s list |
| Waiting | Address confirmations and driver asks |
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 Miriam would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| This year’s list, this year’s cars | Mission | Keep driver count beside the urge to double meals |
| Choose count versus drivers | Delivery | Compare keep-count, reduce-stops, and recruit-drivers-first options |
| Two drivers dropped out | Delivery | Name the gap a generous slogan wants to ignore |
| Last year’s address list | Households | Mark a list that has not been confirmed |
| Kitchen booked: fourteen cooks | Kitchen | Show that cooking capacity is not the constraint |
| Household confirmations | Waiting | Keep unconfirmed addresses from filling routes |
Available today
Available today: Choose count versus drivers becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Scale brief: Place driver gap, stale list, and keep / reduce / recruit-first options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Miriam to choose a scale that cars can actually deliver. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare keeping last year’s count, reducing stops, and recruiting drivers before changing volume. Do not contact households 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.
Miriam's call remains explicit: Miriam’s community chooses the scale, talks to drivers and households, and owns the meals
| Surface | Job in this example |
|---|---|
| Stage | Scale brief: Place driver gap, stale list, and keep / reduce / recruit-first options on one page |
| Chat | Keep Miriam's request and Ava's attributed response with the work |
| Pulse | Waiting for Miriam to choose a scale that cars can actually deliver |
| 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.
The community owns meals, contacts, and routes. Ava does not contact households, drive, or give dietary advice.
The modest outcome is not that Ava lives Miriam's life. The modest outcome is a week that can be driven: cooks are not mistaken for cars, last year’s list is a confirmation job, and volume is a decision.
- Request idea: summarize kitchen, delivery, and household Cards already on the Board
- Request idea: compare scale options using driver count Miriam captured
- Request idea: help keep unconfirmed addresses in Waiting
A paper signup plus last year’s addresses may still be enough
A paper signup plus last year’s addresses is enough when drivers and households are unchanged
It starts to break when two drivers are gone and someone wants to double the food
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 Miriam'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. Separate cooks and drivers | Different jobs |
| 2. Confirm this year’s households | Last year’s list is a starting point |
| 3. Count cars | Dropped drivers are a gap |
| 4. Park confirmations | Addresses in Waiting |
| 5. Decide scale | Open a Room before doubling food stranded on a counter |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when meal count exceeds driver Cards, still leaving every route with Miriam.
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
- Miriam is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not dietary, medical, or charitable-registration advice.
- It does not show Ava contacting households or driving deliveries.
- It is not a measured service result.