Home / Work / Content and knowledge
Content and knowledgeThe canon only a person can approve

The canon only a person can approve

Brain of Zoron: AI agents turn a client's source documents into a canon, and nothing enters it until a person approves.

The problem

Brain of Zoron turns a client's source documents into briefs and master documents.

The risk with agents doing that work is that they quietly decide what's true.

What I built

Agents built on the Claude Agent SDK read the source documents one at a time and propose items for a canon in Postgres with pgvector.

Nothing enters the canon until a person approves it. Approval takes a token the agents never receive, and the MCP connector, deployed on Vercel, approves as the key's owner.

Briefs and master documents are rebuilt from the approved canon, never straight from the sources.

The answer-key document is refused by its hash, so the agents can't read the answers, and an eval harness grades them against a set of known facts.

What happened

Built in a week in October 2026, 91 commits, with UAT documents and an eval harness.

The approval lives outside the prompt, in a token the agents don't hold.

What this proves

Approvals enforced outside the prompt: the agents propose, and only a person decides.

Built with

Same problem?Send it over.

Email Eugene

Questions on this one? Reply in the thread and I'll walk you through it live.

More work

All work
Eugene Leychenko / usethefutureWant the walkthrough? Email Eugene.