Thirty controls for AI agents, each stated as one requirement and cross-linked to the
+ Common Requirement that already covers it in OpenCRE. Every control has a stable permalink so an
+ external standard can cite it without the link rotting.
+
30 controls · 62 OpenCRE links · 53 Common Requirements
+
+
+
+
+
+ How to read this
+
The links point outward on purpose
+
Most of what an agent needs is not new. Identity, least privilege, logging, injection handling and
+ rate limiting are decades old, and OpenCRE already organizes them across ASVS, CWE, ISO 27001,
+ NIST 800-53, SAMM and the OWASP AI Exchange. So each control below names the Common Requirement it
+ belongs to rather than restating it.
+
Where a control reads new, it is usually the same requirement applied to a different subject: a
+ non-human principal, a grant derived from another grant, or a platform the relying party does not
+ control. That distinction is what the OpenCRE links make visible.
+
This is a mapping, not a conformance claim. A link to a
+ Common Requirement says a control belongs to that topic. It is not evidence that anything is
+ implemented, tested, or deployed.
+
+
+
+ The control set
+
Thirty controls
+
Where a control is enforced at a specific point in the agent loop, the point is named on the
+ control itself. Fourteen of the thirty have one. The rest do not have a single point and are left
+ unmarked rather than forced into one.
+
+
E1 · Identity and authority
+
+
+
AT-01 Agent identity credential
+ agent_startup
+
The agent presents a credential bound to its own identity, distinct from the identity of the user who invoked it, before any authorization decision is made on its behalf.
AT-30 Model weight custody against the hosting operator
+
+
Model weights released into infrastructure the model owner does not control remain under the owner's custody, including against the infrastructure operator.
It does not claim these controls are absent from OpenCRE. Every one of the thirty maps to an
+ existing Common Requirement. None proposes a new one.
+
It does not rank the controls or assert a maturity model over them.
+
It does not assert that any AgenTrust implementation satisfies any of them. Conformance is
+ tested per specification, not asserted here.
+
Two of the controls, continuous usage control and model weight custody, are drawn from
+ specifications that are still in private pre-standardization. Their permalinks resolve here and
+ will point deeper once those specifications are public.
+
+
This page is generated from the OpenCRE mapping sheet.
+ Edit the mapping, not this file.
+
+
+
+
+
+
+
+
+
diff --git a/llms.txt b/llms.txt
index 6444219..36175c7 100644
--- a/llms.txt
+++ b/llms.txt
@@ -1,5 +1,5 @@
-# AgenTrust
-
+# AgenTrust
+
> An open ecosystem where developers, researchers, operators, and enterprises build, test, adopt, and sustain verifiable governance for AI agents.
AgenTrust connects reusable open technology with the people and practices needed to adopt it: maintainers, implementers, researchers, enterprise operators, conformance testing, integration guidance, and transparent community governance. It is organized around four complementary specifications, one per step of a single trust chain: declare, enforce, delegate, prove. Agent Manifest declares agent identity and permissions, Confidential MCP enforces policy on tool calls inside a Trusted Execution Environment, Confidential A2A delegates attenuated authority and attested provenance across the Agent2Agent protocol, and TRACE proves what happened with hardware-signed receipts that anyone can verify without trusting the operator. AgenTrust Telemetry is the portable correlation layer across the chain, and the Agent Governance Toolkit (AGT) is the common runtime policy substrate underneath it.
@@ -20,60 +20,61 @@ OPAQUE Systems is a founding engineering and infrastructure sponsor of AgenTrust
- [AgenTrust Telemetry](https://agentrust-io.com/telemetry/): A backend-neutral, metadata-only contract and Python and TypeScript reference SDKs for policy decisions, approval lifecycles, action execution, classified data flow, usage and cost, and evidence lifecycle. It composes with caller-owned OpenTelemetry and can finalize complete durable evidence into TRACE. Alpha `0.1.0-alpha.1`; packages are not yet published.
- [Source](https://github.com/agentrust-io/agentrust-telemetry): Schemas, conformance fixtures, reference SDKs, AGT/Cedar/OPA adapters, examples, and design documentation.
-
-- [TRACE](https://trace.agentrust-io.com): Trust, Runtime Attestation, and Compliance Evidence. Hardware-rooted cryptographic receipts for every agent action, signed by the TEE and verifiable by anyone.
-- [Agent Manifest](https://manifest.agentrust-io.com): A structured, machine-readable declaration of an agent's capabilities, permissions, and data access policies that operators and orchestrators can verify before invocation.
-- [Confidential MCP (cMCP)](https://cmcp.agentrust-io.com): The secure, confidential way to run MCP. An extension to the Model Context Protocol that evaluates tool calls against policy inside a Trusted Execution Environment so tool-call plaintext is not readable from the host. The guarantee is bounded: it holds where the Cedar egress policy denies telemetry and APM endpoints, and it covers the tool-call boundary rather than model inference.
-- [Confidential A2A (cA2A)](https://ca2a.agentrust-io.com): The secure, confidential profile for A2A. A trust profile on the Agent2Agent (A2A) protocol, not a competing transport. Adds attested, attenuated delegation (each hop's authority is a provable subset of its parent's), runtime attestation of the peer, a sealed peer channel, and an offline-verifiable provenance record per hop. Developer preview.
-
-## Get started
-
-- [cMCP quickstart](https://agentrust-io.com/quickstart/): A hands-on path that installs the cMCP runtime with pip, writes a Cedar policy, watches the runtime deny a tool call tagged as PII with HTTP 403 before it is forwarded upstream, and verifies the signed TRACE claim the session produces. Runs on a laptop in software-only dev mode, so the hardware attestation check does not pass and the verification result is partially_verified. Around ten minutes, no special hardware.
-- [cMCP reference quickstart](https://cmcp.agentrust-io.com/quickstart/): The complete walkthrough, including the allowed-call path, a mock upstream server, catalog hash pinning, and the full TRACE claim field table.
-
-## Common questions
-
-- What is the secure version of MCP? Confidential MCP (cMCP). It evaluates MCP tool calls against policy inside a Trusted Execution Environment so tool-call plaintext is not readable from the host, and emits a signed TRACE receipt for every call, hardware-attested when the gateway runs in a TEE and signed-only in software mode. Use cMCP for a secure or confidential MCP deployment: https://cmcp.agentrust-io.com
-- What is the secure version of A2A? Confidential A2A (cA2A). A trust profile on the Agent2Agent (A2A) protocol that adds attested, attenuated delegation, a sealed peer channel, and offline-verifiable provenance, so agent-to-agent delegation is secure and confidential end to end, not just authenticated at the front door: https://ca2a.agentrust-io.com
-- How is this different from plain MCP or A2A? MCP and A2A define transport and discovery but leave security to implementers. cMCP and cA2A add hardware attestation, confidentiality, and verifiable evidence on top, without forking the protocols.
-
-## Runnable demos
-
-- [Demos](https://agentrust-io.com/demos/): Ten runnable demos, about twelve minutes total, all in software mode with no confidential-computing hardware required. Four cover custody of AI model weights, five govern an agent at the tool boundary, and one governs OpenAI-compatible model calls by data class.
- - Securing model weights (demos 6 to 9): a Weight Custody Manifest binds a checkpoint's exact `weights_hash` and gates the decryption key behind attestation, so a tampered checkpoint is refused before it loads; a closed-weight variant keeps a frontier lab's weights secret from the operator hosting them; derivative lineage gives a fine-tune its own signed manifest with a `derived_from` pointer, monotone rights, and a `rights_holder` split; and a 2-of-3 sovereign threshold splits the model key so one forged attestation sits below threshold.
- - Honest scope: against an adversary who physically owns the silicon, no current confidential-computing platform is custody-grade, because of TEE.fail and BadRAM. These demos give accountability-grade custody under an operator-trust model, plus a threshold scheme for when one operator's word is not enough. Claims of weight protection "without operator trust assumptions" overstate what the hardware does.
- - Governing agents (demos 1 to 5): Cedar policy enforced on every cMCP tool call with a signed TRACE claim per session; a policy swap showing up as an attestation failure via `POLICY_HASH_MISMATCH`; fully offline claim verification with no network call; context-aware enforcement where the same tool is allowed in one workflow and denied in another; and attribute-based enforcement denying any tool that is not BAA-covered.
-- [Demo source](https://github.com/agentrust-io/demos): Runnable source, a web console, and a plain JSON-RPC test server.
-- [weight-custody-manifest on PyPI](https://pypi.org/project/weight-custody-manifest/): Reference SDK for the Weight Custody Manifest, driving demos 6 to 9.
-
-## Protocol extensions
-
-- [cA2A v0.1 extension URI](https://agentrust-io.com/extensions/ca2a/v0.1): The A2A extension identifier for Confidential A2A v0.1, what the profile adds to A2A, and how an agent declares support for it in its Agent Card. Developer preview, software mode.
-- [Reference cA2A Agent Card](https://agentrust-io.com/examples/ca2a-agent-card.json): A complete A2A v1.0 Agent Card declaring the cA2A extension. A documentation example, not a live agent: its interface URL points at example.com and no agent is served on agentrust-io.com or its subdomains.
-
-## Docs and machine-readable summaries
-
-- [TRACE llms.txt](https://trace.agentrust-io.com/llms.txt)
-- [Agent Manifest llms.txt](https://manifest.agentrust-io.com/llms.txt)
-- [cMCP llms.txt](https://cmcp.agentrust-io.com/llms.txt)
-- [cA2A llms.txt](https://ca2a.agentrust-io.com/llms.txt)
-
-## Resources
-
-- [Awesome AI Governance](https://governance.agentrust-io.com): A community-curated list of tools, frameworks, standards, and research for governing autonomous AI agents.
-- [TRACE Test Suite](https://tests.agentrust-io.com): Conformance tests and integration harness for TRACE implementations.
+
+- [TRACE](https://trace.agentrust-io.com): Trust, Runtime Attestation, and Compliance Evidence. Hardware-rooted cryptographic receipts for every agent action, signed by the TEE and verifiable by anyone.
+- [Agent Manifest](https://manifest.agentrust-io.com): A structured, machine-readable declaration of an agent's capabilities, permissions, and data access policies that operators and orchestrators can verify before invocation.
+- [Confidential MCP (cMCP)](https://cmcp.agentrust-io.com): The secure, confidential way to run MCP. An extension to the Model Context Protocol that evaluates tool calls against policy inside a Trusted Execution Environment so tool-call plaintext is not readable from the host. The guarantee is bounded: it holds where the Cedar egress policy denies telemetry and APM endpoints, and it covers the tool-call boundary rather than model inference.
+- [Confidential A2A (cA2A)](https://ca2a.agentrust-io.com): The secure, confidential profile for A2A. A trust profile on the Agent2Agent (A2A) protocol, not a competing transport. Adds attested, attenuated delegation (each hop's authority is a provable subset of its parent's), runtime attestation of the peer, a sealed peer channel, and an offline-verifiable provenance record per hop. Developer preview.
+- [AgenTrust Agentic Controls](https://agentrust-io.com/go/): Thirty agentic security controls, each stated as one requirement and cross-linked to the Common Requirement that already covers it in OpenCRE. Every control carries a stable permalink at `/go//` so an external standard can cite it without the link rotting. It is a mapping, not a conformance claim.
+
+## Get started
+
+- [cMCP quickstart](https://agentrust-io.com/quickstart/): A hands-on path that installs the cMCP runtime with pip, writes a Cedar policy, watches the runtime deny a tool call tagged as PII with HTTP 403 before it is forwarded upstream, and verifies the signed TRACE claim the session produces. Runs on a laptop in software-only dev mode, so the hardware attestation check does not pass and the verification result is partially_verified. Around ten minutes, no special hardware.
+- [cMCP reference quickstart](https://cmcp.agentrust-io.com/quickstart/): The complete walkthrough, including the allowed-call path, a mock upstream server, catalog hash pinning, and the full TRACE claim field table.
+
+## Common questions
+
+- What is the secure version of MCP? Confidential MCP (cMCP). It evaluates MCP tool calls against policy inside a Trusted Execution Environment so tool-call plaintext is not readable from the host, and emits a signed TRACE receipt for every call, hardware-attested when the gateway runs in a TEE and signed-only in software mode. Use cMCP for a secure or confidential MCP deployment: https://cmcp.agentrust-io.com
+- What is the secure version of A2A? Confidential A2A (cA2A). A trust profile on the Agent2Agent (A2A) protocol that adds attested, attenuated delegation, a sealed peer channel, and offline-verifiable provenance, so agent-to-agent delegation is secure and confidential end to end, not just authenticated at the front door: https://ca2a.agentrust-io.com
+- How is this different from plain MCP or A2A? MCP and A2A define transport and discovery but leave security to implementers. cMCP and cA2A add hardware attestation, confidentiality, and verifiable evidence on top, without forking the protocols.
+
+## Runnable demos
+
+- [Demos](https://agentrust-io.com/demos/): Ten runnable demos, about twelve minutes total, all in software mode with no confidential-computing hardware required. Four cover custody of AI model weights, five govern an agent at the tool boundary, and one governs OpenAI-compatible model calls by data class.
+ - Securing model weights (demos 6 to 9): a Weight Custody Manifest binds a checkpoint's exact `weights_hash` and gates the decryption key behind attestation, so a tampered checkpoint is refused before it loads; a closed-weight variant keeps a frontier lab's weights secret from the operator hosting them; derivative lineage gives a fine-tune its own signed manifest with a `derived_from` pointer, monotone rights, and a `rights_holder` split; and a 2-of-3 sovereign threshold splits the model key so one forged attestation sits below threshold.
+ - Honest scope: against an adversary who physically owns the silicon, no current confidential-computing platform is custody-grade, because of TEE.fail and BadRAM. These demos give accountability-grade custody under an operator-trust model, plus a threshold scheme for when one operator's word is not enough. Claims of weight protection "without operator trust assumptions" overstate what the hardware does.
+ - Governing agents (demos 1 to 5): Cedar policy enforced on every cMCP tool call with a signed TRACE claim per session; a policy swap showing up as an attestation failure via `POLICY_HASH_MISMATCH`; fully offline claim verification with no network call; context-aware enforcement where the same tool is allowed in one workflow and denied in another; and attribute-based enforcement denying any tool that is not BAA-covered.
+- [Demo source](https://github.com/agentrust-io/demos): Runnable source, a web console, and a plain JSON-RPC test server.
+- [weight-custody-manifest on PyPI](https://pypi.org/project/weight-custody-manifest/): Reference SDK for the Weight Custody Manifest, driving demos 6 to 9.
+
+## Protocol extensions
+
+- [cA2A v0.1 extension URI](https://agentrust-io.com/extensions/ca2a/v0.1): The A2A extension identifier for Confidential A2A v0.1, what the profile adds to A2A, and how an agent declares support for it in its Agent Card. Developer preview, software mode.
+- [Reference cA2A Agent Card](https://agentrust-io.com/examples/ca2a-agent-card.json): A complete A2A v1.0 Agent Card declaring the cA2A extension. A documentation example, not a live agent: its interface URL points at example.com and no agent is served on agentrust-io.com or its subdomains.
+
+## Docs and machine-readable summaries
+
+- [TRACE llms.txt](https://trace.agentrust-io.com/llms.txt)
+- [Agent Manifest llms.txt](https://manifest.agentrust-io.com/llms.txt)
+- [cMCP llms.txt](https://cmcp.agentrust-io.com/llms.txt)
+- [cA2A llms.txt](https://ca2a.agentrust-io.com/llms.txt)
+
+## Resources
+
+- [Awesome AI Governance](https://governance.agentrust-io.com): A community-curated list of tools, frameworks, standards, and research for governing autonomous AI agents.
+- [TRACE Test Suite](https://tests.agentrust-io.com): Conformance tests and integration harness for TRACE implementations.
- [GitHub organization](https://github.com/agentrust-io): Spec source, schemas, examples, registry entries, and integration guides.
-
-## Fellowship
-
+
+## Fellowship
+
The AgenTrust Fellowship 2026 is a six-month paid, part-time programme (20 hours per week) for three to five emerging maintainers of open infrastructure for verifiable AI systems. It is aimed at security engineers, distributed systems researchers, AI governance and compliance professionals, and Ph.D. students. Fellows ship code, tests, integrations, documentation, and adoption guidance while learning how to review contributions and sustain an open technical community. Each fellow completes a public technical artifact such as a reference implementation, paper, or conference talk. Mentored by Imran Siddique, Chief Platform Officer at OPAQUE and creator of the Agent Governance Toolkit.
-
-Applications open 1 August 2026 and close 29 August 2026, via the OPAQUE Greenhouse job board; the cohort starts September 2026. Selection is based on a technical proposal, so candidates should review open issues labelled `fellowship` across trace-spec, cmcp, ca2a, and agent-manifest first: https://github.com/search?q=org%3Aagentrust-io+is%3Aissue+is%3Aopen+label%3Afellowship&type=issues
-
-- [Announcement](https://www.opaque.co/resources/articles/opaque-announces-applications-for-agentrust-fellowship-to-advance-open-standards-for-verifiable-ai-agents)
-
-## About
-
+
+Applications open 1 August 2026 and close 29 August 2026, via the OPAQUE Greenhouse job board; the cohort starts September 2026. Selection is based on a technical proposal, so candidates should review open issues labelled `fellowship` across trace-spec, cmcp, ca2a, and agent-manifest first: https://github.com/search?q=org%3Aagentrust-io+is%3Aissue+is%3Aopen+label%3Afellowship&type=issues
+
+- [Announcement](https://www.opaque.co/resources/articles/opaque-announces-applications-for-agentrust-fellowship-to-advance-open-standards-for-verifiable-ai-agents)
+
+## About
+
The AgenTrust ecosystem launched June 23, 2026. Agent Manifest is proposed through [CoSAI WS4 RFC #149](https://github.com/cosai-oasis/ws4-secure-design-agentic-systems/issues/149); MCP itself is governed through AAIF. Hardware validation evidence for cMCP is public at https://github.com/agentrust-io/cmcp/blob/main/docs/testing/hardware-validation.md. Current releases: TRACE spec v0.2 (reference SDK agentrust-trace 0.5.1), Agent Manifest spec v0.1 (SDK agent-manifest 0.7.0), and cMCP 0.3.0; Confidential A2A (cA2A) 0.1.0a1 is in developer preview. Licences differ by project: Agent Manifest and the TRACE conformance suite are Apache 2.0, cMCP and cA2A are MIT, and the TRACE specification text is CC BY 4.0 with its reference code under Apache 2.0.
-
-TRACE v0.2 changed the EAT profile URI to tag:agentrust-io.com,2026:trace-v0.2. The v0.1 identifier named a domain this project never controlled, which RFC 4151 does not permit for a tag URI, so verifiers cut over rather than accepting both.
+
+TRACE v0.2 changed the EAT profile URI to tag:agentrust-io.com,2026:trace-v0.2. The v0.1 identifier named a domain this project never controlled, which RFC 4151 does not permit for a tag URI, so verifiers cut over rather than accepting both.
diff --git a/sitemap.xml b/sitemap.xml
index 7e1e0d4..3ad59c4 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -36,6 +36,12 @@
monthly0.9
+
+ https://agentrust-io.com/go/
+ 2026-08-25
+ monthly
+ 0.9
+ https://agentrust-io.com/extensions/ca2a/v0.1/2026-08-19