Trust Is Where
The Memory Lives.
Verity One earns trust from where your data lives and how every memory is tracked — not from a badge, a seal, or a promise. This page is the plain statement of both. Read it; then hold us to it.
It runs on your machine.
Verity One runs locally. A PostgreSQL database on your own machine is the source of truth for everything it remembers — every memory, every edge, every reference. There is no account to create and no server to phone home to before it works.
Your memory is kept close and private on your machine. Nothing leaves your desk unless you deliberately opt into VO+, the optional web bridge described further down. Until you do, the local node is the whole story — authoritative, and entirely yours.
A reference, recorded as-is.
A memory can carry a reference to where it came from. Verity One records, honestly, whether that reference was provided — and nothing more than that.
That status — linked, missing, or optional — is a record of provenance, not a verdict. Verity One does not fetch the source, follow the link, or check that it says what the memory claims. There is no "verified" badge here, because there is nothing behind one. Even the verified_at field is just the moment the memory was written — a write timestamp, not a re-check. We would rather tell you a reference is missing than imply a validation we never performed.
Nothing forgotten behind your back.
A memory moves through four real states, and you are the one who moves it. Verity One does not silently delete what you have entrusted to it.
- Active — current and recallable, the default for anything you write.
- Superseded — replaced by a newer memory you wrote in its place; the old one steps aside but is not erased.
- Retracted — withdrawn by you because it was wrong; kept on the record as withdrawn, not vanished.
- Archived — set aside, out of the way, still there if you go looking.
Recall ranks recent memories higher and flags ones older than about thirty days as stale — but that is advice, not action. A stale flag never deletes anything. Your tenant memories persist until you supersede, retract, or set them aside. The automatic decay you may have heard about applies only to the shared public knowledge graph — never to your own memory.
The honest shape of the bridge.
If you choose to turn on VO+, a hosted mirror of your memory can travel beyond the desk so web agents can reach it. We want you to understand exactly what that means before you opt in.
The hosted mirror is encrypted at rest with a per-tenant key. But those keys are service-managed, which means the hosted layer can read your data while it syncs. That is the honest truth, and it is worth saying plainly: VO+ is not zero-knowledge. We do not claim to be unable to read it, because that would not be true.
Even with the payload encrypted, the mirror keeps some metadata in plaintext so it can route, deduplicate, and apply updates without decrypting first: the item addr and its project, the item type/status, the governance key, the source node id, and sync timestamps. The memory content (substance, labels, descriptions) is encrypted; its shape and addressing are not. If even that is too much, the content_opaque opt-in narrows it further.
What does not change is authority: your local node stays the source of truth, and the mirror is a copy that follows it. For those who want more, an advanced opt-in mode (content_opaque) is available — but it is a deliberate choice you make, never the default we describe above.