Example
How to build a family photo archive without losing decades in a hard-drive drawer
Joan's problem is not a lack of effort. It is that Capture the expiring link, the unlabeled box, and a reunion set without requiring a perfect folder tree first has outgrown scattered reminders, tabs, and memory. This fictional playbook shows a concrete Board, the Cards inside it, one consequential Room, and the line Ava does not cross.
This fictional example was created with AI assistance from a structured editorial brief and reviewed by the You.one Editorial Team for usefulness, distinctness, and product truth.
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 Superboard provides the durable structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Joan's pressure is ordinary—and still heavy
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.
Joan can scan. The archive fails if the expiry link, the unlabeled box, and a reunion deadline never share a sequence.
Two drives, a cloud link, and a cardboard box all claim to be the archive.
Making a perfect taxonomy first would miss the reunion.
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
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Joan still owns the purpose, tradeoff, and final call.
Available today
Photo decades: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Joan does not have to convert life into project-management jargon or decide the perfect taxonomy first. Lists separate kinds of attention; Cards keep each meaningful item visible and movable.
The Cards are deliberately mixed. Some are tasks, some are decisions, some hold a person or promise, and some are reference points. Current Superboard supports that flexibility without flattening the mission into one long to-do list.
| 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 | Sibling link and drive cables |
Available today
The Cards make the operating picture concrete
A Board becomes useful when the Card titles sound like the actual situation. These are not generic placeholders; they show what Joan would need to see to run this mission without carrying every open loop in memory.
| 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 |
| Sibling cloud link expires | Waiting | Name a clock that scanning the wedding will not stop |
| 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 |
| 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 Waiting for Joan to choose a capture order that beats the expiry. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, 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 context and can make limited reversible product changes. She does not deeply reason over the whole Board by default, and 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 | Waiting for Joan to choose a capture order that beats the expiry |
| Activity | Preserve attributed Card changes and the supported record around the request |
What to ask Ava—and what not to assume
These are useful requests to adapt, not claims that current Ava automatically surveys the whole Board, prepares every comparison, or follows up on her own. The relevant facts must be present in supported Board/Card context, and the human still checks the result.
Joan owns files, sharing, and sibling conversations. Ava does not copy drives, contact anyone, or host the archive.
The modest outcome is not that Ava lives Joan's life. The modest outcome is 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: summarize sources, in-progress scans, and the reunion deadline already on the Board
- Request idea: compare capture-order options using the expiry Joan captured
- Request idea: help keep the comfortable wedding scans from pretending to be the whole archive
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
Superboard earns a place only when the responsibility needs a durable picture around the list: the reason, artifact, conversation, current state, decision, and history.
A starter recipe to adapt, not obey
Use the names that already make sense in Joan's world. The recipe is successful when the Board reduces remembering and exposes the real decision—not when every Card is perfectly categorized.
| 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 capture order | 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.
The unified You.one and Superboard runtime, cross-product personalized Memory Spine, broad proactive coordination, realtime shared editing, and general external execution are not available today. Future actions 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.