Skip to Content

Scenarios for Companion Memory

A scenario is a short walkthrough of one job a person wants to do with Companion Memory, such as sharing photos with family. Each table lists the steps in order, what happens, who sees the result, and the status.

The people in these scenarios are fictional. They are invented to show how the product is used, and they are not real users. They are described on the personas page.

The status column uses four words:

  • Works today: the step is on by default.
  • Behind a setting: the step is in the product, but it stays off until an owner or operator turns it on.
  • Planned: the design is documented, but the code does not exist yet.
  • Not yet: the step is not built, or it is built but not connected to the product.

After each table, a short paragraph lists the steps that are not yet built or only planned. Two scenarios involve buying something, and none of the purchase steps works in the product today.

Dinner and a film

Tomas organizes an evening for five friends in three households. He wants to check their availability, set a reminder, and have an agent buy tickets inside a group limit. Only part of this works today.

StepWhat happensWho sees whatStatus
Calendar and same-box askTomas imports his calendar and asks friends on his box when they are free. Google imports only the main calendar.Friends on his box.Works today
Ask to other boxesNeeds an outbound setting on Tomas’s box and inbound asks on the friend’s box. Delivery between boxes is not yet confirmed.The friend’s box gets Tomas’s handle and time window.Behind a setting
Friend’s answerMeant to show only free or busy times. This is not yet guaranteed for every friend, and private events can show as busy.Tomas sees free or busy times.Not yet
No answer in 72 hoursThe ask expires, and the time limit cannot be changed.The friend sees it as expired. Tomas sees it as delivered.Works today
Friend answers lateThe answer stays on the friend’s box and does not reach Tomas.The friend’s box only.Not yet
ReminderTomas sets a reminder. In the memory app, browser push stays off until its keys are set.Tomas’s phone. The push message carries the title and text.Behind a setting

What is missing. Friends are not alerted to asks, and asks are not held or retried when a box is down. Answers do not return to Tomas. Invitations do not collect replies, and cancelling a plan does not tell friends. Reminders do not reach friends. The agent cannot book or buy, and there is no spending limit or refund.

Notes. This scenario assumes each household runs its own box, linked to Tomas’s box by both owners.

Client meeting

Noor prepares an agenda, invites an outside client to a meeting, keeps minutes linked to their sources, and sets a retention rule when a matter closes. The client has no box or account.

StepWhat happensWho sees whatStatus
Agenda and minutesNoor writes the agenda and types the minutes in a plan. Only she can see them.Only Noor.Works today
Adding the clientNoor adds the client by hand. The product does not check who the client is.Noor’s box.Not yet
Calendar and meetingNoor imports her calendars and creates the meeting by hand. Automatic calendar updates are off by default.Nothing leaves her box.Behind a setting
Sending availabilityAvailability goes only to other Companion boxes, so the client cannot receive it.No one outside her box.Not yet
Invitation fileNoor sends an exported file by her own mail. The file is not signed and does not ask for a reply.The client.Not yet
Matter kept apartThere is no matter boundary. A shared search can cover several clients.Readers of a shared search that spans clients.Not yet

What is missing. A matter is not a separate object. Minutes cannot yet link to their sources, which is planned. The client cannot reply to an invitation, and agendas cannot be shared outside the product. There is no retention rule for each matter. Copies the client has saved are not recalled.

Family photo sharing and revocation

Ruth shares family photos with her grandchildren and their parents from Maya’s household box. Maya helps as the box owner, but Ruth keeps control of her archive. After a family change, Ruth narrows or ends access.

StepWhat happensWho sees whatStatus
Standing permissionRuth gives a family member a photo permission. It lasts until she removes it, unless an end date is set.Ruth and that family member.Works today
Shared search linkAnyone signed in with the link can read results, up to any limit Ruth sets.Anyone signed in with the link.Not yet
Family photo requestOn the same box, requests work today. Requests from other boxes need the inbound setting.Ruth’s box sees who asked and what they asked for.Behind a setting
Match only, no countThe asker learns that something matches, but not how many. A count is not yet shown.The asker.Not yet
Review and narrowingRuth previews each answer. She can lower a family account’s level, and permissions still apply within it.Ruth. The asker sees only what she sends.Works today
Ending access and exportRevoking stops new reads. Ruth can export her archive, or archive and delete the photos. Archive and delete keeps permissions and asks.Whoever holds an export file.Works today

What is missing. A settled default for shared search links, a count for photo requests, and alerts to Ruth when requests wait in her review inbox. The sensitive-item check does not yet apply to family accounts. Queued requests are not re-checked when a level changes. Ending access through another box’s link does not yet work as described. Copies readers saved cannot be removed. Backup contents and operator limits are not yet documented.

Friend-group membership change

