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

agentrust_trace-0.4.0/.github/CODEOWNERS

@@ -0,0 +1,5 @@
+# Default owners for all files
+* @agentrust-io/maintainers
+
+# CI/CD workflow changes
+.github/workflows/ @agentrust-io/maintainers

agentrust_trace-0.4.0/.github/dependabot.yml

@@ -0,0 +1,19 @@
+version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    open-pull-requests-limit: 5
+    ignore:
+      - dependency-name: "*"
+        update-types:
+          - "version-update:semver-major"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    open-pull-requests-limit: 5

{agentrust_trace-0.3.0 → agentrust_trace-0.4.0}/.github/workflows/ci.yml

@@ -16,9 +16,9 @@ jobs:
         python-version: ["3.11", "3.12"]
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
 
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v6
         with:
           python-version: ${{ matrix.python-version }}
 

agentrust_trace-0.4.0/.github/workflows/codeql.yml

@@ -0,0 +1,43 @@
+name: CodeQL
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+  schedule:
+    - cron: '15 3 * * 0'
+
+permissions:
+  actions: read
+  contents: read
+  security-events: write
+
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
+
+jobs:
+  analyze:
+    name: Analyze (python)
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v7
+
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v4
+        with:
+          languages: python
+          queries: +security-extended
+
+      - name: Autobuild
+        uses: github/codeql-action/autobuild@v4
+
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@v4
+        continue-on-error: true
+        with:
+          category: /language:python

{agentrust_trace-0.3.0 → agentrust_trace-0.4.0}/.github/workflows/contributor-check.yml

@@ -27,7 +27,7 @@ jobs:
       github.actor != 'imran-siddique'
     steps:
       - name: Checkout org action
-        uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
         with:
           repository: agentrust-io/.github
           ref: main

{agentrust_trace-0.3.0 → agentrust_trace-0.4.0}/.github/workflows/docs.yml

@@ -6,6 +6,8 @@ on:
     paths:
       - "docs/**"
       - "spec/**"
+      - "overrides/**"
+      - "robots.txt"
       - "mkdocs.yml"
       - "requirements-docs.txt"
       - "README.md"
@@ -30,7 +32,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
@@ -58,7 +60,7 @@ jobs:
           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
+          for fname in README.md CHANGELOG.md CONTRIBUTING.md GOVERNANCE.md ROADMAP.md LIMITATIONS.md CNAME robots.txt; do
             if [ -f "$fname" ]; then cp "$fname" "$BUILD/$fname"; fi
           done
 

{agentrust_trace-0.3.0 → agentrust_trace-0.4.0}/.github/workflows/publish.yml

@@ -16,9 +16,9 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
 
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v6
         with:
           python-version: "3.11"
 
@@ -27,7 +27,7 @@ jobs:
           pip install hatchling
           python -m hatchling build
 
-      - uses: actions/upload-artifact@v4
+      - uses: actions/upload-artifact@v7
         with:
           name: dist
           path: dist/
@@ -37,9 +37,9 @@ jobs:
     runs-on: ubuntu-latest
     environment: pypi
     steps:
-      - uses: actions/download-artifact@v4
+      - uses: actions/download-artifact@v8
         with:
           name: dist
           path: dist/
 
-      - uses: pypa/gh-action-pypi-publish@release/v1
+      - uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0

{agentrust_trace-0.3.0 → agentrust_trace-0.4.0}/.github/workflows/require-maintainer-approval.yml

@@ -22,7 +22,7 @@ jobs:
     if: github.event.pull_request.base.ref == 'main'
     steps:
       - name: Check for maintainer approval
-        uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7.0.1
+        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
         with:
           script: |
             const MAINTAINERS = ['imran-siddique'];

{agentrust_trace-0.3.0 → agentrust_trace-0.4.0}/.github/workflows/sbom.yml

