Not a Third Party to Your Own Records
2026-07-29 · Sovereignty
A correction, and the principle underneath it.
By VK Singh Vashisht — Datura Labs
The first version of the access control I built for my own archive got something backwards, and it took shipping it to see how.
What v1 got wrong
The early design walled off my own corpus by content sensitivity — green, amber, red — and restricted my own access according to which tier a given record fell into. The reasoning felt sound at the time: treat sensitive material carefully, gate it behind explicit review, don’t let anything slip through by default.
What it actually built was a system that treated its own owner as a risk to be managed.
That’s not caution. That’s a broken tool wearing caution’s clothes.
The correction
An airgap was never about disconnection. It’s about having no trusted third party at any layer — nothing leaves the box you didn’t author, nothing gets read by a process you don’t control. That’s the property worth protecting.
I am not a third party to my own records.
The fix moved the control from what the content is to where it’s going. Not: is this row green, amber, or red. Instead: is this request going to stay on hardware I own, is it going to a model I’ve chosen to trust with the retrieved text, or is it trying to leave to somewhere else entirely. One socket, one gate, instead of a taxonomy that has to be maintained by hand, forever, as the archive grows.
Why the second version is stronger, not weaker
It looks, at first, like loosening a restriction. It’s the opposite. A tier-based wall has to be right about every row, indefinitely, and a taxonomy that has to be perfectly maintained forever is a taxonomy that will eventually drift wrong in exactly the place it mattered most. A route-based gate only has to be right about one thing: where does this go. That’s a smaller, more stable, more honestly enforceable question — and it happens to be the one that actually protects against the failure mode an airgap exists to prevent.
Sovereignty was never the promise that a system would be hard to use. It was the promise that the owner stays the owner — that the files, the structure, and the rules stay on hardware they control, and that no vendor, no default, no well-intentioned safeguard gets quietly inserted between an owner and their own history.
That’s what it means for sovereignty to be what remains when any single vendor disappears. It has to hold at the level of who’s allowed to ask the archive a question, not just at the level of where the archive is stored.
Datura Labs builds agents and infrastructure directly on frontier models. This is the work.