Mnemonic sovereignty

Knows everything.
Says only what belongs here.

We build the Relational Companion: a portable identity layer the person owns, which governs what enters its memory, what may leave it, and to whom — across every engine it borrows.

The membrane · who is present Fig. I

Every hold is recorded in the transit log — held on your machine, not ours.

An illustration of the governing criterion, drawn from behaviour observed in our own system. It is not a live demonstration of the product.

The problem

The field has named it

Memory is now the axis on which assistants compete. MemTensor's survey on the security of long-term memory in LLM agents (arXiv:2604.16548) calls the missing piece mnemonic sovereignty — verifiable control over what may be written, who may read it and what can be forgotten — and finds that no published architecture covers the nine governance primitives it identifies.

Our position

The parts exist. The whole does not

Provenance, temporal validity, write gates, authority routing: each has serious work behind it, and we cite all of it. What no one has composed is the governed whole, answering to one person, that carries them from one engine to the next.

Why now

Governance cannot be added later

Labels can be reconstructed after the fact. Authorisation cannot: consent is an event, not an attribute. A system that absorbed years of a life without a gate can never demonstrate that it was permitted to.

Declared, not dressed up

What runs today, and what remains on paper

We publish our own failures in our build reports. It would be inconsistent to stop here.

Running

The companion installed as a guest across four separate engine providers, recognisable in each
A longitudinal corpus with cryptographic provenance
Membrane holds observed in live sessions, one of them with a witness present
Engine switching through our own router, cost measured per call
Espina v0.9 published; clone-and-verify closed without third parties
A reconstruction-fidelity study replicated across three agents, published with a DOI and the full coding matrix

Specified, not yet built

The single window: the companion as host rather than guest
Blind-server operation under governed custody
Canon reversal under nuclear authority
The full transit log, including exchange between companions
Benchmark results for the full companion: transit, window and end-to-end cost

The standard

Espina

The open specification for a portable spine: identity, worlds, membrane, provenance and authority, in a form any implementation can carry. Published with a date, a manifest and hashes, so the claim can be checked rather than taken on trust.

Read the specification on GitHub

Read the study and the data (DOI)

Talk to us

We are raising to build the window, and to put the companion in the hands of the people who need it first: those who hold other people's confidences for a living.

[email protected]