Memory
Knowledge that can be verified
but not reconstructed.

VERITY memory is not storage. It is fidelity-bounded compression: meaning is reduced to compact signatures, fidelity is checked at every stage, and the process stops when reconstruction of the original is no longer possible.

What it is

Compression as a first-class idea.

"Most systems store text. VERITY stores its meaning, then discards the text. What remains is smaller, more secure, and more useful."

Traditional RAG and vector database systems store the original text alongside its embedding. The embedding navigates retrieval, but the text is still there. It can be exfiltrated, misquoted, or retrieved out of context. The embedding is an index to the data, not a replacement for it.

VERITY takes a different position. When content is ingested, it is measured and compressed through multiple stages, not as a storage optimization, but as a deliberate design. The text is discarded. What remains cannot reproduce the original. It can only verify whether new inputs are consistent with what was stored.

What it does

Fidelity measured at every stage.

The cascade does not compress and hope. At each stage, the system measures what survived: how much fidelity remains relative to the prior stage, and whether the result is still useful for verification.

Stage What remains Purpose
Full resolution Complete fidelity
Active processing
Working storage Near-lossless
Long-term retention
Compact signature Verification-ready
Irreversible claim check
Decision Verified or declined
High-throughput screening

Aggressive compression. Fidelity measured at every stage. Original text is not retained.

01
Ingest once. Verify forever.
Content enters as text. It is encoded, compressed, and stored as a signature. The original text is discarded. What remains is small, yet enough to verify future claims against what was stored.
02
Fidelity is computable between signatures.
Two compact signatures, from two different pieces of content or from a query and a stored document, can be compared directly. The system measures how much meaning they share. This is not retrieval. It is verification.
03
The cascade is the security model.
By the time content reaches a compact signature, reconstruction of the original is not possible. There is no plaintext to steal. The loss is the protection.
What that means

"Below a certain stage, content cannot be reconstructed. Only verified."

This is not a limitation. It is the design. Past that stage, the original text is permanently inaccessible, but meaning remains permanently queryable. Content that crosses it cannot be exfiltrated because it no longer exists in any reconstructible form.

What that means for security

Protection that is structural,
not bolted on.

Because the cascade is the security model, there is no perimeter to defend and no key file to protect. The security is not a layer around the data. It is a property of how the data exists.

Bound to the deployment
Signatures only work with the deployment that created them. A different installation cannot read them as meaningful structure. Without that deployment, stored signatures are useless noise. There is no key file to steal. There is no plaintext to exfiltrate.
Kill Switch
The system monitors its own structural integrity continuously. If that integrity degrades from tampering, systematic probing, or corruption, the system zeros its cryptographic material and halts. There is no override. There is no recovery path. The attack defeats itself.

AES-256 encryption at rest  ·  ECDSA-signed verification traces  ·  License-locked per deployment  ·  Air-gap native from day one