Wrap the loop. Ledger every act. Prove delivery.
Kernel function-invocation filters intercept every skill call — the ownership gate and the ledger write fit in a single filter.
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.
The pattern for code-first agent frameworks: A middleware/callback adapter over the framework’s own hooks: tools registered as levers, ownership checked at the call chokepoint, every action written to an append-only ledger, duty completion keyed to verified outcomes.
Why Semantic Kernel fits: Kernel function-invocation filters intercept every skill call — the ownership gate and the ledger write fit in a single filter.
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.
Integration pattern: documented (this page). The Semantic Kernel adapter, mapping, or worked example is being built in the open — progress, scope, and acceptance criteria live in the public GitHub issue. This page will not say “supported” before that issue closes with a working example. Holding our own pages to the standard’s claims discipline is not modesty; it is the product.
For agencies, consultancies, and product teams shipping on this stack: govern what you build and the governance record becomes the differentiator — every proposal ends with “and you’ll be able to prove it works.” We co-market shipped integrations, list governed implementations in the registry, and route inbound “govern my agents” demand for this stack to the people who built its adapter.
Different stack? Browse all 45 integrations — or run the free audit from any MCP-capable tool.