“Ticket closed” is a claim. “Problem resolved” is a record.
Support agents that deflect, answer, and “resolve” at scale are only trustworthy if resolution is verified, not self-reported. GOVENANT measures resolved-against-the-record, logs the escalations and abandons an internal dashboard would rather smooth over, and makes the whole thing reproducible.
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.
A closed ticket and a verifiably solved problem are different events; the gap between them is the performed-autonomy gap. The standard measures resolution against the record and writes down the reopens.
Your resolution rate is your platform grading itself. GOVENANT requires an independent watchdog for misses and numbers anyone can recompute — a record, not a self-graded metric.
A public delivery record with the misses included is the strongest CX trust asset there is, because it’s the one thing a vendor can’t comfortably fake.
An e-commerce brand lets an AI support agent auto-resolve tier-1 tickets; it closes 8,000 a week and reports a 90% deflection rate.
A closed ticket isn’t a solved problem. Nobody is measuring how many “deflected” customers reopened or churned — the deflection number and the trust number are drifting apart, and only one is on the dashboard.
With resolution verified against the record and reopens logged independently, verified resolution is 68% and a reopen spike traces to a broken returns flow the agent kept “resolving.” The brand can now show customers a delivery record with the misses in it — the one thing a competitor can’t fake.
The substrate: The ticket and conversation record: resolutions, reopens, escalations, CSAT — outcome rows a support agent’s “handled” is checked against.
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.
Wear the Built-on badge with a real integration; publish self-assessed levels to the registry with probe logs, open to challenge, never “certified.” A support org that can show verified resolution — misses and all — has a trust asset its competitors can only assert.
Per-stack integration patterns for common ways to build AI customer-service agents — 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.