Example
How to back up a digital life without confusing a folder named Backup with a restore test
June's problem is not a lack of effort. It is that Get one tested restore of photos and tax PDFs before the laptop is replaced, and treat the clicking drive as dying rather than as a third copy 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.
June is an explicitly fictional portrait, not a customer or testimonial.
The Backup that restores Board gives one mission a visible field; the Choose clicking drive, cloud test, or delay laptop 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.
June's pressure is ordinary—and still heavy
June is a fictional 44-year-old household member responsible for family photos and tax PDFs in Sault Ste. Marie, Ontario. June has a drawer of drives labeled Backup. One drive clicks. Photos also live on a phone that is full. A laptop replacement is next month. Nobody has ever restored a file on purpose.
June can copy files. The month fails if the clicking drive, the full phone, and the new laptop never share a tested restore.
Three drives, a phone, and a cloud folder all claim to be safe.
Buying another drive feels like backup and would still be untested.
A drive labeled Backup is not a restore, and a clicking disk is a clock
The mission is specific: Get one tested restore of photos and tax PDFs before the laptop is replaced, and treat the clicking drive as dying rather than as a third copy
The consequential choice is not something a board or an AI should quietly make: Whether to copy off the clicking drive first, restore-test the cloud copy first, or delay the laptop purchase until one restore has worked
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. June still owns the purpose, tradeoff, and final call.
Available today
Backup that restores: one Board shape to adapt
A useful Board gives this mission one durable operating picture. June 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 | Tested restore before the new laptop |
| Sources | Phone, laptop, clicking drive |
| Copies | What actually exists where |
| Tests | Restores done on purpose |
| Waiting | New drive and laptop order |
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 June would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| A restore that has been tried | Mission | Keep the laptop replacement beside the untested Backup labels |
| Choose clicking drive, cloud test, or delay laptop | Tests | Compare copy-off-clicking, restore-test-cloud, and delay-purchase |
| Drive that clicks | Sources | Name a dying disk so it is not counted as a healthy copy |
| Phone full of photos | Sources | Hold a source that is one drop away from loss |
| Folder named Backup | Copies | Mark a label that has never been restored from |
| Laptop replacement next month | Waiting | Keep a purchase from outrunning a tested copy |
Available today
Available today: Choose clicking drive, cloud test, or delay laptop becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Restore-path brief: Place clicking drive, untested folder, laptop date, and copy / test-cloud / delay options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for June to choose a path that produces a restore, not another unlabeled drive. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare copying off the clicking drive, testing a cloud restore, and delaying the laptop. Do not buy anything 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.
June's call remains explicit: June chooses copies, runs the restore test, and owns purchases and any shredding of old drives
| Surface | Job in this example |
|---|---|
| Stage | Restore-path brief: Place clicking drive, untested folder, laptop date, and copy / test-cloud / delay options on one page |
| Chat | Keep June's request and Ava's attributed response with the work |
| Pulse | Waiting for June to choose a path that produces a restore, not another unlabeled drive |
| 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.
June owns files, purchases, and destruction of old media. Ava does not copy data, buy drives, or guarantee recovery.
The modest outcome is not that Ava lives June's life. The modest outcome is a restore that has been tried: the clicking drive is treated as dying, the phone is a source, and a new laptop does not outrun a test.
- Request idea: summarize sources, copies, and the missing restore test already on the Board
- Request idea: compare path options using the clicking drive and laptop date June captured
- Request idea: help keep a Backup label from counting as a test
A drawer of drives labeled Backup may still be enough
A drawer of drives labeled Backup is enough when a restore has already been proven
It starts to break when a clicking disk, a full phone, and a new laptop share an untested folder name
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 June'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 | Phone, laptop, clicking drive |
| 2. Stop counting labels as copies | Backup is a word |
| 3. Put the laptop date on the Board | A clock |
| 4. Schedule a restore test | On purpose, one file |
| 5. Choose the dying disk’s fate | Open a Room before buying another untested drive |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a laptop Card is close and no Tests Card is done, still leaving every copy with June.
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
- June is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not data-recovery, security, or tax-records advice.
- It does not show Ava copying files, buying drives, or guaranteeing a restore.
- It is not a measured backup result.