AGT Conformance¶

Regulated buyers, auditors, and supply chain verifiers increasingly ask a single question before signing off on an agentic deployment: can you prove the agent was governed? An AGT conformance claim is how you answer that question — it asserts that your implementation correctly intercepts agent actions before execution, evaluates them against policy, enforces authorization decisions, and produces tamper-evident records that a third party can verify offline.

Conformance is verified by running the AGT spec conformance suite — nine test files, one per formal specification, each test annotated with the normative section it covers.

Conformance at a Glance¶

Conformance Levels¶

Baseline — Policy Engine and Audit¶

The non-negotiable minimum. If these six requirements fail, no governance claim holds.

Conformance tests: agent-governance-python/agent-os/tests/test_spec_policy_engine_conformance.py and test_spec_audit_compliance_conformance.py

Standard — Identity, Trust, and MCP Governance¶

Adds cryptographic agent identity and tool-call governance — the layer regulated buyers require before connecting agents to production data sources.

All Baseline requirements, plus:

Conformance tests: test_spec_identity_trust_conformance.py, test_spec_mesh_trust_conformance.py, test_spec_mcp_gateway_conformance.py, test_spec_adapter_contract_conformance.py

Advanced — Execution Control and Hardware Attestation¶

Adds execution isolation, liveness proof, and hardware-rooted signing. Required for deployments where the regulator or counterparty cannot trust the operator.

All Standard requirements, plus:

Conformance tests: test_spec_hypervisor_conformance.py, test_spec_sre_conformance.py, test_spec_lightning_conformance.py

Running the Conformance Suite¶

The nine conformance test files live alongside their respective packages. Each test is annotated with the spec section it covers. No custom pytest markers required — run the files directly.

Install¶

# Baseline
pip install -e "agent-governance-python/agent-governance-toolkit-core[dev]"

# Standard adds
pip install -e "agent-governance-python/agent-governance-toolkit-integrations[dev]"

# Advanced adds
pip install -e "agent-governance-python/agent-hypervisor[dev]"
pip install -e "agent-governance-python/agent-lightning[dev]"
pip install -e "agent-governance-python/agent-sre[dev]"

Run by level¶

pytest \
  agent-governance-python/agent-os/tests/test_spec_policy_engine_conformance.py \
  agent-governance-python/agent-os/tests/test_spec_audit_compliance_conformance.py \
  -v

pytest \
  agent-governance-python/agent-os/tests/test_spec_policy_engine_conformance.py \
  agent-governance-python/agent-os/tests/test_spec_audit_compliance_conformance.py \
  agent-governance-python/agent-mesh/tests/test_spec_identity_trust_conformance.py \
  agent-governance-python/agent-mesh/tests/test_spec_mesh_trust_conformance.py \
  agent-governance-python/agent-os/tests/test_spec_mcp_gateway_conformance.py \
  agent-governance-python/agent-os/tests/test_spec_adapter_contract_conformance.py \
  -v

pytest \
  agent-governance-python/*/tests/test_spec_*_conformance.py \
  -v

Run a single spec¶

# Just the Policy Engine
pytest agent-governance-python/agent-os/tests/test_spec_policy_engine_conformance.py -v

# Just MCP Gateway governance
pytest agent-governance-python/agent-os/tests/test_spec_mcp_gateway_conformance.py -v

# Just identity and trust
pytest agent-governance-python/agent-mesh/tests/test_spec_identity_trust_conformance.py -v

What passing looks like¶

PASSED  test_spec_policy_engine_conformance.py::TestSection10::test_pre_execution_interception_mandatory
PASSED  test_spec_policy_engine_conformance.py::TestSection7::test_policy_evaluation_deterministic
PASSED  test_spec_audit_compliance_conformance.py::TestSection3::test_merkle_chain_tamper_evidence
...

Each test name includes its spec section. A failed test tells you exactly which normative requirement your implementation violates.

Regulatory Alignment¶

Conformance levels map to regulatory obligations. The table below is indicative — your legal team determines what suffices for your jurisdiction.

Full regulatory crosswalk documentation is in the Compliance section.

Claiming Conformance¶

To register as AGT-conformant:

1. Run the suite for your target level and confirm all tests pass.
2. Link a CI run or test artifact that is publicly accessible (or sharable with maintainers under NDA for proprietary deployments).
3. Open a PR adding your implementation to ADOPTERS.md with: organization, implementation name, conformance level, test evidence link, and a maintainer contact.

Baseline and Standard claims¶

Advanced claims — additional requirements¶

Conformant Implementations¶

Microsoft reference implementations¶

Community¶

See ADOPTERS.md for the full adopter list, including organizations in evaluation.

Want your implementation listed? Follow the claiming conformance steps above.

Conformance and TRACE¶

Standard and Advanced conformance produce cryptographically signed audit records. TRACE takes this one step further: it binds the policy version, hardware measurement, and tool-call transcript into a single signed artifact that a third party — a regulator, counterparty, or auditor — can verify offline without trusting the operator.

AGT policy enforcement (conformant)
        ↓
cMCP gateway (TEE-enforced policy, hardware-attested)
        ↓
TRACE Trust Record (signed: model + policy + hardware measurement + transcript)
        ↓
SCITT transparency log (public, append-only anchor)

An Advanced AGT conformance claim combined with TRACE emission is what moves the answer to "can you prove it was governed?" from we have logs to here is a signed artifact, verifiable offline, rooted in silicon.

• TRACE specification — the open attestation format
• cMCP — reference implementation of AGT policy enforcement inside a confidential TEE with TRACE claim emission
• TRACE registry — public Merkle anchor log

Versioning¶

This page documents AGT conformance v1.0, corresponding to the 1.0 release of each formal specification. Specification versions are pinned in each spec file header. Conformance claims should record the spec version used for verification.

When specifications advance to v2.0, existing v1.0 claims remain valid for the specs they covered. The conformance suite version is recorded in agent-governance-python/agent-governance-toolkit-core/src/agent_os/conformance/version.py.

Related¶

• TESTING_GUIDE.md — how to use the test suite end-to-end
• Integration Tiers — governance depth at Tier 0 (sidecar), Tier 1 (SDK), and Tier 2 (deep hooks)
• CSA ATF Conformance Assessment — AGT's self-assessment against the CSA Agentic Trust Framework (25/25 requirements, Senior maturity)
• Specifications — the normative specs each requirement references
• ADOPTERS.md — full adopter registry