VO+  ·  OPTIONAL

Your Memory,
Beyond The Desk.

VO+ carries your memory beyond the desk, on demand — a bridge, not a replacement. Your local node stays the source of truth; VO+ never takes its place.

WHEN YOU'D REACH FOR IT

Away from the machine that holds your node.

Most of the time you work at the desk, and on-machine agents read and write your local node directly. VO+ is for the moments you are somewhere else — and only those moments.

  • Recall from web MCP agents — a browser, a phone, a tablet — that can't reach the local node directly.
  • Review a synced snapshot of your memory from any device at verityone.app/my, once you've linked and pushed.

All of this is optional and later-phase. None of it is needed to install Verity One, connect on-machine agents, or do your day-to-day work.

WHAT SYNCS

Outbound, on demand — never a merge back.

When you choose to, the local node pushes your memory outbound to a hosted mirror. Sync runs in one direction: from your machine to the mirror. It is not a two-way merge, and there is no leg that pulls a graph back into your node.

Nothing leaves your machine until you link your account and push. Until then the mirror is empty and the bridge is closed — the local node holds everything.

Manual beta. Linking is hands-on today: there is no vo sync pair command yet, so pairing a node to your account is done through the dashboard connect flow, then you enable the outbound push by hand. The polished one-command pairing is still to come — set expectations accordingly before you rely on web-agent recall.

TWO ACCESS PATHS

One source of truth, two ways to reach it.

ON-MACHINE · LIVE

Claude Desktop, Codex, and generic MCP clients read and write live against the local node. Their changes land in the source of truth immediately.

WEB · QUEUED

Web agents reach the synced mirror. Their reads come from the last sync, and their writes are queued as intents (vo.write.intent) — recorded, not applied live to your node.

For the wire-level contract — transports, scopes, and how queued intents are shaped — see /agents.

ENCRYPTED, NOT ZERO-KNOWLEDGE

We're plain about what the mirror can see.

The hosted mirror is encrypted at rest with a per-tenant key. Those keys are service-managed, which means the hosted layer can read your memory while it syncs. This is encrypted-at-rest, not zero-knowledge — and we'd rather say so plainly than imply otherwise.

And the encryption covers the payload, not the metadata: the item address and project, item type/status, governance key, source node id, and sync timestamps stay in plaintext so the mirror can route and dedupe without decrypting. Your memory's content is encrypted; its shape and addressing are not. The content_opaque opt-in narrows that further.

The local node remains authoritative; the mirror is a copy you opted to send. For the full wording on keys and trust, see /trust.

GOOGLE DRIVE MIRROR · OPTIONAL

Mirror your vault into a Drive folder.

If you want it, VO+ can mirror your vault into a Google Drive folder of your choosing. It builds on your hosted connection, so it's an extension of VO+ rather than a separate path.

It isn't set-and-forget: Google may require you to re-authorize the connection periodically, and the mirror keeps working only while that authorization is current.

VO+ is optional and later-phase. Everything core to Verity One runs entirely on your machine — the bridge is there only if and when you reach for it.