TL;DR
The whole argument, nine lines.
If this is all you read, you have the shape. Everything below is the proof and the detail.
1
The ground most of us build on belongs to somebody else: a landlord, a vendor, a platform, a grant upstream. When it moves, the work goes with it.
2
You cannot coordinate durably on sand. Connection needs ground that does not shift.
3
Put the rule in the wiring, not the prompt. A rule kept by the data store cannot be talked out of by anything a machine reads.
4
One rule does three jobs at once: it keeps your story yours, it governs what the machines read and write, and it holds no matter what anyone types. That interlock is the one new thing here.
5
You can hand someone your whole story and lose nothing, because your sovereignty lives in the rule underneath, not in the file.
6
The machine works backward from the goal and keeps going until the goal is actually met. I call that reverse navigation, after the man who taught it to me.
7
Connect without exposure: a capability instead of a login, scoped to assigned records, revocable in a second.
8
Stand it up yourselves, on ground you hold. Nobody has to say yes.
9
I filed five patent applications in December 2025 and let four of them go; the first is still technically pending until I decide by December 2026. I published this instead, so nobody can lock it up. It is yours.
The story
Five parts, in order.
A story first, because the method only makes sense once you have felt the thing it fixes. Each part is its own page with its own pace.
Part One · 14 min
Building on sand
A grocery store, a signed lease, a changed lock, and the five ways the ground gives way under people who did everything right.
Part Two · 7 min
Ground that holds
The actual path a request travels, from a cracked phone to a link that comes back, and six scenes where the same ground holds.
Part Three · 12 min
Three secrets
The rule goes in the wiring. You can hand someone your whole story and lose nothing. One rule does three jobs at once. Then the culture that runs it.
Interlude · 5 min
Why I could see it
A parachuting accident, a thousand-dollar toll, a satellite wire, and what Stanford said this year about judgment and oversight.
Part Four · 9 min
The demons
Enclosure, the manufactured moat, the toll, the standing door, the ones who cut you off, the fencers. Then the eight doubts inside you.
Part Five · 2 min
Pick it up
Fork the kit, author your SOUL, build the other two legs where you are, point it at your own gap, run the culture, keep it open.
The build · 3 min
One application: the reference build
One application: Postgres, row-level security, a capability-scoped connection proven across machines, and a research run at real scale.
The depth
For whoever wants to go all the way down.
The argument above is complete without this. The depth is the detail: every concept named, the mechanics, the delivery layer, where it lands, and the methodology stated precisely.
Reference
The concepts, by name
Every term the method uses, each defined in a few lines: membrane, seat, holon, SOUL, the per-record rule, reverse navigation, the translating modem, and the rest.
Reference
How it works, in detail
The interlock mechanically, joining and composing, public and private on one rule, rented capacity under owned governance, the loop, compounding.
Reference
The translating modem
One conserved source, form as a free variable, the gate that conserves meaning, the reader's dial, visibility as a switch you hold, and the pipeline so anyone can build it.
Reference
Where it lands
Teaching, community memory, tribute, the traversal, the thinnest body, a cognitive prosthetic, federation, waste to value, Fort Lupton, seasonal events, dissemination.
Reference
The work this stands on
The prior work each leg stands on, named and credited, and the one thing that was new.
Reference
The methodology, stated precisely
Thirty-eight numbered statements of the methodology, written to be precise enough to stand as prior art.
I filed, and I chose not to fence this. I published it instead, so that nobody can. It is yours.