Skip to main content
// FILE 03 · THE WRITING

ESSAYS & MANIFESTOS

Long-form pieces on protocol design, the privacy layer, and infrastructure that holds up under audit. No schedule. Published when there is something worth saying.

7 entries / updated Jul 2026

2026

15 min

Load-Bearing Memory: The Bones Remember

In April someone gave the third layer of the agent stack a name. The name is context. It is the wrong name, and the wrong name is the reason nobody has built the right thing.

#agents#receipts#evidence
12 min

Order of Arrival

The part you recognize a thing by and the part that makes it durable are almost never the same part. A note, a dog, and a system, on the same argument.

#core-and-transient#architecture#strategy
8 min

The Unarmed Gate

I run every session with permissions bypassed. That is not the absence of a floor. It is the removal of one that was never load bearing, and the installation of one that is.

#agents#receipts#sovereignty
5 min

The Dumb Lock

There is a room under every life now. A low hum of everything you have ever written down, every contact, every decision with its reasons still attached, sitting in one place and vibrating at a frequency only you are supposed to hear.

#memory#sovereignty#architecture
6 min

The Substructure Signal: What Ledgers Expose When Systems Hit Their Breaking Point

A ledger is a record. A tolerance limit is a wall. When a system hits that wall, the ledger becomes the only witness that matters. A short essay on why the deepest truth about any system lives in its low frequencies.

#systems#architecture#sovereignty
5 min

AIP by AIP: Proof of Build

How I'm using the protocol I built to prove I built the protocol. A short note on the Proof of Build loop, why it compounds, and why AIP will forever be validated by AIP.

#aip#proof-of-build#selective-disclosure
6 min

Why AIP exists

AIP is the receipts layer for autonomous agents. A local, signed, hash-chained audit log is the product; the handshake is just the warm-up.

#aip#protocols#interoperability
Context is a retrieval word. It describes something you fetch and put in front of a model so it answers better. Under that name the design space collapses into a search problem: embed better, rank better, forget less. Every system built in that lane...Here is what changed. I stopped thinking of the prompt as a wall and started hearing it for what it actually is, which is a doorbell with no door behind it. It rings on everything. It rings the same way for a directory listing and for a command that...I adopted Copper, an Australian cattle dog, which means he likes to work. I have never raised this breed before, so I enlisted a consultant.There is a room under every life now. A low hum of everything you have ever written down, every contact, every decision with its reasons still attached, sitting in one place and vibrating at a frequency only you are supposed to hear. The industry...There is a frequency beneath every system that most people never hear. A low, humming truth that sits under the noise and the polish and the architecture diagrams. You only notice it when the pressure rises. When the cables buzz. When the whole...An autonomous software agent is a program that takes a goal, makes a plan, calls tools, and produces an output. Many such agents exist. They are built by different teams, on different runtimes, with different model backends, and they live in...Every protocol has to answer the same first question: how do you know it's the real one? AIP answers that question with itself. The protocol I built is the system I used to build the protocol. Each piece of proof I produce is itself a build event....