Example
How to run a local mutual-aid drive without losing requests, offers, or privacy
Sasha’s neighborhood chat contains rides, groceries, and a couch, but two requests may be duplicates and current availability is unclear. Neighbors must choose a public offer list, private consent-based matching, or a pause until clarification—without deciding who deserves help.
Match this week’s offers to requests with consent, keep duplicates visible, and refuse to turn the Board into a ranking of neighbors
This week’s matching job and the no-ranking rule
Keep the storm week’s job beside the line that the Board does not decide desert
Compare open-offer list, private consent matching, and pause-for-duplicates
Asks with consent notes, not judgments
Flag a possible duplicate without investigating anyone’s life
Current offers with remaining availability, not stale chat yeses
Hold a specific remaining offer so it does not vanish in chat
Consent, duplicate-check, and still-available replies
Keep the pause option tied to a clarification Sasha already requested
Reconfirm before treating a chat message as open housing
Keep privacy as a step, not an afterthought
The Storm-week matches Board holds requests, current offers, consent, and replies without becoming an eligibility or ranking system.
Open Choose public list, private match, or pause as a Room with the Matching-posture brief and the privacy facts.
Ava can organize only what Sasha provides. Neighbors own requests, offers, consent, privacy, and every match; Ava does not message, allocate, rank need, or give emergency, housing, legal, medical, or financial advice.
A chat is not a match log, and a coordinator is not a judge
What belongs together 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 judgment remains human: Whether to post a simple open-offer list, match privately with consent, or pause public matching until duplicate requests are clarified.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose public list, private match, or pause” decision visible through its Superboard view. Sasha still owns the call: Sasha and neighbors choose matches; Sasha owns messages and privacy. The Board does not judge need.
What changes after a neighborhood chat thread
A neighborhood chat thread can be enough while the situation stays simple: two people already found each other.
It starts to break when duplicate asks, vanishing offers, and a ranking comment share one storm week.
The Storm-week matches Board earns its place only when the familiar tool—a neighborhood chat thread—can no longer keep the reason, Matching-posture brief, conversation, current state, decision, and history connected.
Available today
A focused Storm-week matches Board
The Storm-week matches Board gives this mission one durable operating picture. Sasha 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.
The point is a fast scan: what is moving, what is known, what is unresolved, and what Sasha must choose. Questions not yet asked stay with Sasha; they do not move to a list for outside replies.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Mission | This week’s matching job and the no-ranking rule |
| Requests | Asks with consent notes, not judgments |
| Offers | Current offers with remaining availability, not stale chat yeses |
| Replies and outside conditions | Consent, duplicate-check, and still-available replies |
Available today
Inside the “Choose public list, private match, or pause” Room
Opening the Card gives the visible item durable depth. Stage can hold Matching-posture brief: Place duplicate risk, the Thursday ride offer, the couch still-available reply, first-name sharing consent, 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 “Open decision: Sasha will choose a matching posture that does not rank people.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose public list, private match, or pause” from the visible evidence. Ava can work from the context Sasha deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Sasha's call remains explicit: Sasha and neighbors choose matches; Sasha owns messages and privacy. The Board does not judge need.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Matching-posture brief: Place duplicate risk, the Thursday ride offer, the couch still-available reply, first-name sharing consent, and public / private / pause options on one page |
| Chat | Keep Sasha's request and Ava's attributed response with the work |
| Pulse | Open decision: Sasha will choose a matching posture that does not rank people |
What Ava can prepare from visible context
These requests stay with the facts Sasha has made visible around “Choose public list, private match, or pause.” Sasha supplies the evidence, checks Ava's work, and decides what belongs in the Room.
Current Ava can prepare help after an explicit request. She cannot make the choice, represent Sasha, watch other work on her own, or contact anyone.
Neighbors own what they offer and ask. Ava does not message people, rank need, or give legal, medical, or financial advice.
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: using only the context visible in this Card Room, compare an open-offer list, private matching with consent, and pausing until duplicates are clarified. Do not message neighbors or choose for me.
- Request idea: use only the Matching-posture brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: from “Choose public list, private match, or pause,” draft a short decision note and name Sasha as the decider
A starter shape, not a prescribed workflow
Sasha should rename every List or Card that feels artificial. This recipe succeeds when “Choose public list, private match, or pause” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
Swipe or scroll sideways to see every column.
| 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 public list, private match, or pause | Open a Room before a ranking comment becomes the method |
Where this example stops
- This is a fictional example, not a customer story.
- This is not social-work, legal, medical, financial, housing, shelter, or emergency-management 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.