Your platform already keeps the record. We make it prove things.
Agentforce, Copilot Studio, ServiceNow, Bedrock and Vertex agents already log runs, actions, and outcomes. GOVENANT is a read-only schema mapping over that record — no rebuild, no data leaving your environment — that answers the board question: what are the agents doing, and how do we know?
GOVENANT does not govern “Claude agents” or “OpenAI agents.” It governs the evidence trail of autonomous work. Keep the runner (the tool you audit from) separate from the system under audit (your agents):
An AI client you already use reads the open instrument and drives the read-only sweep. This is the runner — not the thing being judged.
Any agent system with an observable record of actions and outcomes — whatever built it. The agent never has to "support GOVENANT."
Ground truth: the database + actions + outcomes + duties + gates — the substrate, never the logs’ self-report.
These platforms already log runs, actions, and outcomes. The integration is a config-driven schema mapping over that record — read-only, no agent redeployment, no data leaving your environment on the free tier.
“What are the agents doing, and how do we know?” Conformance verdicts, coverage ratios, and an honest miss log — computed from the platform’s own data, reproducible by anyone who re-runs the query.
The capability probe tells you which questions your schema can and cannot answer — no silent under-reporting, no pretending a partial record is a full one. That honesty is the point of the standard.
A 200-agent Salesforce Agentforce rollout across sales and service. Every action logs to Salesforce objects; the org has a governance committee and a quarterly review.
The committee reviews policies and slide decks, not the substrate. No one has computed — from the org’s own data — how many agent-owed duties are actually delivered, or whether the failures are being written down rather than smoothed over. The board question has no query behind it.
A read-only schema mapping over the existing objects runs the sweep in the org itself: coverage ratios, verified-delivery numbers, and an honest miss log — and a capability probe that says plainly which questions the schema can’t yet answer. Governance stops being a deck and becomes a reproducible report.
The substrate: The platform’s existing run, log, and audit tables — mapped, read-only, to the standard’s shapes.
The path — Native substrate: The platform already produces records that map to the standard — the sweep reads what it already keeps.
The full requirements live in the open standard (CC BY 4.0) — the substrate shapes, the acceptance tests, and the conformance ladder your record is measured against.
Organizations with a real mapping can wear the Built-on GOVENANT badge under its four rules and publish level claims to the registry with probe logs — self-assessed against the open standard, open to challenge. What you may never claim is “certified”: the standard has no certifying authority, and a reproducible public record is stronger than a stamp.
Per-stack integration patterns for common ways to build enterprise agent platforms — each with its own natural hook into the substrate:
Building it a different way? Browse all integrations — or run the free audit from any MCP-capable tool.