Example
How to build a family photo archive without losing decades in a hard-drive drawer
Joan can scan. The archive fails if the expiry link, the unlabeled box, and a reunion deadline never share a sequence.
Capture the expiring link, the unlabeled box, and a reunion set without requiring a perfect folder tree first
Expiry, unlabeled box, reunion date
Keep the expiry and unlabeled box ahead of folder perfection
Drives, albums, links
Compare unlabeled-box-next, copy-expiring-link, and reunion-from-done
Hold the pile that is not already titled Wedding
What is actually being copied or scanned
Show the comfortable work that is hiding the box
The six-week album
Keep a delivery from becoming a reason to invent a database
The sibling cloud link's external expiry clock
Name a clock that scanning the wedding will not stop
Joan is an explicitly fictional portrait, not a customer or testimonial.
The Photo decades Board gives one mission a visible field; the Choose box, link, or reunion-only 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 Photo decades needs an operating picture
Joan is a fictional 58-year-old family member gathering photos from several decades in Indianapolis, Indiana. Joan has two hard drives, a box of albums, and a sibling’s cloud link that expires. A reunion wants a shared album in six weeks. She keeps scanning the same wedding because it is labeled.
Two drives, a cloud link, and a cardboard box all claim to be the archive.
Making a perfect taxonomy first would miss the reunion.
In You.one's Superboard view, Joan can give “Capture the expiring link, the unlabeled box, and a reunion set without requiring a perfect folder tree first” a Board of its own. That Board connects the project's purpose, materials, experiments, and the maker's judgment; opening “Choose box, link, or reunion-only” creates a Room for its evidence, discussion, state, and decision.
A labeled wedding is not the unlabeled childhood box, and an expiry link is a clock
The mission is specific: Capture the expiring link, the unlabeled box, and a reunion set without requiring a perfect folder tree first.
The consequential choice is not something a board or an AI should quietly make: Whether to scan the unlabeled box next, copy the expiring link first, or make the reunion set from already-scanned years only.
You.one can keep the work, evidence, live dependency, and “Choose box, link, or reunion-only” decision visible through its Superboard view. The Owner boundary stays explicit: Joan chooses the order, copies files, and owns what is shared at the reunion.
Available today
Photo decades: one Board shape to adapt
The Photo decades Board gives this mission one durable operating picture. Joan 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.
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 |
|---|---|
| Mission | Expiry, unlabeled box, reunion date |
| Sources | Drives, albums, links |
| In progress | What is actually being copied or scanned |
| Reunion set | The six-week album |
| Waiting | The sibling cloud link's external expiry clock |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Joan's situation: “Choose box, link, or reunion-only” is the live choice, “Unlabeled childhood box” holds evidence, and “Sibling cloud link expires” names something genuinely in motion outside Joan's control. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Capture before taxonomy | Mission | Keep the expiry and unlabeled box ahead of folder perfection |
| Choose box, link, or reunion-only | Sources | Compare unlabeled-box-next, copy-expiring-link, and reunion-from-done |
| Unlabeled childhood box | Sources | Hold the pile that is not already titled Wedding |
| Wedding scans repeating | In progress | Show the comfortable work that is hiding the box |
| Sibling cloud link expires | Waiting | Name a clock that scanning the wedding will not stop |
| Reunion album in six weeks | Reunion set | Keep a delivery from becoming a reason to invent a database |
Available today
Available today: Choose box, link, or reunion-only becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Capture-order brief: Place expiry, unlabeled box, and box / link / reunion-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: Joan will choose a capture order that beats the expiry.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Capture-order brief and this Card Room's visible notes and left “Choose box, link, or reunion-only” with Joan.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare scanning the unlabeled box, copying the expiring link first, and making the reunion set from what is already scanned. Do not contact the sibling 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.
Joan's call remains explicit: Joan chooses the order, copies files, and owns what is shared at the reunion.
| Surface | Job in this example |
|---|---|
| Stage | Capture-order brief: Place expiry, unlabeled box, and box / link / reunion-only options on one page |
| Chat | Keep Joan's request and Ava's attributed response with the work |
| Pulse | Open decision: Joan will choose a capture order that beats the expiry |
| Activity | Ava compared the options in Card Chat using the Capture-order brief and this Card Room's visible notes and left “Choose box, link, or reunion-only” with Joan |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose box, link, or reunion-only” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Joan 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 Joan, watch other Lists, or act outside this Card Room.
Joan owns files, sharing, and sibling conversations. Ava does not copy drives, contact anyone, or host the archive.
A capture order: the expiring link is first or chosen later, the unlabeled box is on the Board, and the reunion set does not require a perfect taxonomy.
- Request idea: using only the context visible in this Card Room, compare scanning the unlabeled box, copying the expiring link first, and making the reunion set from what is already scanned. Do not contact the sibling or choose for me.
- Request idea: use only the Capture-order 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 drawer of drives plus repeating the labeled wedding may still be enough
A drawer of drives plus repeating the labeled wedding is enough when everything is already on one disk.
It starts to break when an expiring link, an unlabeled box, and a reunion date share six weeks.
The Photo decades Board earns its place only when the familiar tool—a drawer of drives plus repeating the labeled wedding—can no longer keep the reason, Capture-order brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Joan should rename every List or Card that feels artificial. This recipe succeeds when “Choose box, link, or reunion-only” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. List sources | Drives, boxes, links |
| 2. Put expiry on the Board | A clock beats a taxonomy |
| 3. Name the unlabeled pile | Do not only scan what is already titled |
| 4. Cap the reunion set | Six weeks is a delivery, not a database |
| 5. Choose box, link, or reunion-only | Open a Room before rescanning the wedding |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when an expiry Card is near and no copy job exists, still leaving every file with Joan.
A future unified You.one experience could carry relevant context from “Choose box, link, or reunion-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
- Joan is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not a storage, copyright, or genealogy-research claim.
- It does not show Ava copying files or contacting a sibling.
- It is not a measured archive result.