Use GOVENANT and Claude Code together — govern the coding agents, not the framework. “Done” lives in the database, not in the model’s mouth.
A platform team runs a fleet of coding agents that open ~300 pull requests a week across forty repos. The dashboard is green; velocity is up and to the right.
Leadership can’t answer a board question: of everything the agents “shipped,” how much actually merged, passed CI, and stayed green — versus PRs that were opened, auto-approved by another agent, and quietly reverted three days later? Velocity counts motion; nobody is counting delivery.
Keyed to merged-and-green, the sweep shows 71% of agent PRs delivered — and surfaces a cluster of “completed” tasks whose deploys never went out and two repos where the agent was reviewing its own PRs. The number is lower than the dashboard, and for the first time it’s defensible.
The substrate: The repository: commits, pull requests, CI results, deploys — a terminal, verifiable record of what actually shipped.
The path — Native substrate: The platform already produces records that map to the standard — the sweep reads what it already keeps.
The substrate shapes and acceptance tests are open (CC BY 4.0): developer integration · the portable schema.
A real integration can wear the Built-on GOVENANT badge under its four rules from day one. The ladder — Logged → Gated → Delivered → Earned — is self-assessed against the open standard and published to the registry with probe logs, open to challenge. For coding agents the Delivered rung has teeth: it means the record shows verified shipped work, not activity.
This example is a documented reference pattern; the runnable adapter/mapping is being built in the open. It will never say “supported” or “certified” before a working example lands and its record is public — progress lives in the GitHub issue. Holding our own examples to the standard’s claims discipline is the product.
All sample projects · Govern coding agents · All integrations · Run the audit