agentrust-trace 0.2.0__tar.gz → 0.3.0__tar.gz

agentrust_trace-0.3.0/.github/workflows/docs.yml

@@ -0,0 +1,72 @@
+name: Docs
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - "docs/**"
+      - "spec/**"
+      - "mkdocs.yml"
+      - "requirements-docs.txt"
+      - "README.md"
+      - "CHANGELOG.md"
+      - "CONTRIBUTING.md"
+      - "GOVERNANCE.md"
+      - "ROADMAP.md"
+      - "LIMITATIONS.md"
+      - "CNAME"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+concurrency:
+  group: docs-deploy
+  cancel-in-progress: false
+
+jobs:
+  deploy:
+    name: Build and deploy docs
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+          cache: pip
+
+      - name: Install docs dependencies
+        run: |
+          pip install -r requirements-docs.txt
+          pip install -e ".[dev]"
+
+      - name: Configure git for gh-deploy
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Assemble docs build directory
+        run: |
+          BUILD=.docs_build
+          mkdir -p $BUILD
+
+          if [ -d docs ]; then cp -r docs $BUILD/docs; fi
+          if [ -d spec ]; then cp -r spec $BUILD/spec; fi
+          if [ -d examples ]; then cp -r examples $BUILD/examples; fi
+
+          for fname in README.md CHANGELOG.md CONTRIBUTING.md GOVERNANCE.md ROADMAP.md LIMITATIONS.md CNAME; do
+            if [ -f "$fname" ]; then cp "$fname" "$BUILD/$fname"; fi
+          done
+
+          echo "Build dir contains $(find $BUILD -type f | wc -l) files"
+
+      - name: Generate build config
+        run: |
+          sed 's|^docs_dir: \.$|docs_dir: .docs_build|' mkdocs.yml > .mkdocs_build.yml
+
+      - name: Build and deploy to GitHub Pages
+        run: mkdocs gh-deploy --force --clean --config-file .mkdocs_build.yml

{agentrust_trace-0.2.0 → agentrust_trace-0.3.0}/ADOPTERS.md

@@ -8,4 +8,4 @@ To add your organization, open a pull request editing this file.
 
 | Organization | Usage |
 |---|---|
-| Opaque Systems | Founding contributor — developed the initial specification, reference implementation, and TRACE registry infrastructure |
+| OPAQUE Systems | Founding contributor — developed the initial specification, reference implementation, and TRACE registry infrastructure |

{agentrust_trace-0.2.0 → agentrust_trace-0.3.0}/CHANGELOG.md

