Skip to content

Example

How to plan a group camping trip without losing permits, gear, and a weather call

Quinn can pack. The weekend fails if gear, cooking, and a storm call live in a chat that already said yes.

Superboard exampleTwo-night camp

Run two nights with sites, tents, and food that match the weather—or delay using the park’s written change window

Mission1

Sites, tents, and a weather call

Tents that match the night

Keep storm Saturday beside the maybe tent car

People and cars2

Who is coming and what they can carry

Car with the big tent: maybe

Name the cancellation risk that the chat already treated as coming

Two first-time campers

Keep skill mix visible without stereotyping anyone as helpless

Gear2

Tents, cook kit, and what is borrowed

Possible second tent to ask for

Keep the extra-tent option as owned work until Quinn sends a specific request

Small tent confirmed

Keep gear already in hand separate from the big-tent car and borrowed-tent maybes

Weather and park3

Forecast, permit, change window

Choose keep, delay, or Friday only

Compare second-tent, delay-weekend, and one-night options

Two site reservations

Attach confirmation numbers and the change window as written

Saturday night storm window

Keep the stated forecast window beside the tent and date choice without treating the Board as weather authority

An illustrative Board built from this fictional scenario. Adapt the Lists and Cards to your own mission.
01

Quinn is an explicitly fictional portrait, not a customer or testimonial.

02

The Two-night camp Board gives one mission a visible field; the Choose keep, delay, or Friday only Room keeps its evidence, conversation, state, and decision together.

03

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 Two-night camp needs an operating picture

Quinn is a fictional 36-year-old friend organizing a two-night group camp in Bend, Oregon. Quinn reserved two sites. Six people said yes. Two have never camped. A storm window moved into Saturday night. The car with the big tent is also the car with a maybe-cancellation.

A park confirmation, a group chat, and a gear closet photo do not share Saturday night.

Canceling feels dramatic. Sleeping six people through a storm in one remaining tent is also a decision.

In You.one's Superboard view, Quinn can give “Run two nights with sites, tents, and food that match the weather—or delay using the park’s written change window” a Board of its own. That Board connects the shared purpose, logistics, preferences, and decisions people still own; opening “Choose keep, delay, or Friday only” creates a Room for its evidence, discussion, state, and decision.

A reservation is not a trip if the tent car is a maybe

The mission is specific: Run two nights with sites, tents, and food that match the weather—or delay using the park’s written change window.

The consequential choice is not something a board or an AI should quietly make: Whether to keep Saturday and bring a second borrowed tent, delay to the following weekend, or drop to a one-night trip Friday only.

You.one can keep the work, evidence, and “Choose keep, delay, or Friday only” decision visible through its Superboard view. The Owner boundary stays explicit: Quinn chooses the dates, talks to the group and park, and owns safety and spending.

Available today

Two-night camp: one Board shape to adapt

The Two-night camp Board gives this mission one durable operating picture. Quinn 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, and decisions while keeping unsent questions in owned work. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.

Two-night camp Board shape
ListWhat belongs here
MissionSites, tents, and a weather call
People and carsWho is coming and what they can carry
GearTents, cook kit, and what is borrowed
Weather and parkForecast, permit, change window

Available today

The Cards make the operating picture concrete

These Card titles come directly from Quinn's situation: “Choose keep, delay, or Friday only” is the live choice, “Two site reservations” holds evidence, and “Car with the big tent: maybe” is still work Quinn controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.

Example Cards for Quinn
CardListJob
Tents that match the nightMissionKeep storm Saturday beside the maybe tent car
Choose keep, delay, or Friday onlyWeather and parkCompare second-tent, delay-weekend, and one-night options
Two site reservationsWeather and parkAttach confirmation numbers and the change window as written
Saturday night storm windowWeather and parkKeep the stated forecast window beside the tent and date choice without treating the Board as weather authority
Car with the big tent: maybePeople and carsName the cancellation risk that the chat already treated as coming
Two first-time campersPeople and carsKeep skill mix visible without stereotyping anyone as helpless
Possible second tent to ask forGearKeep the extra-tent option as owned work until Quinn sends a specific request
Small tent confirmedGearKeep gear already in hand separate from the big-tent car and borrowed-tent maybes

Available today

Available today: Choose keep, delay, or Friday only becomes a Room

Opening the Card gives the visible item durable depth. Stage can hold Weather-call brief: Place storm window, tent-car maybe, park change window, and keep / delay / Friday-only options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Quinn will choose a weather posture that matches tents.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Weather-call brief and this Card Room's visible notes and left “Choose keep, delay, or Friday only” with Quinn.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, compare bringing a second tent, delaying a week, and Friday only. Do not message the group 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.

Quinn's call remains explicit: Quinn chooses the dates, talks to the group and park, and owns safety and spending.

Inside the Choose keep, delay, or Friday only Room
SurfaceJob in this example
StageWeather-call brief: Place storm window, tent-car maybe, park change window, and keep / delay / Friday-only options on one page
ChatKeep Quinn's request and Ava's attributed response with the work
PulseOpen decision: Quinn will choose a weather posture that matches tents
ActivityAva compared the options in Card Chat using the Weather-call brief and this Card Room's visible notes and left “Choose keep, delay, or Friday only” with Quinn

What to ask Ava—and what not to assume

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

Quinn owns safety, bookings, and group messages. Ava does not contact the park, message friends, or give outdoor-safety advice as authority.

A trip with a weather call: the maybe car is named, the park change window is on the Board, and a second tent is real or the date moves.

  • Request idea: using only the context visible in this Card Room, compare bringing a second tent, delaying a week, and Friday only. Do not message the group or choose for me.
  • Request idea: use only the Weather-call 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 group chat plus a park confirmation email may still be enough

A group chat plus a park confirmation email is enough when the tent car is certain and the sky is quiet.

It starts to break when a storm Saturday, a maybe car, and six yeses share two sites.

The Two-night camp Board earns its place only when the familiar tool—a group chat plus a park confirmation email—can no longer keep the reason, Weather-call brief, conversation, current state, decision, and history connected.

A starter recipe to adapt, not obey

Quinn should rename every List or Card that feels artificial. This recipe succeeds when “Choose keep, delay, or Friday only” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Start with the Two-night camp Board
StepAction
1. Attach park confirmationsChange windows as written
2. Card cars and tentsMaybes are not gear
3. Note first-timers as planning factsWithout turning them into a joke
4. Keep a possible tent ownedIt becomes Waiting only after Quinn sends a request
5. Choose keep, delay, or Friday onlyOpen a Room before Saturday night

Direction

Direction, not a current promise

Later, Ava may help this Board notice when a storm Card has no tent coverage, still leaving every go-call with Quinn.

A future unified You.one experience could carry relevant context from “Choose keep, delay, or Friday only” 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

  • Quinn is fictional and is not a customer, testimonial, research participant, or disguised real person.
  • This is not wilderness, weather, or safety authority advice.
  • It does not show Ava contacting a park or messaging the group.
  • It is not a measured trip result.

Use this example as a starting shape—not a claim about your life.

Get early access