Example
How to propose a riverfront-cleanup posture when rain and sharps exceed volunteer authority
Rain can send thirty-six untrained volunteers toward a shoreline where volunteers may only report sharps, and the city has not yet said how reported sharps will be collected.
AI assistance helped shape this fictional example from a structured editorial brief. It was reviewed for usefulness, distinctness, accessibility, and product truth.
Propose one event posture with safe access limits and a report path for hazards volunteers must not handle
Purpose, boundaries, and the definition of enough
Hold the mission and boundary: propose one event posture with safe access limits and a report path for hazards volunteers must not handle
State the non-negotiable handling limit
The decision and preparation that deserve attention next
Hold the live choice—whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow—so Olivier can decide from the evidence in this Room
Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed
Use the result of the first owned action to update the Access-scope brief; record the finding, not merely the effort
The visible proof behind the plan—not a vague feeling of readiness
Keep the shoreline hazard map beside the four trained volunteers so rain cannot slide thirty-six untrained people into a report-only zone
Keep total turnout beside the restricted shoreline
Ground the split-zones option in actual trained capacity
Record the dated condition evidence that can rule out the split-zones posture
Keep the volunteer boundary visible
Separate the specialized zone from general cleanup
External answers that matter but should not occupy the active-work List
Record who owns the answer, what was asked, and that city sharps-disposal reply is still unconfirmed
Olivier is an explicitly fictional portrait, not a customer or testimonial.
The Riverfront access zones Board gives one mission a visible field; the Propose cancel, upland-only, or split zones if conditions allow Room keeps its evidence, conversation, state, and decision together.
Current You.one provides the Superboard structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Why Riverfront access zones needs an operating picture
Olivier is a fictional 34-year-old neighborhood volunteer proposing access zones for a riverfront cleanup in Moncton, New Brunswick. Forty people registered, four confirmed volunteers have shoreline-access training, rain is possible, the city supplies bags but not sharps handling, one shoreline section needs trained access, and Olivier has already asked the city how reported sharps will be collected.
Rain changes footing on the one shoreline section that only four confirmed volunteers are trained to enter.
Volunteer no-handling is settled, while the city's collection path for reported sharps is still unanswered.
In You.one's Superboard view, Olivier can give “Propose one event posture with safe access limits and a report path for hazards volunteers must not handle” a Board of its own. That Board connects community promises, volunteer capacity, local evidence, and human authority; opening “Propose cancel, upland-only, or split zones if conditions allow” creates a Room for its evidence, discussion, state, and decision.
Riverfront access zones has one live choice: Propose cancel, upland-only, or split zones if conditions allow
The mission is specific: Propose one event posture with safe access limits and a report path for hazards volunteers must not handle.
The consequential choice is not something a board or an AI should quietly make: Whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow.
You.one can keep the work, evidence, live dependency, and “Propose cancel, upland-only, or split zones if conditions allow” decision visible through its Superboard view. The Owner boundary stays explicit: Olivier can propose canceling the event, an upland-only event, or split zones if conditions allow. Event leadership owns the event decision, the city owns sharps collection, untrained volunteers may not handle sharps, and Ava cannot contact the city or handle hazards.
Available today
Riverfront access zones: one Board shape to adapt
The Riverfront access zones Board gives this mission one durable operating picture. Olivier 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.
| List | What belongs here |
|---|---|
| Safe-use promise | Purpose, boundaries, and the definition of enough |
| Zone actions | The decision and preparation that deserve attention next |
| Site evidence | The visible proof behind the plan—not a vague feeling of readiness |
| Waiting on city | External answers that matter but should not occupy the active-work List |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Olivier's situation: “Propose cancel, upland-only, or split zones if conditions allow” is the live choice, “Shoreline hazard map” holds evidence, and “City sharps-disposal reply” names something genuinely in motion outside Olivier's control. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| No bag count is worth sending an untrained volunteer toward sharps or onto unstable shoreline | Safe-use promise | Hold the mission and boundary: propose one event posture with safe access limits and a report path for hazards volunteers must not handle |
| Propose cancel, upland-only, or split zones if conditions allow | Zone actions | Hold the live choice—whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow—so Olivier can decide from the evidence in this Room |
| Shoreline hazard map | Site evidence | Keep the shoreline hazard map beside the four trained volunteers so rain cannot slide thirty-six untrained people into a report-only zone |
| Draft the zone briefing | Zone actions | Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed |
| City sharps-disposal reply | Waiting on city | Record who owns the answer, what was asked, and that city sharps-disposal reply is still unconfirmed |
| Mark general and trained boundaries on the hazard map against city handling limits | Zone actions | Use the result of the first owned action to update the Access-scope brief; record the finding, not merely the effort |
| Registered headcount: forty | Site evidence | Keep total turnout beside the restricted shoreline |
| Confirmed shoreline-trained volunteers: four | Site evidence | Ground the split-zones option in actual trained capacity |
| Rain and footing observations for the shoreline section | Site evidence | Record the dated condition evidence that can rule out the split-zones posture |
| General volunteers are not sharps trained | Site evidence | Keep the volunteer boundary visible |
| Sharps are report-only for this event | Safe-use promise | State the non-negotiable handling limit |
| Shoreline section requires trained access | Site evidence | Separate the specialized zone from general cleanup |
Available today
Available today: Propose cancel, upland-only, or split zones if conditions allow becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Access-scope brief: Place rain conditions, trained access, volunteer mix, sharps, and city disposal authority together. Live choice: Whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow.. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Olivier will decide whether to propose canceling the event, an upland-only event with the shoreline closed, or split zones for four trained and thirty-six general volunteers if conditions allow.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Access-scope brief and this Card Room's visible notes and left “Propose cancel, upland-only, or split zones if conditions allow” with Olivier.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare proposing event cancellation, an upland-only event with the shoreline closed, and split zones for four trained and thirty-six general volunteers if conditions allow. Cite only notes visible in this Room. Do not cancel the event, contact the city, handle hazards, or choose the posture 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.
Olivier's call remains explicit: Olivier can propose canceling the event, an upland-only event, or split zones if conditions allow. Event leadership owns the event decision, the city owns sharps collection, untrained volunteers may not handle sharps, and Ava cannot contact the city or handle hazards.
| Surface | Job in this example |
|---|---|
| Stage | Access-scope brief: Place rain conditions, trained access, volunteer mix, sharps, and city disposal authority together. Live choice: Whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow. |
| Chat | Keep Olivier's request and Ava's attributed response with the work |
| Pulse | Open decision: Olivier will decide whether to propose canceling the event, an upland-only event with the shoreline closed, or split zones for four trained and thirty-six general volunteers if conditions allow |
| Activity | Ava compared the options in Card Chat using the Access-scope brief and this Card Room's visible notes and left “Propose cancel, upland-only, or split zones if conditions allow” with Olivier |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Propose cancel, upland-only, or split zones if conditions allow” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Olivier 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 Olivier, watch other Lists, or act outside this Card Room.
Olivier can propose canceling the event, an upland-only event, or split zones if conditions allow. Event leadership owns the event decision, the city owns sharps collection, untrained volunteers may not handle sharps, and Ava cannot contact the city or handle hazards.
Olivier finishes “Mark general and trained boundaries on the hazard map against city handling limits,” keeps “Shoreline hazard map” beside “Propose cancel, upland-only, or split zones if conditions allow,” and does not treat “City sharps-disposal reply” as resolved before the outside answer arrives.
- Request idea: using only the context visible in this Card Room, compare proposing event cancellation, an upland-only event with the shoreline closed, and split zones for four trained and thirty-six general volunteers if conditions allow. Cite only notes visible in this Room. Do not cancel the event, contact the city, handle hazards, or choose the posture for me.
- Request idea: use only the Access-scope 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 shoreline site map may still be enough
A shoreline site map is enough when sharps reporting and trained shoreline access are already set for the current weather.
It starts to break when “Shoreline hazard map” and “City sharps-disposal reply” must inform the same choice.
The Riverfront access zones Board earns its place only when the familiar tool—a shoreline site map—can no longer keep the reason, Access-scope brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Olivier should rename every List or Card that feels artificial. This recipe succeeds when “Propose cancel, upland-only, or split zones if conditions allow” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Write the mission | Propose one event posture with safe access limits and a report path for hazards volunteers must not handle |
| 2. Open the live choice | Put “Propose cancel, upland-only, or split zones if conditions allow” in a Room of its own |
| 3. Attach the evidence | Access-scope brief: Place rain conditions, trained access, volunteer mix, sharps, and city disposal authority together. Live choice: Whether Olivier should propose canceling the event, propose an upland-only event with the shoreline closed, or propose split zones for four trained and thirty-six general volunteers if conditions allow. |
| 4. Name the live dependency | Keep “City sharps-disposal reply” visibly waiting |
| 5. Take the first owned action | Mark general and trained boundaries on the hazard map against city handling limits |
Direction
Direction, not a current promise
The useful future step is timely orientation: Ava may surface “Propose cancel, upland-only, or split zones if conditions allow” when “City sharps-disposal reply” changes, explain what changed in the Access-scope brief, and stop at the named Owner's authority boundary.
A future unified You.one experience could carry relevant context from “Propose cancel, upland-only, or split zones if conditions allow” 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.
What this realistic example does not claim
- Olivier is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This fictional example is not environmental, medical, hazardous-material, weather, or municipal safety advice; event leadership, trained professionals, and the city own real decisions and hazard handling.
- It does not show Ava completing external actions or contacting anyone for Olivier.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.