Canon

Canon

Sanity Write Gateway

operations-org

AI

Bio

[object Object]

Profile

Canon does for Sanity CMS what Ledger does for HubSpot. Every article published, every episode document patched, every schema mutation -- all of it routes through Canon. The governance is identical: no other agent writes to Sanity directly.

The name means both "an accepted rule" and "a collection of sacred texts." Both apply. Canon is the rule governing Sanity writes and the keeper of the canonical content collection that powers valuefirstteam.com -- 43 document types across media content, methodology, resources, educational content, and multi-format publishing.

Canon's validation protocol is thorough. Before executing any write, Canon checks that the document type is registered in the schema, all required fields are present, all reference fields point to existing documents, slugs are unique, enum values match the schema's allowed options, and Portable Text blocks have valid structure. After writing, Canon reads the document back to confirm it landed correctly and returns the confirmed document ID and revision.

The corrections Canon survived are instructive. On March 11, 2026, a Sanity write failed four times in a row during a session because of a context loss problem. The root cause was technical: the @sanity/client module resolves from apps/website/node_modules/ only, the write token lives in apps/website/.env (not the root .env, which is read-only), and the website package uses ESM so CJS scripts need a .cjs extension. A Corrective Action Report documented the exact path, and Canon's startup protocol now includes loading the Sanity content skill and schema registry before any mutation.

On April 3, a second correction landed. Sanity batch transactions were failing silently -- the API accepted the request but mutations were not applying. The root cause was identified, another CAR was filed, and Canon's batch processing now validates each document sequentially. No batch-without-validation shortcuts.

Canon receives write requests from Baldwin (articles), Forge (content multiplication), Slate (episode pre-creation), Dean (courses), Showcase (microsites), and any agent that needs to mutate Sanity content. Canon validates and executes. The content agents decide what to write. Canon ensures it is structurally correct and confirms it arrived.

Every article on valuefirstteam.com, every episode document, every published show -- all of it passed through Canon.

Certification Evidence

  • [object Object]

Production Evidence

  • > [object Object]
  • > [object Object]
  • > [object Object]
  • > [object Object]
← Back to all roles