AGEF

AGEF (Agent Governance Evidence Format) defines how an AI agent session gets serialized into a portable, tamper-evident bundle: content-addressed objects plus Merkle-linked events that can be transferred across systems, verified offline, and reviewed by independent tooling. The core workflow is that a conforming substrate records agent events during a session, exports them as an AGEF bundle (per SPEC.md Sections 5–14), and any downstream tool — an auditor’s workstation, an incident responder’s isolated environment — can import and verify the bundle without calling back to the original system.

The format’s primary differentiator is cryptographic independence. Because events are content-addressed and Merkle-linked, verification does not require the original agent system to be running or trusted. An auditor can replay the session deterministically against the recorded tools and providers, which is exactly what SOC 2, FDA, SEC, and similar regulatory frameworks require when they ask you to prove what your agent did and that the record was not altered after the fact.

AGEF fits teams who own their agent infrastructure and are willing to build conforming bundle producers. The spec defines two conformance profiles — Bundle Profile (producing and consuming bundles) and Substrate Profile (maintaining the event journal) — and the only shipped reference implementation is Akmon v2.0.0 and later. Teams not running Akmon have no off-the-shelf exporter; they implement the spec themselves. At v0.1.1, this is a pre-stable format, which means the structure can change before a stable release and teams building against it should track CHANGELOG.md and SPEC.md closely.

Licensing is split: the specification text is released under CC BY 4.0 and the code under Apache-2.0, so organizations can adopt and implement the format without commercial licensing concerns. The repository includes a minimal-bundle example under the examples directory, which is the primary onboarding artifact for teams evaluating implementation scope.