How to run a local mutual-aid drive without losing requests, offers, or privacy

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, and Sasha has already asked the posters to clarify. Sasha has also asked whether the couch is still available and whether a first name may be shared. Nobody asked Sasha to decide who deserves help.

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.

In You.one's Superboard view, Sasha can give “Match this week’s offers to requests with consent, keep duplicates visible, and refuse to turn the Board into a ranking of neighbors” a Board of its own. That Board connects community promises, volunteer capacity, local evidence, and human authority; opening “Choose public list, private match, or pause” creates a Room for its evidence, discussion, state, and decision.

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.

You.one can keep the work, evidence, live dependency, and “Choose public list, private match, or pause” decision visible through its Superboard view. The Owner boundary stays explicit: Sasha and neighbors choose matches; Sasha owns messages and privacy. The Board does not judge need.

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.

Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Sasha's situation: “Choose public list, private match, or pause” is the live choice, “Two grocery requests might be one household” holds evidence, and “Duplicate grocery-request clarification reply” names something genuinely in motion outside Sasha's control. The point is recognition, not a perfect taxonomy.

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.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Matching-posture brief and this Card Room's visible notes and left “Choose public list, private match, or pause” with Sasha.”

A useful Card Chat request would be: “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.” 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.

Sasha's call remains explicit: Sasha and neighbors choose matches; Sasha owns messages and privacy. The Board does not judge need.

These requests use the visible supported context inside the “Choose public list, private match, or pause” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Sasha 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 Sasha, watch other Lists, or act outside this Card Room.

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: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

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.

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.

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.

Later, Ava may help this Board notice when an offer Card has no remaining availability note, still leaving every message with Sasha.

A future unified You.one experience could carry relevant context from “Choose public list, private match, or pause” 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.

• Sasha is fictional and is not a customer, testimonial, research participant, or disguised real person.
• 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.