@@ -17,14 +17,14 @@ jobs:
   sbom:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
       - name: Generate SBOM
         uses: anchore/sbom-action@v0
         with:
           format: spdx-json
           output-file: sbom.spdx.json
       - name: Upload SBOM artifact
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: sbom
           path: sbom.spdx.json

agentrust_trace-0.4.0/.github/workflows/scorecard.yml

@@ -0,0 +1,40 @@
+name: OpenSSF Scorecard
+
+on:
+  branch_protection_rule:
+  schedule:
+    - cron: '30 4 * * 1'
+  push:
+    branches:
+      - main
+
+permissions: read-all
+
+jobs:
+  scorecard:
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      id-token: write
+      contents: read
+      actions: read
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+          fetch-depth: 0
+
+      - name: Run Scorecard
+        uses: ossf/scorecard-action@4eaacf0543bb3f2c246792bd56e8cdeffafb205a # v2.4.3
+        with:
+          results_file: scorecard-results.sarif
+          results_format: sarif
+          # publish_results requires a public repo; flip to true after the
+          # 2026-06-23 public launch.
+          publish_results: false
+
+      - name: Upload SARIF
+        uses: github/codeql-action/upload-sarif@v4
+        with:
+          sarif_file: scorecard-results.sarif

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

@@ -1,76 +1,88 @@
-# Changelog
-
-All notable changes to the TRACE specification will be documented here.
-
-Format: [Semantic Versioning](https://semver.org/). Spec versions follow `MAJOR.MINOR.PATCH`:
-- **MAJOR**: breaking changes to wire format or required Trust Record fields
-- **MINOR**: new optional fields, new platform profiles, new conformance levels
-- **PATCH**: editorial fixes, clarifications, non-normative additions
-
----
-
-## [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.
-
-### Specification
-
-- Trust Record logical schema (§3.1): `subject`, `model`, `runtime`, `policy`, `data_class`, `tool_transcript`, `build_provenance`, `appraisal`, `transparency`, `cnf`
-- Wire format (§3.2): EAT/JWT and CBOR-COSE envelopes; profile URI `tag:agentrust.io,2026:trace-v0.1`
-- Signing and key management (§3.2.1): ES256/ES384/EdDSA; four-layer key hierarchy; hash agility; revocation
-- Verification protocol (§3.3): five-step offline verification, no issuer callback
-- Standards composition (§4): RATS/EAT, SLSA, SPIFFE, SCITT, EAR, MCP, A2A, AIBOM, C2PA
-- Hardware roots (§4.2): NVIDIA H100/Blackwell, Intel TDX, AMD SEV-SNP, Azure MAA, GCP Confidential Space, AWS Nitro
-- Reference implementation (§5): cMCP Phase 1–3 roadmap
-
-### Schema
-
-- `schema/trace-claim.json`: JSON Schema (draft/2020-12) for Trust Record validation
-
-### Examples
-
-- `examples/amd-sev-snp.json`: AMD SEV-SNP Trust Record
-- `examples/intel-tdx.json`: Intel TDX Trust Record
-- `examples/nvidia-h100.json`: NVIDIA H100 Confidential Computing Trust Record
-
-### Open questions
-
-Seven open questions requiring community input before v0.2 are documented in §7 of the spec.
-
----
-
-## [0.2.0] — TBD
-
-### Specification
-
-- Extend `subject` field to accept DID URIs (any `did:` method) in addition to SPIFFE SVIDs.
-  Previously `^spiffe://` only; now `^(spiffe://|did:)`. Additive, backward-compatible.
-  DID-native runtimes (e.g. AGT `did:mesh:` identities) no longer require a parallel SPIFFE identity.
-  Closes: microsoft/agent-governance-toolkit ADR-0032, agentrust-io/trace-spec#35.
-
-### Schema
-
-- `schema/trace-claim.json`: `subject` pattern updated to `^(spiffe://|did:)`, description updated.
-
-### Reference Implementation
-
-- `TrustRecord.subject` pattern updated to `r"^(spiffe://|did:)"`.
-
----
-
-## Upcoming
-
-See [ROADMAP.md](ROADMAP.md) for planned changes in v0.2 and v1.0.
+# Changelog
+
+All notable changes to the TRACE specification will be documented here.
+
+Format: [Semantic Versioning](https://semver.org/). Spec versions follow `MAJOR.MINOR.PATCH`:
+- **MAJOR**: breaking changes to wire format or required Trust Record fields
+- **MINOR**: new optional fields, new platform profiles, new conformance levels
+- **PATCH**: editorial fixes, clarifications, non-normative additions
+
+---
+
+## [Unreleased]
+
+## [0.4.0]
+
+### Added
+
+- **`azure-cvm-sev-snp` platform** — Azure confidential VMs run AMD SEV-SNP behind a Hyper-V paravisor: the SNP report is read from the vTPM (the guest does not control `REPORT_DATA`), so the runtime binding rides a vTPM AK-signed quote rather than the SNP `report_data`. Given its own `runtime.platform` value (distinct from `amd-sev-snp`) so a consumer keying on `runtime.platform` knows the root of trust is vTPM-rooted, not direct-silicon. Added to the `RuntimeInfo` model and the JSON schema enum. Hardware-validated on a live Azure SEV-SNP VM via cMCP.
+
+- `delegation` (optional object): the A2A profile delegation-link block, carrying `parent_record_hash` (digest of the parent hop's Trust Record) and `credential_id` (the delegation credential this hop acted under). A chain of records linked this way forms an offline-verifiable delegation DAG. Backward-compatible: existing records without `delegation` remain valid. This is a MINOR (additive) change and the foundation of the forthcoming A2A profile; A2A is now stable at v1.x, clearing the prior blocker.
+
+---
+
+## [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.
+
+### Specification
+
+- Trust Record logical schema (§3.1): `subject`, `model`, `runtime`, `policy`, `data_class`, `tool_transcript`, `build_provenance`, `appraisal`, `transparency`, `cnf`
+- Wire format (§3.2): EAT/JWT and CBOR-COSE envelopes; profile URI `tag:agentrust.io,2026:trace-v0.1`
+- Signing and key management (§3.2.1): ES256/ES384/EdDSA; four-layer key hierarchy; hash agility; revocation
+- Verification protocol (§3.3): five-step offline verification, no issuer callback
+- Standards composition (§4): RATS/EAT, SLSA, SPIFFE, SCITT, EAR, MCP, A2A, AIBOM, C2PA
+- Hardware roots (§4.2): NVIDIA H100/Blackwell, Intel TDX, AMD SEV-SNP, Azure MAA, GCP Confidential Space, AWS Nitro
+- Reference implementation (§5): cMCP Phase 1–3 roadmap
+
+### Schema
+
+- `schema/trace-claim.json`: JSON Schema (draft/2020-12) for Trust Record validation
+
+### Examples
+
+- `examples/amd-sev-snp.json`: AMD SEV-SNP Trust Record
+- `examples/intel-tdx.json`: Intel TDX Trust Record
+- `examples/nvidia-h100.json`: NVIDIA H100 Confidential Computing Trust Record
+
+### Open questions
+
+Seven open questions requiring community input before v0.2 are documented in §7 of the spec.
+
+---
+
+## [0.2.0] — TBD
+
+### Specification
+
+- Extend `subject` field to accept DID URIs (any `did:` method) in addition to SPIFFE SVIDs.
+  Previously `^spiffe://` only; now `^(spiffe://|did:)`. Additive, backward-compatible.
+  DID-native runtimes (e.g. AGT `did:mesh:` identities) no longer require a parallel SPIFFE identity.
+  Closes: microsoft/agent-governance-toolkit ADR-0032, agentrust-io/trace-spec#35.
+
+### Schema
+
+- `schema/trace-claim.json`: `subject` pattern updated to `^(spiffe://|did:)`, description updated.
+
+### Reference Implementation
+
+- `TrustRecord.subject` pattern updated to `r"^(spiffe://|did:)"`.
+
+---
+
+## Upcoming
+
+See [ROADMAP.md](ROADMAP.md) for planned changes in v0.2 and v1.0.

{agentrust_trace-0.3.0 → agentrust_trace-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentrust-trace
-Version: 0.3.0
+Version: 0.4.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
@@ -101,6 +101,89 @@ signed = sign_record(record, key=signing_key)
 
 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.
 
+## Frequently asked questions
+
+### What is TRACE?
+
+TRACE (Trust Runtime Attestation and Compliance Evidence) is an open specification for hardware-attested AI agent governance records. It defines the record format, the anchoring protocol, and the verification rules for cryptographic evidence that an AI agent ran under a specific policy, in a verified hardware environment, on a given data class, invoking identified tools.
+
+### What does a TRACE Trust Record prove?
+
+A single signed Trust Record answers, in a form any third party can verify without trusting the operator: what model ran, where it ran, under which policy, what data class it touched, which tools were called, and whether the record is independently anchored to a SCITT transparency ledger.
+
+### What standards is TRACE built on?
+
+TRACE builds on open IETF and IRTF standards: RFC 9711 (CBOR Web Token / EAT) for the claim envelope, RFC 9334 (RATS) for the attester, verifier, and relying-party roles, and the SCITT draft for transparency-ledger anchoring. It is designed for CoSAI WS4 interoperability.
+
+### How do I create and verify a Trust Record?
+
+Install the Python library with `pip install agentrust-trace`, sign a record with `TrustRecord.sign(claims, signing_key)`, anchor it to a SCITT ledger with `record.anchor()`, and check it with `record.verify(verifying_key)`.
+
+### How does TRACE relate to AGT and cMCP?
+
+TRACE is the evidence format. AGT and cMCP produce and consume Trust Records, so you can connect them into an end-to-end agent governance pipeline. See the integration guides for details.
+
+### What is the current status of TRACE?
+
+The current specification is TRACE v0.1, published with a conformance test suite. See the Limitations page for scope boundaries before relying on it in production.
+
+<script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [
+    {
+      "@type": "Question",
+      "name": "What is TRACE?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE (Trust Runtime Attestation and Compliance Evidence) is an open specification for hardware-attested AI agent governance records. It defines the record format, the anchoring protocol, and the verification rules for cryptographic evidence that an AI agent ran under a specific policy, in a verified hardware environment, on a given data class, invoking identified tools."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What does a TRACE Trust Record prove?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "A single signed Trust Record answers, in a form any third party can verify without trusting the operator: what model ran, where it ran, under which policy, what data class it touched, which tools were called, and whether the record is independently anchored to a SCITT transparency ledger."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What standards is TRACE built on?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE builds on open IETF and IRTF standards: RFC 9711 (CBOR Web Token / EAT) for the claim envelope, RFC 9334 (RATS) for the attester, verifier, and relying-party roles, and the SCITT draft for transparency-ledger anchoring. It is designed for CoSAI WS4 interoperability."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "How do I create and verify a Trust Record?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "Install the Python library with pip install agentrust-trace, sign a record with TrustRecord.sign(claims, signing_key), anchor it to a SCITT ledger with record.anchor(), and check it with record.verify(verifying_key)."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "How does TRACE relate to AGT and cMCP?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE is the evidence format. AGT and cMCP produce and consume Trust Records, so you can connect them into an end-to-end agent governance pipeline. See the integration guides for details."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What is the current status of TRACE?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "The current specification is TRACE v0.1, published with a conformance test suite. See the Limitations page for scope boundaries before relying on it in production."
+      }
+    }
+  ]
+}
+</script>
+
 ## 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.4.0/PRIVACY.md

@@ -0,0 +1,9 @@
+# Privacy
+
+agentrust-trace (the TRACE SDK) collects and transmits no personal data.
+
+It runs locally as a Python library. It processes only the inputs you give it, entirely on your machine, and sends no telemetry, analytics, or usage data to agentrust-io, OPAQUE, or any third party. There is no account, login, or tracking, and no cookies or background network calls.
+
+Any network activity is user-initiated: anchoring a record to a SCITT transparency service happens only when you explicitly call it, to the endpoint you configure.
+
+Uninstalling removes it completely. Questions or corrections: https://github.com/agentrust-io/trace-spec/issues

agentrust_trace-0.4.0/README.md

@@ -0,0 +1,155 @@
+<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.
+
+## Frequently asked questions
+
+### What is TRACE?
+
+TRACE (Trust Runtime Attestation and Compliance Evidence) is an open specification for hardware-attested AI agent governance records. It defines the record format, the anchoring protocol, and the verification rules for cryptographic evidence that an AI agent ran under a specific policy, in a verified hardware environment, on a given data class, invoking identified tools.
+
+### What does a TRACE Trust Record prove?
+
+A single signed Trust Record answers, in a form any third party can verify without trusting the operator: what model ran, where it ran, under which policy, what data class it touched, which tools were called, and whether the record is independently anchored to a SCITT transparency ledger.
+
+### What standards is TRACE built on?
+
+TRACE builds on open IETF and IRTF standards: RFC 9711 (CBOR Web Token / EAT) for the claim envelope, RFC 9334 (RATS) for the attester, verifier, and relying-party roles, and the SCITT draft for transparency-ledger anchoring. It is designed for CoSAI WS4 interoperability.
+
+### How do I create and verify a Trust Record?
+
+Install the Python library with `pip install agentrust-trace`, sign a record with `TrustRecord.sign(claims, signing_key)`, anchor it to a SCITT ledger with `record.anchor()`, and check it with `record.verify(verifying_key)`.
+
+### How does TRACE relate to AGT and cMCP?
+
+TRACE is the evidence format. AGT and cMCP produce and consume Trust Records, so you can connect them into an end-to-end agent governance pipeline. See the integration guides for details.
+
+### What is the current status of TRACE?
+
+The current specification is TRACE v0.1, published with a conformance test suite. See the Limitations page for scope boundaries before relying on it in production.
+
+<script type="application/ld+json">
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [
+    {
+      "@type": "Question",
+      "name": "What is TRACE?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE (Trust Runtime Attestation and Compliance Evidence) is an open specification for hardware-attested AI agent governance records. It defines the record format, the anchoring protocol, and the verification rules for cryptographic evidence that an AI agent ran under a specific policy, in a verified hardware environment, on a given data class, invoking identified tools."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What does a TRACE Trust Record prove?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "A single signed Trust Record answers, in a form any third party can verify without trusting the operator: what model ran, where it ran, under which policy, what data class it touched, which tools were called, and whether the record is independently anchored to a SCITT transparency ledger."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What standards is TRACE built on?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE builds on open IETF and IRTF standards: RFC 9711 (CBOR Web Token / EAT) for the claim envelope, RFC 9334 (RATS) for the attester, verifier, and relying-party roles, and the SCITT draft for transparency-ledger anchoring. It is designed for CoSAI WS4 interoperability."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "How do I create and verify a Trust Record?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "Install the Python library with pip install agentrust-trace, sign a record with TrustRecord.sign(claims, signing_key), anchor it to a SCITT ledger with record.anchor(), and check it with record.verify(verifying_key)."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "How does TRACE relate to AGT and cMCP?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "TRACE is the evidence format. AGT and cMCP produce and consume Trust Records, so you can connect them into an end-to-end agent governance pipeline. See the integration guides for details."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "What is the current status of TRACE?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "The current specification is TRACE v0.1, published with a conformance test suite. See the Limitations page for scope boundaries before relying on it in production."
+      }
+    }
+  ]
+}
+</script>
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) and [GOVERNANCE.md](GOVERNANCE.md). All contributors must agree to the [ANTITRUST.md](ANTITRUST.md) policy.