Wrap the loop. Ledger every act. Prove delivery.
LangGraph, CrewAI, AutoGen, the OpenAI and Claude Agent SDKs — code-first frameworks give you the hooks; GOVENANT rides them to make every tool call answer for itself. The framework keeps running your agents; the adapter makes their work provable.
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.
Every tool call becomes an append-only action row: input, output, cost, verified outcome. When a customer, an auditor, or your own CEO asks what the agents did, the answer is a query, not a vibe.
The adapter rides the framework’s existing callback and middleware points — no rewrite, no new runtime, no lock-in. The standard is open under CC BY 4.0 and the method is free forever under the covenant.
Agents that look busy but don’t verifiably ship are this generation’s failure mode. The sweep measures verified outcomes against the record — never the logs’ self-report.
A data team ships a LangGraph system: a planner, three specialists, and a critic, handing off through a shared state graph in production.
When an output is wrong, no one can say which node did what, whether the critic actually ran, or whether a tool call that “succeeded” changed anything downstream. The graph is a black box the moment it leaves a notebook.
Riding the checkpointer and callbacks, every node’s tool calls become append-only action rows with verified outcomes. The record shows the critic silently short-circuited on 12% of runs and one specialist’s “done” never wrote to the warehouse — invisible before, a query now.
The substrate: The framework’s own callbacks and middleware: run IDs, tool inputs/outputs, and cost — everything an append-only action row needs.
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.
From day one of a real integration you can wear the Built-on GOVENANT badge under its four rules — real integration, a disclosure line, a link to the standard, no certification implication. From there the ladder is public: Logged → Gated → Delivered → Earned. Levels are self-assessed against the open standard and published to the registry with their probe logs, open to anyone’s challenge — no authority hands out stamps, which is exactly why a published record means something.
Per-stack integration patterns for common ways to build multi-agent frameworks — 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.