@@ -9,6 +9,19 @@ Format: [Semantic Versioning](https://semver.org/). Spec versions follow `MAJOR.
 
 ---
 
+## [0.3.0] — 2026-06-30
+
+### Security
+
+- `verify_record` now requires an explicit trusted key. Self-verification from the embedded `cnf.jwk` is no longer the default; use `allow_embedded_key=True` to opt in.
+- Verification enforces freshness (`iat` / `max_age_seconds`, default 24h) and an optional `expected_nonce`. JWK `kty` / `crv` are validated.
+
+### Breaking
+
+- **BREAKING:** Canonicalization is now RFC 8785 (JCS). Trust records are NOT cross-verifiable with 0.2.0 (the prior `json.dumps` canonicalization was non-conformant).
+
+---
+
 ## [0.1.0] — 2026-06-23
 
 Initial public draft. Announced at Confidential Computing Summit, San Francisco.
@@ -35,7 +48,7 @@ Initial public draft. Announced at Confidential Computing Summit, San Francisco.
 
 ### Open questions
 
-Seven open questions requiring founding-member input before v0.2 are documented in §7 of the spec.
+Seven open questions requiring community input before v0.2 are documented in §7 of the spec.
 
 ---
 

agentrust_trace-0.3.0/CNAME

@@ -0,0 +1 @@
+trace.agentrust-io.com

{agentrust_trace-0.2.0 → agentrust_trace-0.3.0}/MAINTAINERS.md

@@ -4,7 +4,7 @@
 
 | Name | Affiliation | GitHub | Contact |
 |---|---|---|---|
-| Imran Siddique | OPAQUE Systems | @imraan | imran.siddique@opaque.co |
+| Imran Siddique | OPAQUE Systems | @imraan | maintainers@agentrust.io |
 
 The Project Lead has final decision authority on specification changes, AAIF/CoSAI submission scope, conformance requirements, and Maintainer appointments.
 

{agentrust_trace-0.2.0 → agentrust_trace-0.3.0}/NOTICE

@@ -1,7 +1,7 @@
 TRACE
-Copyright 2026 AgentTrust Authors
+Copyright 2026 AgenTrust Authors
 
-This product includes software developed by the AgentTrust project
+This product includes software developed by the AgenTrust project
 (https://github.com/agentrust-io/trace-spec).
 
 ---

agentrust_trace-0.3.0/PKG-INFO

@@ -0,0 +1,106 @@
+Metadata-Version: 2.4
+Name: agentrust-trace
+Version: 0.3.0
+Summary: TRACE v0.1 — hardware-attested governance records for AI agents
+Project-URL: Homepage, https://github.com/agentrust-io/trace-spec
+Project-URL: Repository, https://github.com/agentrust-io/trace-spec
+Project-URL: Issues, https://github.com/agentrust-io/trace-spec/issues
+Project-URL: Changelog, https://github.com/agentrust-io/trace-spec/blob/main/CHANGELOG.md
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: ai-governance,attestation,confidential-computing,eat,rats,tee,trace
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: cryptography>=42.0
+Requires-Dist: jsonschema>=4.20
+Requires-Dist: pydantic>=2.0
+Requires-Dist: rfc8785>=0.1.2
+Provides-Extra: dev
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Requires-Dist: types-jsonschema; extra == 'dev'
+Description-Content-Type: text/markdown
+
+<p align="center">
+  <img src="docs/assets/icon.svg" width="96" height="96" alt="TRACE"/>
+</p>
+
+# TRACE: Trust Runtime Attestation and Compliance Evidence
+
+<p align="center">
+  <a href="https://trace.agentrust-io.com">
+    <img src="https://img.shields.io/badge/%F0%9F%93%96_Full_Documentation-trace.agentrust--io.com-8251EE?style=for-the-badge&logoColor=white" alt="Full Documentation" height="40">
+  </a>
+</p>
+
+<p align="center">
+  <a href="spec/trace-v0.1.md">Specification</a> &nbsp;|&nbsp;
+  <a href="schema/trace-claim.json">Schema</a> &nbsp;|&nbsp;
+  <a href="examples/">Examples</a> &nbsp;|&nbsp;
+  <a href="https://github.com/agentrust-io/trace-registry">Registry</a> &nbsp;|&nbsp;
+  <a href="https://github.com/agentrust-io/trace-tests">Test Suite</a> &nbsp;|&nbsp;
+  <a href="https://github.com/agentrust-io/cmcp">Reference Impl</a>
+</p>
+
+[![License: CC BY 4.0](https://img.shields.io/badge/License-CC_BY_4.0-lightgrey.svg)](LICENSE)
+[![Spec](https://img.shields.io/badge/Spec-v0.1-0ea5e9)](spec/trace-v0.1.md)
+[![PyPI](https://img.shields.io/pypi/v/agentrust-trace)](https://pypi.org/project/agentrust-trace/)
+[![CI](https://github.com/agentrust-io/trace-spec/actions/workflows/ci.yml/badge.svg)](https://github.com/agentrust-io/trace-spec/actions/workflows/ci.yml)
+[![Discord](https://img.shields.io/badge/Discord-Join-5865F2?logo=discord&logoColor=white&style=flat)](https://discord.gg/grgzFEHgkj)
+
+> **Developer Preview.** Launching at Confidential Computing Summit, June 23 2026.
+
+An open specification for hardware-attested AI agent governance records. TRACE defines the format, anchoring protocol, and verification rules for cryptographically provable evidence that an AI agent ran under a specific policy, in a verified hardware environment, on classified data, invoking identified tools — bound into a single signed artifact rooted in silicon attestation.
+
+A TRACE Trust Record answers: _what ran, where, under which policy, touching which data, calling which tools_ — in a form any third party can verify without trusting the operator.
+
+## Quick start
+
+```bash
+pip install agentrust-trace
+```
+
+```python
+from agentrust_trace import TrustRecord, sign_record
+
+record = TrustRecord(
+    subject="spiffe://trust.example.org/agent/payments-processor",
+    model_id="claude-sonnet-4-6",
+    platform="amd-sev-snp",
+    policy_hash="sha256:b2c3d4...",
+)
+signed = sign_record(record, key=signing_key)
+```
+
+## Resources
+
+| | |
+|---|---|
+| 📖 Full documentation | [trace.agentrust-io.com](https://trace.agentrust-io.com) |
+| 📄 Specification | [spec/trace-v0.1.md](spec/trace-v0.1.md) |
+| 🔍 Schema | [schema/trace-claim.json](schema/trace-claim.json) |
+| 📦 PyPI | [agentrust-trace](https://pypi.org/project/agentrust-trace/) |
+| 🧪 Test suite | [trace-tests](https://github.com/agentrust-io/trace-tests) |
+| 🗂 Registry | [trace-registry](https://github.com/agentrust-io/trace-registry) |
+| 🔗 Reference implementation | [cmcp](https://github.com/agentrust-io/cmcp) |
+| 💬 Discussions | [GitHub Discussions](https://github.com/orgs/agentrust-io/discussions) |
+| 📋 Changelog | [CHANGELOG.md](CHANGELOG.md) |
+
+## Standards alignment
+
+Targeting the [Agentic AI Foundation (AAIF)](https://agenticai.foundation) at the Linux Foundation. Active standardization track in [CoSAI WS4](https://github.com/oasis-open-projects/coalition-for-secure-ai). Builds on [RFC 9711 (EAT)](https://www.rfc-editor.org/rfc/rfc9711), [RFC 9334 (RATS)](https://www.rfc-editor.org/rfc/rfc9334), and SCITT draft-22.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) and [GOVERNANCE.md](GOVERNANCE.md). All contributors must agree to the [ANTITRUST.md](ANTITRUST.md) policy.

agentrust_trace-0.3.0/README.md

@@ -0,0 +1,72 @@
+<p align="center">
+  <img src="docs/assets/icon.svg" width="96" height="96" alt="TRACE"/>
+</p>
+
+# TRACE: Trust Runtime Attestation and Compliance Evidence
+
+<p align="center">
+  <a href="https://trace.agentrust-io.com">
+    <img src="https://img.shields.io/badge/%F0%9F%93%96_Full_Documentation-trace.agentrust--io.com-8251EE?style=for-the-badge&logoColor=white" alt="Full Documentation" height="40">
+  </a>
+</p>
+
+<p align="center">
+  <a href="spec/trace-v0.1.md">Specification</a> &nbsp;|&nbsp;
+  <a href="schema/trace-claim.json">Schema</a> &nbsp;|&nbsp;
+  <a href="examples/">Examples</a> &nbsp;|&nbsp;
+  <a href="https://github.com/agentrust-io/trace-registry">Registry</a> &nbsp;|&nbsp;
+  <a href="https://github.com/agentrust-io/trace-tests">Test Suite</a> &nbsp;|&nbsp;
+  <a href="https://github.com/agentrust-io/cmcp">Reference Impl</a>
+</p>
+
+[![License: CC BY 4.0](https://img.shields.io/badge/License-CC_BY_4.0-lightgrey.svg)](LICENSE)
+[![Spec](https://img.shields.io/badge/Spec-v0.1-0ea5e9)](spec/trace-v0.1.md)
+[![PyPI](https://img.shields.io/pypi/v/agentrust-trace)](https://pypi.org/project/agentrust-trace/)
+[![CI](https://github.com/agentrust-io/trace-spec/actions/workflows/ci.yml/badge.svg)](https://github.com/agentrust-io/trace-spec/actions/workflows/ci.yml)
+[![Discord](https://img.shields.io/badge/Discord-Join-5865F2?logo=discord&logoColor=white&style=flat)](https://discord.gg/grgzFEHgkj)
+
+> **Developer Preview.** Launching at Confidential Computing Summit, June 23 2026.
+
+An open specification for hardware-attested AI agent governance records. TRACE defines the format, anchoring protocol, and verification rules for cryptographically provable evidence that an AI agent ran under a specific policy, in a verified hardware environment, on classified data, invoking identified tools — bound into a single signed artifact rooted in silicon attestation.
+
+A TRACE Trust Record answers: _what ran, where, under which policy, touching which data, calling which tools_ — in a form any third party can verify without trusting the operator.
+
+## Quick start
+
+```bash
+pip install agentrust-trace
+```
+
+```python
+from agentrust_trace import TrustRecord, sign_record
+
+record = TrustRecord(
+    subject="spiffe://trust.example.org/agent/payments-processor",
+    model_id="claude-sonnet-4-6",
+    platform="amd-sev-snp",
+    policy_hash="sha256:b2c3d4...",
+)
+signed = sign_record(record, key=signing_key)
+```
+
+## Resources
+
+| | |
+|---|---|
+| 📖 Full documentation | [trace.agentrust-io.com](https://trace.agentrust-io.com) |
+| 📄 Specification | [spec/trace-v0.1.md](spec/trace-v0.1.md) |
+| 🔍 Schema | [schema/trace-claim.json](schema/trace-claim.json) |
+| 📦 PyPI | [agentrust-trace](https://pypi.org/project/agentrust-trace/) |
+| 🧪 Test suite | [trace-tests](https://github.com/agentrust-io/trace-tests) |
+| 🗂 Registry | [trace-registry](https://github.com/agentrust-io/trace-registry) |
+| 🔗 Reference implementation | [cmcp](https://github.com/agentrust-io/cmcp) |
+| 💬 Discussions | [GitHub Discussions](https://github.com/orgs/agentrust-io/discussions) |
+| 📋 Changelog | [CHANGELOG.md](CHANGELOG.md) |
+
+## Standards alignment
+
+Targeting the [Agentic AI Foundation (AAIF)](https://agenticai.foundation) at the Linux Foundation. Active standardization track in [CoSAI WS4](https://github.com/oasis-open-projects/coalition-for-secure-ai). Builds on [RFC 9711 (EAT)](https://www.rfc-editor.org/rfc/rfc9711), [RFC 9334 (RATS)](https://www.rfc-editor.org/rfc/rfc9334), and SCITT draft-22.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) and [GOVERNANCE.md](GOVERNANCE.md). All contributors must agree to the [ANTITRUST.md](ANTITRUST.md) policy.

{agentrust_trace-0.2.0 → agentrust_trace-0.3.0}/ROADMAP.md

@@ -9,7 +9,7 @@ Announced at Confidential Computing Summit, San Francisco, June 23 2026.
 - Wire formats: EAT/JWT and CBOR-COSE
 - Hardware roots: NVIDIA H100/Blackwell, Intel TDX, AMD SEV-SNP, Azure MAA, GCP Confidential Space, AWS Nitro
 - JSON Schema and three hardware examples
-- Reference implementation: cMCP Phase 1 (runtime trust, no policy enforcement)
+- Reference implementation: cMCP Phase 1 (Cedar policy enforcement, TRACE Level 2 emission)
 
 **Not in v0.1:** MCP profile (normative), A2A profile, vendor platform annexes, OWASP/ATLAS cross-walks, encrypted claims envelope.
 
@@ -45,4 +45,4 @@ Driven by founding-member feedback and open questions from §7 of the spec.
 
 ## Influencing the roadmap
 
-Open a GitHub issue with the `spec` or `roadmap` label. Founding-member and vendor feedback from the CC Summit period (June–September 2026) has priority for v0.2 scope.
+Open a GitHub issue with the `spec` or `roadmap` label. Contributor and community feedback from the CC Summit period (June–September 2026) has priority for v0.2 scope.

{agentrust_trace-0.2.0 → agentrust_trace-0.3.0}/docs/assets/icon.svg

@@ -2,14 +2,16 @@
   <defs>
     <linearGradient id="bg" x1="0" y1="0" x2="1" y2="1">
       <stop offset="0%" stop-color="#f5f3ff"/>
-      <stop offset="100%" stop-color="#e0f2fe"/>
+      <stop offset="100%" stop-color="#ede9fe"/>
     </linearGradient>
     <linearGradient id="brand" x1="0" y1="0" x2="1" y2="1">
-      <stop offset="0%" stop-color="#7c3aed"/>
-      <stop offset="100%" stop-color="#0ea5e9"/>
+      <stop offset="0%" stop-color="#5BD2BE"/>
+      <stop offset="50%" stop-color="#8251EE"/>
+      <stop offset="100%" stop-color="#C661F7"/>
     </linearGradient>
   </defs>
   <rect width="400" height="400" fill="url(#bg)"/>
+  <!-- Shield -->
   <path d="M200,58 L326,112 L326,224 C326,298 268,340 200,360 C132,340 74,298 74,224 L74,112 Z"
         fill="url(#brand)" opacity="0.10" stroke="url(#brand)" stroke-width="3.5" stroke-linejoin="round"/>
   <!-- Eye outline -->

agentrust_trace-0.3.0/docs/glossary.md

@@ -0,0 +1,68 @@
+# Glossary
+
+Terms used in the TRACE specification and documentation.
+
+---
+
+**Appraisal**
+The process of evaluating a TEE evidence bundle against a reference integrity manifest (RIM) to produce an `appraisal.status` verdict. An `"affirming"` verdict means the measured environment matches the expected state. Defined in IETF RFC 9334 (RATS).
+
+---
+
+**cnf / JWK**
+The TRACE `cnf` field (from RFC 7800) carries a JSON Web Key (`jwk` sub-field) that contains the Ed25519 public key used to sign the record. It is included in the signed payload so the verifier does not need to retrieve the key out-of-band.
+
+---
+
+**Conformance**
+A trust record is conformant if it passes all test cases required at its declared trust level. Conformance is verified by the `trace-tests` test suite. Partial conformance (record passes some but not all required tests) is not valid.
+
+---
+
+**EAT — Entity Attestation Token**
+A JWT-based format for conveying evidence about a hardware or software entity. TRACE records use the EAT `eat_profile` claim to identify the specific TRACE profile version. Defined in IETF draft-ietf-rats-eat.
+
+---
+
+**GatewayClaim**
+A cMCP claim embedded in a TRACE trust record that binds the record to a specific cMCP session. Contains the session ID, gateway DID, and the Cedar policy bundle hash that governed the session.
+
+---
+
+**JCS — JSON Canonicalization Scheme**
+RFC 8785. A deterministic serialization of JSON objects: Unicode code-point-ordered keys, no whitespace, IEEE 754 double-precision number encoding. TRACE uses JCS to canonicalize the record before computing the Ed25519 signature.
+
+---
+
+**RIM — Reference Integrity Manifest**
+A signed document describing the expected firmware and software measurements for a TEE environment. During Level 1 appraisal, the verifier compares the TEE's runtime measurements against the RIM. The `runtime.rim_uri` field optionally points to a RIM.
+
+---
+
+**RATS — Remote Attestation Procedures**
+The IETF working group and architecture (RFC 9334) that defines the roles and flows for remote attestation: Attester (the hardware), Verifier (checks evidence against RIM), Relying Party (consumes the resulting attestation result). TRACE Level 1 and 2 follow the RATS architecture.
+
+---
+
+**SCITT — Supply Chain Integrity, Transparency, and Trust**
+An IETF draft standard for append-only transparency logs of software and attestation artifacts. TRACE Level 2 records include a SCITT receipt URI in the `transparency` field, anchoring the record to a public or shared log.
+
+---
+
+**SPIFFE / SPIRE**
+SPIFFE (Secure Production Identity Framework For Everyone) defines URI-based workload identities of the form `spiffe://<trust-domain>/<workload-path>`. TRACE requires the `subject` field to be a SPIFFE URI or a DID. SPIRE is the reference implementation.
+
+---
+
+**Trust Level**
+A numeric value (0, 1, or 2) that summarizes the strength of the guarantees carried by a trust record. See [Trust Levels](trust-levels.md) for the full definition of each level.
+
+---
+
+**Trust Record**
+A signed JSON document emitted by an AI agent at the end of a governed session. It asserts the agent's identity, model, policy, data class, tool invocations, and (at Level 1+) hardware attestation state. Defined in full in the [TRACE Specification](../spec/trace-v0.1.md).
+
+---
+
+**Transparency**
+In the TRACE context, transparency means that a trust record has been submitted to an append-only log (SCITT) and can be independently audited by any party with access to the log. The `transparency` field holds the receipt URI. Required at Level 2.

agentrust_trace-0.3.0/docs/index.md

@@ -0,0 +1,73 @@
+# TRACE
+
+**Trust Runtime Attestation and Compliance Evidence** — an open specification for hardware-attested AI agent governance records.
+
+TRACE defines the format, anchoring protocol, and verification rules for cryptographically provable evidence that an AI agent ran under a specific policy, in a verified hardware environment, on classified data, invoking identified tools — bound into a single signed artifact rooted in silicon attestation.
+
+---
+
+<div class="grid cards" markdown>
+
+-   :material-rocket-launch: **Get Started**
+
+    Install the library, sign your first Trust Record, and verify it end-to-end in minutes.
+
+    [Quickstart →](quickstart.md)
+
+-   :material-file-document: **Specification**
+
+    The normative TRACE v0.1 specification — envelope format, claim types, signing rules, and verification algorithm.
+
+    [Read the spec →](../spec/trace-v0.1.md)
+
+-   :material-connection: **Integration**
+
+    Connect TRACE to AGT and cMCP for end-to-end agent governance pipelines.
+
+    [Integration guides →](integration/agt.md)
+
+-   :material-check-all: **Conformance Tests**
+
+    197 tests across 7 modules. Verify your implementation against the spec.
+
+    [Test suite →](https://tests.agentrust-io.com){ target=_blank }
+
+</div>
+
+## What a Trust Record proves
+
+A TRACE Trust Record answers — in a form any third party can verify without trusting the operator:
+
+| Question | TRACE claim |
+|---|---|
+| What model ran? | `model.model_id` + `model.weights_digest` |
+| Where did it run? | `runtime.platform` + `runtime.measurement` |
+| Under which policy? | `policy.bundle_hash` + `policy.enforcement_mode` |
+| What data did it touch? | `data_class` |
+| Which tools were called? | `tool_transcript.hash` + `tool_transcript.call_count` |
+| Is the record independently anchored? | `anchoring.receipt_uri` (SCITT) |
+
+## Standards alignment
+
+TRACE is built on open IETF/IRTF standards and designed for CoSAI WS4 interoperability:
+
+- **RFC 9711** — CBOR Web Token (CWT) / EAT claim envelope
+- **RFC 9334** — RATS architecture (attester, verifier, relying-party roles)
+- **SCITT draft-22** — transparency ledger anchoring
+- **CoSAI WS4** — AI agent digital lifecycle controls (contributed spec language)
+
+## Quick reference
+
+```bash
+pip install agentrust-trace
+```
+
+```python
+from agentrust_trace import TrustRecord
+
+record = TrustRecord.sign(claims, signing_key)
+receipt = record.anchor()            # SCITT ledger
+record.verify(verifying_key)         # raises on invalid
+```
+
+[Full API reference →](schema.md) · [Changelog →](../CHANGELOG.md) · [GitHub →](https://github.com/agentrust-io/trace-spec){ target=_blank }

agentrust_trace-0.3.0/docs/integration/agt.md

@@ -0,0 +1,139 @@
+# Integration: AGT
+
+[AGT (Agent Governance Toolkit)](https://github.com/microsoft/agent-governance-toolkit) is the most widely adopted agent governance framework (4,100+ stars, 100+ contributors). It provides Cedar policy enforcement, SPIFFE/SVID identity, and Merkle-chained audit logs for any agent framework.
+
+AGT emits TRACE v0.1 Trust Records via `TRACEAuditSink` — see [ADR 0032](https://github.com/microsoft/agent-governance-toolkit/blob/main/docs/adr/0032-agt-emits-trace-v01-trust-records.md) for the full design.
+
+## What AGT emits
+
+AGT emits **Level 0 (software-only)** TRACE records. The record is signed with an Ed25519 key held in the operator's key store — not a TEE-bound key. For Level 2 hardware-rooted records, deploy AGT inside [cMCP](cmcp.md) or another TEE runtime.
+
+| TRACE field | Source in AGT |
+|---|---|
+| `subject` | `agent_did` passed to `govern()` |
+| `policy.bundle_hash` | SHA-256 of the Cedar policy bundle bytes at session start |
+| `policy.enforcement_mode` | Always `enforce` (Phase 1) |
+| `tool_transcript.hash` | SHA-256 of the canonical JSON of the Merkle `AuditEntry` list |
+| `tool_transcript.call_count` | Count of `AuditEntry` items in the session |
+| `runtime.platform` | `software-only` |
+| `runtime.measurement` | SHA-256 of the Merkle chain tip |
+| `appraisal.status` | `affirming` (Phase 1) |
+| `model`, `data_class`, `build_provenance` | Injected from `TraceConfig` |
+
+## Install
+
+```bash
+pip install agentmesh agentrust-trace
+```
+
+## Quick start: TraceAGTAdapter
+
+`TraceAGTAdapter` eliminates the ~50-line field-mapping boilerplate. Install:
+
+```bash
+pip install agentrust-trace
+```
+
+One-liner upgrade path for any AGT-governed session:
+
+```python
+from agentrust_trace.adapters import TraceAGTAdapter, AGTSessionResult
+from agentrust_trace import sign_record, generate_key
+
+adapter = TraceAGTAdapter(
+    model_provider="anthropic",
+    model_id="claude-sonnet-4-6",
+    model_version="20251001",
+    build_provenance_digest="sha256:e5f6a7b8...",
+    transparency="https://registry.agentrust.io/claim/...",
+)
+
+session = AGTSessionResult(
+    agent_did="spiffe://trust.example.org/agent/my-agent",
+    policy_bundle_bytes=Path("policy.cedar").read_bytes(),
+    audit_entries=govern_fn.get_audit_entries(),
+    merkle_chain_tip=govern_fn.chain_tip,
+)
+
+record = adapter.build_trust_record(session)
+signed = sign_record(record, generate_key())  # or load_signing_key() for production
+```
+
+→ Full walkthrough: [TraceAGTAdapter tutorial](../tutorials/agt-adapter.md)
+
+## Manual wiring (legacy)
+
+The following is the raw field-mapping approach — kept for reference. Prefer `TraceAGTAdapter` for new integrations.
+
+```python
+from agentmesh.governance import govern, GovernanceConfig
+from agentmesh.governance.trace_sink import TraceConfig
+
+trace_config = TraceConfig(
+    output_path="session.trace.json",
+    model_provider="anthropic",
+    model_id="claude-sonnet-4-6",
+    model_version="20251001",
+    data_class="confidential",
+    build_provenance_slsa_level=2,
+    build_provenance_digest="sha256:e5f6a7b8...",
+)
+
+config = GovernanceConfig(
+    policy_path="policy.cedar",
+    trace=trace_config,
+)
+
+governed_fn = govern(
+    my_tool,
+    agent_did="spiffe://trust.example.org/agent/my-agent",
+    config=config,
+)
+
+result = governed_fn(input)
+path = governed_fn.close_session()
+print(f"Trust Record written to: {path}")
+```
+
+## Key management
+
+Key material is managed entirely by `agentrust_trace.load_signing_key()`. AGT does not hold keys directly.
+
+```bash
+# Set the signing key path via environment variable
+export AGENTRUST_TRACE_KEY_PATH=/run/secrets/trace-signing-key.pem
+```
+
+For production, store the key in a secrets manager (AWS Secrets Manager, HashiCorp Vault, Kubernetes Secret) and inject via environment variable or volume mount.
+
+## Verifying the emitted record
+
+```bash
+agentrust-trace verify session.trace.json --pubkey trace-key.pem.pub
+```
+
+## Upgrading to Level 2 (hardware-rooted)
+
+Deploy your AGT-governed agent inside cMCP. The cMCP runtime:
+
+1. Measures the Cedar policy bundle into the TEE before any code runs
+2. Generates a TEE-bound key for the TRACE record
+3. Emits a Level 2 record that supersedes AGT's Level 0 record for the same session
+
+The two records are linked by a shared `subject` and `tool_transcript.hash` — AGT's record and cMCP's record are mutually verifiable.
+
+→ [Integration guide: cMCP](cmcp.md)
+
+## Framework support
+
+AGT instruments any Python callable via `govern()`. Confirmed compatible frameworks:
+
+| Framework | Notes |
+|---|---|
+| LangGraph | Wrap tool nodes with `govern()` |
+| CrewAI | Wrap task tools |
+| AutoGen | Wrap function tools |
+| Mastra | Via adapter contract |
+| Raw Python | Direct function wrapping |
+
+For the full integration list, see the [AGT integrations repo](https://github.com/agentrust-io/integrations).