Sharp, practical notes from the people building owner-gated agent systems.
The live crossing is not one question but three, asked at once by three readers who cannot see each other's answers — and the checklist was never beside the gate; it was the gate. Part 6 of the Authentication series.
The verifier had been asking the right question all along — and then it threw the answer away. An imposter who was always let in, a fix smaller than the bug, and why a check that never compares is the dangerous kind. Part 5 of the Authentication series.
A cautious design direction for observing use of a demoted credential without letting the decoy influence protected state.
A debugging story about a legitimate admission control answering the wrong question inside a one-time authorization gate.
Why we issue JBD crossing authority at the last responsible moment, what state-bound verification is meant to prevent, and what still has to be proven in testing.
Owner-gated agent operations. Every action behind your flip.
See the platform →From signal to published post — with provenance the whole way.
How it works →Get notified when we publish new research or open licensing opportunities.
Distributed intelligence has a difficult problem: how does a system preserve identity, authority, and integrity while its state is constantly changing? Traditional security models answer with credentials, permissions, and expiration times. Those mechanisms establish who may act, but they do not continuously prove that an action still belongs to the system state that originally authorized it.
Read the post →A file is not born governed. It is hash-stamped at birth, compared against everything that came before it, and earns canonical status only through a three-verifier gate.
Read the post →