Ana leaves a standing friend group that Tomas runs. Her asks, answers and read access are handled as far as the product allows. Her plan history is kept or archived, and Ana can be added again later.

StepWhat happensWho sees whatStatus
Group as a planTomas keeps the group as a plan with a member list. There is no group object.Nothing leaves his box.Not yet
Ask to AnaNeeds the outbound setting on Tomas’s box. Ana’s box must also allow inbound asks.Ana’s box gets Tomas’s handle and time window.Behind a setting
Ana leavesThere is no leave action. Access can end on one box, and the other box is not told.Only the box that acts.Not yet
Asks expireAfter 72 hours, an ask expires. Ana sees it as expired, and Tomas sees it as delivered.Ana and Tomas.Works today
Shared plan readerIf the plan is also a shared search, Ana can keep reading until Tomas removes her as a reader.Ana, and anyone else with the link.Not yet
Plan historyTomas archives or exports the plan history. Archive is reversible. Archive and delete keeps asks, links and permissions.Tomas’s box.Works today

What is missing. A group object and a leave action. A settled default for shared searches. Answers do not return to Tomas, and other members are not told. Asks queued before access ended are not re-checked. Keys do not change when a member leaves, because there is no group key yet. Ana’s local copies cannot be removed. Whether links and permissions return on re-adding is not yet confirmed. Re-adding cannot yet check a published key. Old asks and answers have no removal rule, and reminders do not reach other members.

Notes. Until these steps exist, Tomas has to tell the other members and remove access on each box by hand.

Care circle

Ruth lets Maya see appointments and reminders within limits that Ruth sets, until a date that Ruth chooses. Ruth can revoke access at any time. A permission does not replace legal authority, and the product gives no medical advice.

StepWhat happensWho sees whatStatus
Setting the limitsA ready-made care template is planned. Today Ruth sets each limit herself.Nothing leaves her box.Planned
Standing permissionRuth gives Maya a permission. It names the kinds of ask it covers, and other asks wait for Ruth.Maya, within the named kinds.Works today
Summary-only answersRuth can choose a summary, the most limited answer. The form does not offer this yet.Maya gets only what the limit allows.Not yet
Maya’s askSending needs an outbound address. Ruth’s box refuses asks from other boxes until inbound asks are on.Ruth’s box sees Maya’s identifier and time window.Behind a setting
Busy and free timesMaya sees busy and free blocks, with no titles or places. Private appointments still show as busy. Whether the summary limit applies here is not yet confirmed.Maya.Not yet
Ending accessNew asks stop. Asks queued before the change are not yet re-checked.Maya’s box keeps the answers it already has.Not yet

What is missing. The care template is planned. End dates are not yet confirmed in the form. Ruth is not alerted to new asks. Maya cannot ask for titles or counts, and answers carry no dates. Later answers are not collected, and Maya cannot see Ruth’s reminders. Some Disclosure History entries depend on features not yet built. Maya’s box is not told when access ends. A new ask after the end date has no confirmed outcome. There is no delegate role, and passkeys are not yet built.

Notes. Keep sensitive items out of this permission. The sensitive-item check does not yet apply to family accounts.

Travel on a phone

Kenji reaches his box at home from his phone over a private network while he is away. Requests from friends must still behave correctly while the box is unreachable. Several parts of this path are not yet built or tested.

StepWhat happensWho sees whatStatus
Sign-inKenji signs in to his account on the phone.The account service.Works today
Private networkThe phone reaches the box over Tailscale. It needs Tailscale set up on the box and on the phone.Kenji’s own devices.Behind a setting
Ask while the box is downOne direct attempt is made. If it fails, the ask is not delivered, and the sender’s record shows delivered, with a reason.The sender.Behind a setting
Holding and retryingThe product does not hold an ask for a box that is down. Nothing retries the send.The sender only.Not yet
Review inbox while awayAsks from other boxes need the inbound setting. They then wait in Kenji’s review inbox.Kenji.Behind a setting
Ask expiryAn ask expires 72 hours after it was made. Checks run about every five minutes.The sender sees delivered.Works today

What is missing. Private-network addresses in the Hub app. Holding and retrying asks. Alerts to Kenji about new asks. Push to the phone, which needs keys in the memory app and is not yet built in the Hub app. Approval of queued actions on the phone. Offline sync for photos and video.

Notes. The memory app on iOS is in internal testing and is not yet on the public App Store.

Key compromise and recovery

After a suspected compromise or a lost device, Devon signs out the device, revokes access, and changes keys. He also needs to know what the box operator can see and what cannot be recovered. Maya, who runs the box for her household, may need to help. Some steps work today, and others are not yet built.

