In legal work, “I reviewed it” has to be provable.
Agents that review contracts, redline, summarize matters, and prepare filings operate where an unverified “done” is a liability, not a convenience. GOVENANT records what each agent actually did to the matter record, pins the high-consequence actions to human approval, and keeps a reproducible trail.
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.
Earned autonomy means the risky moves — filing, sending, binding the client — are pinned to human approval forever, in code no configuration defeats. Agents accelerate the work; they don’t take the pen.
Every action is an append-only row: which document, which change, which citation, verified against the artifact. When a partner, a client, or opposing counsel asks what happened, the answer is a record — not a recollection.
The clause never checked, the deadline never docketed, the matter untouched for a week — coverage against the duty roster makes the omission the alarm, which is exactly the failure legal teams most fear.
A mid-size firm uses agents to review inbound contracts and draft first-pass redlines; associates review the output before it goes out.
When a clause is missed, there’s no record of what the agent actually checked versus what it claimed — and no enforced guarantee that a human authorized anything that left the building. “The AI reviewed it” has to be provable, and right now it isn’t.
Every redline, flag, and draft becomes a verified action row against the document; filing and sending are pinned to human approval in code. The record shows one matter type where a required clause check silently never ran — caught by coverage math, not by a missed deadline.
The substrate: The matter and document record: redlines applied, clauses flagged, documents generated, filings prepared — verifiable artifacts, checked against what the agent claims it did.
The path — Instrumented boundary: Add a thin hook at the action boundary — no access to prompts, reasoning, or models — so every action and its outcome is recorded.
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.
A real integration wears the Built-on badge; levels are self-assessed against the open standard and published with probe logs — never “certified,” and never a substitute for professional responsibility. What it gives a legal team is an inspectable record that the agent-assisted work happened as claimed.
Per-stack integration patterns for common ways to build AI legal & contract 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.