Example
How to run a local mutual-aid drive without losing requests, offers, or privacy
Sasha's problem is not a lack of effort. It is that Match this week’s offers to requests with consent, keep duplicates visible, and refuse to turn the Board into a ranking of neighbors 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.
Sasha is an explicitly fictional portrait, not a customer or testimonial.
The Storm-week matches Board gives one mission a visible field; the Choose public list, private match, or pause 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.
Sasha's pressure is ordinary—and still heavy
Sasha is a fictional 29-year-old neighbor coordinating a one-week mutual-aid drive in Saint John, New Brunswick. Sasha’s neighborhood chat filled with ride offers, grocery asks, and a couch. A storm is coming. Two requests look similar and might be the same household. Nobody asked Sasha to decide who deserves help.
Sasha can organize information. The week fails if offers vanish, requests duplicate, or the Board starts ranking people.
A chat thread, a notes app, and a paper on a fridge do not show which offer is still open.
A well-meant comment asked who “needs it more.” That question does not belong to a Board.
A chat is not a match log, and a coordinator is not a judge
The mission is specific: Match this week’s offers to requests with consent, keep duplicates visible, and refuse to turn the Board into a ranking of neighbors
The consequential choice is not something a board or an AI should quietly make: Whether to post a simple open-offer list, match privately with consent, or pause public matching until duplicate requests are clarified
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Sasha still owns the purpose, tradeoff, and final call.
Available today
Storm-week matches: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Sasha 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 matching job and the no-ranking rule |
| Requests | Asks with consent notes, not judgments |
| Offers | Rides, food, and space still actually available |
| Matches | Pairs that both people agreed to |
| Waiting | Consent and duplicate-check replies |
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 Sasha would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Match, do not rank | Mission | Keep the storm week’s job beside the line that the Board does not decide desert |
| Choose public list, private match, or pause | Matches | Compare open-offer list, private consent matching, and pause-for-duplicates |
| Two grocery requests might be one household | Requests | Flag a possible duplicate without investigating anyone’s life |
| Ride offer Thursday afternoon | Offers | Hold a specific remaining offer so it does not vanish in chat |
| Couch offer: still available? | Waiting | Reconfirm before treating a chat message as open housing |
| Consent to share a first name | Waiting | Keep privacy as a step, not an afterthought |
Available today
Available today: Choose public list, private match, or pause becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Matching-posture brief: Place duplicate risk, open offers, and public / private / pause options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Sasha to choose a matching posture that does not rank people. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare an open-offer list, private matching with consent, and pausing until duplicates are clarified. Do not message neighbors 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.
Sasha's call remains explicit: Sasha and neighbors choose matches; Sasha owns messages and privacy. The Board does not judge need.
| Surface | Job in this example |
|---|---|
| Stage | Matching-posture brief: Place duplicate risk, open offers, and public / private / pause options on one page |
| Chat | Keep Sasha's request and Ava's attributed response with the work |
| Pulse | Waiting for Sasha to choose a matching posture that does not rank people |
| 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.
Neighbors own what they offer and ask. Ava does not message people, rank need, or give legal, medical, or financial advice.
The modest outcome is not that Ava lives Sasha's life. The modest outcome is a week of matches without a ranking: offers stay visible, possible duplicates are flagged, and the Board has not been asked who deserves help.
- Request idea: summarize requests, remaining offers, and waiting consent already on the Board
- Request idea: compare matching postures using duplicate flags Sasha captured
- Request idea: help keep privacy consent in Waiting until it exists
A neighborhood chat thread may still be enough
A neighborhood chat thread is enough when two people already found each other
It starts to break when duplicate asks, vanishing offers, and a ranking comment share one storm week
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 Sasha'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 no-ranking rule | The Board matches information |
| 2. Capture asks with consent | Privacy is a step |
| 3. Keep offers current | A chat yes can go stale |
| 4. Flag duplicates without investigating lives | Ask, do not surveil |
| 5. Choose a matching posture | Open a Room before a ranking comment becomes the method |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when an offer Card has no remaining availability note, still leaving every message with Sasha.
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
- Sasha is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not social-work, legal, medical, or financial advice, and it is not an eligibility system.
- It does not show Ava contacting neighbors or allocating resources as an authority.
- It is not a measured aid result or a claim about any real neighborhood.