StepWhat happensWho sees whatStatus
Sign out the deviceDevon signs out the suspect device. The product does not yet confirm that access ends at once.Devon’s devices.Not yet
Revoke permissionsDevon revokes standing permissions. New asks from those people stop.Those people lose access to new asks.Works today
Tell the other boxNothing tells a peer’s box that access has ended.The peer’s box keeps what it holds.Not yet
Rotate connection keysKeys for each connection can be rotated one at a time, before they expire.The two ends of the connection.Works today
Set up devices againDevices are paired again with a code. Device key protection is not yet confirmed.Devon’s devices.Not yet
Restore from backupA restore checks only the file structure. A full restore test is not yet confirmed.Devon.Not yet

What is missing. Confirmation that a signed-out device loses access at once. Notice to peers when access ends, and a way to take back copies they hold. Key changes when a peer or group member is removed, and group keys. Passkey recovery and rotation of a leaked sign-in secret. A signature check on update images. Re-checking asks queued from a revoked peer. Pairing box members again is not yet settled.

Notes. Importing an export works as a recovery step, but it replaces the data already on the box. The product does not yet document, in one place, what the box operator can see.

Agent errand with spend cap

Tomas wants an agent to book a table or buy tickets inside a spending cap, after he approves the purchase, and to keep a receipt. This scenario is a design. No purchase or booking works in the product today.

StepWhat happensWho sees whatStatus
Goal and capTomas would set the goal, cap, currency and expiry. These settings are not built.Tomas only.Not yet
SearchThe agent can search. Ordinary reads from outside sources need no approval.The sources searched.Works today
Booking or buyingThe agent has no tool to book or buy.Nothing is sent.Not yet
Approval queueActions the agent marks for review wait in a queue. Whether this is on in every install is not yet confirmed.Tomas, when he reviews the action.Not yet
ApprovalTomas approves from his own session or key. Other apps cannot approve.Tomas.Works today
Charge, receipt and refundNo charge runs for an agent. There is no cap check, no guard against repeat charges, no signed receipt, and no refund request.Nothing is sent.Not yet

What is missing. The Hub app’s approval card, and a check against self-approval. Every purchase, booking, charge, cap, receipt, refund and dispute step. How disputes over agent purchases are handled is not yet set. An audit record of agent actions. A booking would create a calendar entry only, not a reservation.

Notes. No purchase or payment for an agent works today. The steps above show what would be needed.

Stranger identity check

A working photographer gets a request from a person they do not know. They decide how much to share after checking who that person is. Checks that use credentials are not yet built.

StepWhat happensWho sees whatStatus
Request arrivesAsks from other boxes need the inbound setting. Checking an ask’s signature is behind a setting.The owner’s box.Behind a setting
Identifier checkThe asker’s identifier must match the link exactly. Decentralized identifiers for peers are not yet built.The owner’s box.Not yet
Verifiable credentialsA verifiable credential is not yet checked, and other formats are not yet built.The owner’s box.Not yet
Credential proofThe proof on a credential is checked when that setting is on.The owner’s box.Behind a setting
Shared contactsChecking a shared contact without revealing the contacts is not yet built.No one yet.Not yet
The owner decidesThe owner previews each answer and sets the trust tier for that person.The owner sees the request. The asker sees the answer.Works today

What is missing. Credential status checks and presentation requests. Credentials for a later phase are planned. An account check through the account service is not yet confirmed. The asker gets no clear result, so a decline looks the same as a request that is still waiting.

Notes. A stranger gets only a yes or a no.

Export and move

Ruth moves her archive to a new box. She exports her data, the new box checks and imports the file, and the old box keeps or deletes its copy.

StepWhat happensWho sees whatStatus
ExportRuth exports one file with her profile email, her records and her photos.Whoever holds the file.Works today
Moving the fileThere is no direct transfer between boxes, so Ruth moves the file herself. The file has no signature or checksum yet.Whoever moves the file.Not yet
Shape checkThe new box checks the file’s format, version and account. It does not check the contents.The new box.Works today
ImportRuth types her account email to confirm. The import replaces the data already on the new box.Ruth’s new box.Works today
Old boxRuth can archive her old copy, which is reversible, or archive and delete it. Asks, links and permissions stay.Ruth’s old box.Works today
Copies elsewhereCopies held by other boxes are not removed. No rule removes old records on a schedule.Other boxes keep their copies.Not yet

What is missing. A direct transfer between boxes, and a signature or checksum on the export. A check of the audit records in the file, and a preview before import. Permissions and links are not carried over, so Ruth sets them up again. Removal of copies held elsewhere, and a schedule for old records.

Notes. Import replaces the data already on the new box, so check that it holds nothing you want to keep. If an import fails, database changes are undone, but stored photo files are not. Keep export files somewhere safe, because they are not encrypted.

Last updated on