Example
How to run a garden growing season without losing seed orders, frost dates, and a water plan
Ruth can plant. The season fails if frost, the trip, and an extra flat of seedlings never share a bed map.
Grow a season that fits four beds, last-frost timing, and one weekend without water—without treating extra seedlings as a fifth bed
Four beds, frost, and the trip week
Keep water coverage beside the seed order
What each bed is for
Protect a planned crop from overflow seedlings
Keep the received offer as bed-capacity evidence rather than a false outside dependency
Start dates and frost range
Keep a range visible so a catalog week cannot pretend to be a date
Trip coverage and soaker
Compare skip-tomatoes, soaker-before-trip, and written-list-neighbor
Name the absence tomatoes would feel
Keep the owned install option visible without implying supplies have been bought or installed
Ground the neighbor-water path as an unsent request Ruth still owns
Ruth is an explicitly fictional portrait, not a customer or testimonial.
The Four-bed season Board gives one mission a visible field; the Choose skip tomatoes, soaker, or neighbor water 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 Four-bed season needs an operating picture
Ruth is a fictional 47-year-old home gardener with four raised beds in Asheville, North Carolina. Ruth ordered seeds in January. Last frost is still a range. A weekend trip sits on the week tomatoes want water daily. A neighbor offered seedlings that would overflow the fourth bed.
A seed catalog, a weather screenshot, and a calendar hold do not share June.
Accepting every seedling feels generous and would shade the peppers she actually wanted.
In You.one's Superboard view, Ruth can give “Grow a season that fits four beds, last-frost timing, and one weekend without water—without treating extra seedlings as a fifth bed” a Board of its own. That Board connects the project's purpose, materials, experiments, and the maker's judgment; opening “Choose skip tomatoes, soaker, or neighbor water” creates a Room for its evidence, discussion, state, and decision.
A seed order is not a calendar, and a trip is not a watering can
The mission is specific: Grow a season that fits four beds, last-frost timing, and one weekend without water—without treating extra seedlings as a fifth bed.
The consequential choice is not something a board or an AI should quietly make: Whether to skip tomatoes this year, install a simple soaker before the trip, or ask the neighbor to water using a written list.
You.one can keep the work, evidence, and “Choose skip tomatoes, soaker, or neighbor water” decision visible through its Superboard view. The Owner boundary stays explicit: Ruth chooses crops, spending, and any neighbor ask, and owns the garden.
Available today
Four-bed season: one Board shape to adapt
The Four-bed season Board gives this mission one durable operating picture. Ruth 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.
| List | What belongs here |
|---|---|
| Mission | Four beds, frost, and the trip week |
| Beds | What each bed is for |
| Timing | Start dates and frost range |
| Water | Trip coverage and soaker |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Ruth's situation: “Choose skip tomatoes, soaker, or neighbor water” is the live choice, “Bed four: peppers” holds evidence, and “Weekend trip in peak water week” is still work Ruth controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Four beds, one trip week | Mission | Keep water coverage beside the seed order |
| Choose skip tomatoes, soaker, or neighbor water | Water | Compare skip-tomatoes, soaker-before-trip, and written-list-neighbor |
| Bed four: peppers | Beds | Protect a planned crop from overflow seedlings |
| Last frost still a range | Timing | Keep a range visible so a catalog week cannot pretend to be a date |
| Weekend trip in peak water week | Water | Name the absence tomatoes would feel |
| Soaker before the trip week | Water | Keep the owned install option visible without implying supplies have been bought or installed |
| Written list if Ruth asks the neighbor to water | Water | Ground the neighbor-water path as an unsent request Ruth still owns |
| Neighbor seedling offer | Beds | Keep the received offer as bed-capacity evidence rather than a false outside dependency |
Available today
Available today: Choose skip tomatoes, soaker, or neighbor water becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Water-week brief: Place trip dates, bed map, and skip / soaker / neighbor options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Ruth will choose a water plan that fits four beds.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Water-week brief and this Card Room's visible notes and left “Choose skip tomatoes, soaker, or neighbor water” with Ruth.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare skipping tomatoes, installing a soaker, and asking the neighbor with a written list. Do not message anyone 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.
Ruth's call remains explicit: Ruth chooses crops, spending, and any neighbor ask, and owns the garden.
| Surface | Job in this example |
|---|---|
| Stage | Water-week brief: Place trip dates, bed map, and skip / soaker / neighbor options on one page |
| Chat | Keep Ruth's request and Ava's attributed response with the work |
| Pulse | Open decision: Ruth will choose a water plan that fits four beds |
| Activity | Ava compared the options in Card Chat using the Water-week brief and this Card Room's visible notes and left “Choose skip tomatoes, soaker, or neighbor water” with Ruth |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose skip tomatoes, soaker, or neighbor water” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Ruth 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 Ruth, watch other Lists, or act outside this Card Room.
Ruth owns planting, spending, and neighbor conversations. Ava does not buy supplies, message the neighbor, or give agronomic advice as authority.
A season that fits: bed four stays peppers or it does not, the trip has a water plan, and extra seedlings are a decision.
- Request idea: using only the context visible in this Card Room, compare skipping tomatoes, installing a soaker, and asking the neighbor with a written list. Do not message anyone or choose for me.
- Request idea: use only the Water-week 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 seed catalog plus a weather screenshot may still be enough
A seed catalog plus a weather screenshot is enough when someone is home every day and beds are empty.
It starts to break when a trip, a frost range, and extra seedlings all claim bed four.
The Four-bed season Board earns its place only when the familiar tool—a seed catalog plus a weather screenshot—can no longer keep the reason, Water-week brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Ruth should rename every List or Card that feels artificial. This recipe succeeds when “Choose skip tomatoes, soaker, or neighbor water” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Map four beds | Jobs, not wishes |
| 2. Put frost as a range | Catalogs are not dates |
| 3. Card the trip week | Water is work |
| 4. Keep extra plants with the bed map | An offer is evidence, not a fifth bed |
| 5. Choose skip tomatoes, soaker, or neighbor water | Open a Room before tomatoes write the vacation |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a trip week has no water Card, still leaving every planting with Ruth.
A future unified You.one experience could carry relevant context from “Choose skip tomatoes, soaker, or neighbor water” 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
- Ruth is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not horticultural, pest, or water-use advice.
- It does not show Ava messaging a neighbor or ordering supplies.
- It is not a measured harvest result.