Example
How to plan a destination wedding without losing guest count, rooms, and a weather backup
Brooke and her partner love a coastal bluff three time zones away, but the hold expires Friday and the restaurant suggested by family has no capacity number. They must keep the bluff with the included indoor room, move the ceremony earlier, or investigate the restaurant before calling it a backup.
Lock a weekend that guests can actually reach, with rooms counted and a wind plan that is a place rather than a hope
Guest-reachable weekend and a real backup place
Keep travel and a backup place beside the bluff photo
Guests, travel, and rooms
Show beds against names
Venue hold, weather, backup
Compare keep-with-backup, earlier-ceremony, and restaurant-after-capacity-check
Keep a suggested backup as owned research until Brooke chooses whether to check it
Ground the bluff-with-backup path in the indoor room already named by the venue
Ground the earlier-hour option in the weather risk already identified for the bluff
Photographer and others with hard times
Hold a hard constraint against a Sunday dream
The venue hold that expires Friday
Name the clock that packing a mood board will not extend
The Wedding weekend Board separates people and rooms, place facts, vendor clocks, and the hold that is genuinely expiring.
Open Choose bluff, earlier hour, or restaurant as the decision Room, with the Ceremony-path brief and the still-unknown restaurant capacity.
After an explicit Card mention, Ava can compare only the visible Room notes. Brooke and her partner own guests, vendors, weather judgment, spending, every message, and every booking; Ava does not contact or book.
A hold is not a wedding, and a bluff is not a backup
The mission is specific: Lock a weekend that guests can actually reach, with rooms counted and a wind plan that is a place rather than a hope.
The consequential choice is not something a board or an AI should quietly make: Whether to keep the bluff and name an indoor backup, move the ceremony earlier in the day, or change to the restaurant parents mentioned after checking its capacity.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose bluff, earlier hour, or restaurant” decision visible through its Superboard view. Brooke still owns the call: Brooke and her partner choose the place, talk to vendors and guests, and own spending.
Available today
Wedding weekend: the working map
The Wedding weekend Board gives this mission one durable operating picture. Brooke can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.
The Lists separate what Brooke can move now, what is evidence, what is already waiting on a named person or event, and what still needs a decision.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Mission | Guest-reachable weekend and a real backup place |
| People | Guests, travel, and rooms |
| Place | Venue hold, weather, backup |
| Vendors | Photographer and others with hard times |
| Replies and outside conditions | The venue hold that expires Friday |
Available today
Open one decision: Choose bluff, earlier hour, or restaurant
Opening the Card gives the visible item durable depth. Stage can hold Ceremony-path brief: Place hold expiry, photographer Saturday, wind, the included indoor room, unknown restaurant capacity, and the three place options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Brooke and her partner will choose a place that survives wind.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose bluff, earlier hour, or restaurant” from the visible evidence. Ava can work from the context Brooke deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Brooke's call remains explicit: Brooke and her partner choose the place, talk to vendors and guests, and own spending.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Ceremony-path brief: Place hold expiry, photographer Saturday, wind, the included indoor room, unknown restaurant capacity, and the three place options on one page |
| Chat | Keep Brooke's request and Ava's attributed response with the work |
| Pulse | Open decision: Brooke and her partner will choose a place that survives wind |
Useful Ava requests, with the boundary intact
These requests stay with the facts Brooke has made visible around “Choose bluff, earlier hour, or restaurant.” Brooke 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 Brooke, watch other work on her own, or contact anyone.
Brooke owns vendors, guests, and spending. Ava does not contact venues, send invitations, or book travel.
A weekend with a place: the hold has a clock, rooms are counted, and a restaurant is a checked backup or it is not.
- Request idea: using only the context visible in this Card Room, compare keeping the bluff with a backup, moving earlier, and checking the restaurant. Do not contact vendors or choose for me.
- Request idea: use only the Ceremony-path brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Choose bluff, earlier hour, or restaurant,” show which visible fact could reverse the current choice
The limit of a mood board plus a guest spreadsheet
A mood board plus a guest spreadsheet can be enough while the situation stays simple: the venue is local and the weather is irrelevant.
It starts to break when a Friday hold, a Saturday-only photographer, and an uncounted restaurant share one weekend.
The Wedding weekend Board earns its place only when the familiar tool—a mood board plus a guest spreadsheet—can no longer keep the reason, Ceremony-path brief, conversation, current state, decision, and history connected.
A practical way to start the Wedding weekend Board
Brooke should rename every List or Card that feels artificial. This recipe succeeds when “Choose bluff, earlier hour, or restaurant” 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. Put holds and vendor clocks on the Board | Friday and Saturday-only |
| 2. Count rooms against names | Beds are a constraint |
| 3. Name a backup place | Capacity included |
| 4. Keep unknown capacities owned | A suggested restaurant is research until someone requests an answer |
| 5. Choose bluff, earlier hour, or restaurant | Open a Room before the hold expires |
Where this example stops
- This is a fictional example, not a customer story.
- This is not wedding-planning, legal, or travel-booking advice.
- It does not show Ava contacting vendors or guests.
- It is not a measured event result.