Decision Provenance Is Not Authority Provenance
Tracing how an outcome was produced is not proving the actor was entitled to cause the effect.
2026-07-24 · 2-min read
Doctrine, plainly argued: the adjacent layers people mistake for authority — and the one line that separates each from the right to let an AI agent act. Each post reads in under two minutes.
Eight adjacencies, one boundary. Every post resolves to the same place: Authority Finality™.
Tracing how an outcome was produced is not proving the actor was entitled to cause the effect.
2026-07-24 · 2-min read
Compiling a clause into code proves the rule is satisfiable — not that anyone may act on it.
2026-07-22 · 2-min read
Shaping how a model reasons is not deciding whether its conclusion may become an action.
2026-07-21 · 2-min read
A key proves the caller can reach the API. It never proves the caller should have made the call.
2026-07-20 · 2-min read
Knowing who the agent is answers the door. It does not decide what it may do inside.
2026-07-19 · 2-min read
A permit says the action is allowed. Authority says this principal may take it, here, now.
2026-07-18 · 2-min read
A trace tells you what happened. Authority decides whether it was permitted to.
2026-07-17 · 2-min read
Watching an agent act is not the same as deciding it was allowed to.
2026-07-16 · 2-min read
The blog is one format over the same governed content the rest of the site publishes.
Governed, replay-verifiable reports — every claim pinned to a cited source.
What shipped and when — the one canonical, generated update feed.
Glossary, frameworks, and explainers — the AI governance education hub.