Skip to content
The Vault

Your knowledge graph.
Yours.

Drop in your contracts, transcripts, research, and notes. The Vault indexes everything by meaning, ranks fresh truth over stale, and proves nothing has been tampered with. All on your machine.

What goes in

Everything that informs your work. Indexed by meaning.

The Vault treats every chunk as content-addressable. Same paragraph, same hash. You can prove a document hasn't changed without uploading it anywhere.

Documents

PDFs, contracts, briefs, research papers, books

Transcripts

Meetings, depositions, lectures, calls

Web clips

Articles, citations, evidence, references

Notes & messages

Voice memos, journal entries, email threads

Trust tiers

Fresh truth wins. Stale falls back.

Every document carries a trust tier. When you search, the Vault doesn't just return what's most similar. It returns what's most authoritative.

A canonical document at 0.6 similarity outranks a working draft at 0.8. That's the Vault deciding for you. The way a careful researcher would.

Canonical

Source of truth

weight 0.6

The signed contract. The final policy. The decision you live by.

Working

Drafts & revisions

weight 0.8

The negotiation in progress. The current version. Fresh but not final.

Ephemeral

Quick references

weight 0.5

Email threads, scratch notes, transient context.

Archived

Superseded

weight 0.3

Last year's policy. The old contract. Available, but down-weighted.

Time travel

What was true on March 15?

Every document carries a temporal validity window. Ask the Vault what your policy said last quarter, what the contract specified before the amendment, what your medication list looked like in December.

You get only the documents that were active on that date. Not what replaced them. Not what came later. The exact state of your knowledge at that moment.

vault search
asof: 2026-03-15
what was our refund policy?
refund-policy-v3.pdfcanonical · active
refund-policy-v4.pdfnot yet active
refund-policy-v2.pdfsuperseded

Cryptographic proof

Prove a file hasn't changed. Without uploading it.

Every chunk gets a SHA3-256 hash. Every Vault has a Merkle root. To prove a single document is intact, an auditor needs the document and a tiny proof path. Not your whole knowledge base.

Your document

Stays on your device

Proof path

A few hashes, kilobytes total

Verified

Auditor confirms integrity offline

SHA3-256 + Merkle root

Modify a single byte in any document and its hash changes. The Merkle root changes. The proof breaks. Tampering is mathematically detectable without anyone seeing the document itself.

Malicious documents stop at the door.

Before anything reaches your index, the Membrane checks for prompt injection, jailbreak attempts, and embedded payloads. Bad inputs get quarantined. Your knowledge stays clean.

How it works

Build the knowledge base that's actually yours.

Drop in your first hundred documents. See how fast it gets when your AI knows what you know.