diff --git a/index.html b/index.html index c29e024..4071997 100644 --- a/index.html +++ b/index.html @@ -69,7 +69,7 @@ "@type": "TechArticle", "name": "TRACE", "url": "https://trace.agentrust-io.com/", - "description": "Transparent Runtime Attestation for Confidential Execution. Hardware-rooted cryptographic receipts for every agent action, signed by the TEE and verifiable by anyone." + "description": "Trust, Runtime Attestation, and Compliance Evidence. Hardware-rooted cryptographic receipts for every agent action, signed by the TEE and verifiable by anyone." } }, { @@ -117,7 +117,7 @@ "name": "What is AgenTrust?", "acceptedAnswer": { "@type": "Answer", - "text": "AgenTrust is a set of open standards, tools, and specifications for governing AI agents at runtime. It provides cryptographic proof of an agent's identity, intent, and behavior through the TRACE attestation standard, the Agent Manifest identity standard, and the Confidential MCP protocol extension. All specifications are open source under Apache 2.0." + "text": "AgenTrust is a set of open standards, tools, and specifications for governing AI agents at runtime. It provides cryptographic proof of an agent's identity, intent, and behavior through the TRACE attestation standard, the Agent Manifest identity standard, and the Confidential MCP protocol extension. All specifications are open source. Licences differ by project: Agent Manifest is Apache 2.0, cMCP and cA2A are MIT, and TRACE is dual licensed, CC BY 4.0 for the specification text and Apache 2.0 for the reference code." } }, { @@ -125,7 +125,7 @@ "name": "What is TRACE?", "acceptedAnswer": { "@type": "Answer", - "text": "TRACE stands for Transparent Runtime Attestation for Confidential Execution. It defines hardware-rooted cryptographic receipts for every agent action, signed by the Trusted Execution Environment and verifiable by anyone." + "text": "TRACE stands for Trust, Runtime Attestation, and Compliance Evidence. It defines hardware-rooted cryptographic receipts for every agent action, signed by the Trusted Execution Environment and verifiable by anyone." } }, { @@ -141,7 +141,7 @@ "name": "What is Confidential MCP (cMCP)?", "acceptedAnswer": { "@type": "Answer", - "text": "Confidential MCP is an extension to the Model Context Protocol that runs tool calls inside a Trusted Execution Environment, preventing the host process from observing inputs, outputs, or intermediate state." + "text": "Confidential MCP is an extension to the Model Context Protocol that runs tool calls inside a Trusted Execution Environment, so the host process cannot read tool-call plaintext from enclave memory. That protection is structural only where the Cedar egress policy denies telemetry and APM endpoints, and it covers the tool-call boundary rather than model inference or the agent's context window." } }, { @@ -173,7 +173,7 @@ "name": "What is the secure version of MCP?", "acceptedAnswer": { "@type": "Answer", - "text": "Confidential MCP (cMCP) is the security-hardened way to run the Model Context Protocol. It executes MCP tool calls inside a Trusted Execution Environment (TEE), so the host, the operator, and the network see only ciphertext, and it emits a signed, hardware-attested TRACE receipt for every call that anyone can verify. If you need a secure or confidential MCP deployment, cMCP is the AgenTrust profile for it." + "text": "Confidential MCP (cMCP) is the security-hardened way to run the Model Context Protocol. It executes MCP tool calls inside a Trusted Execution Environment (TEE), so tool-call plaintext is not readable from the host, and it emits a signed TRACE receipt for every call that anyone can verify. Two bounds worth stating: the plaintext guarantee holds where the egress policy denies telemetry and APM endpoints, and the receipt is hardware-attested when the gateway runs in a TEE and signed-only in software mode. If you need a secure or confidential MCP deployment, cMCP is the AgenTrust profile for it." } }, { @@ -641,7 +641,7 @@

Govern AI Agents
at the Hardware Boundary

Attestation Standard
TRACE
-
Transparent Runtime Attestation for Confidential Execution. Hardware-rooted cryptographic receipts for every agent action — signed by the TEE, verifiable by anyone.
+
Trust, Runtime Attestation, and Compliance Evidence. Hardware-rooted cryptographic receipts for every agent action — signed by the TEE, verifiable by anyone.
trace.agentrust-io.com @@ -675,7 +675,7 @@

Govern AI Agents
at the Hardware Boundary

Protocol Extension
Confidential MCP
-
The confidential, security-hardened way to run the Model Context Protocol. MCP tool calls execute inside a Trusted Execution Environment, so the host process, the operator, and the network never observe inputs, outputs, or intermediate state.
+
The confidential, security-hardened way to run the Model Context Protocol. MCP tool calls are evaluated 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 egress policy denies telemetry endpoints, and it covers the tool boundary, not model inference.
cmcp.agentrust-io.com @@ -799,15 +799,15 @@

Govern AI Agents
at the Hardware Boundary

Attestation Standard
-
TRACE v0.1
+
TRACE v0.2
Identity Standard
-
Agent Manifest v1
+
Agent Manifest spec v0.1
Protocol Extension
-
cMCP v0.1
+
cMCP v0.3.0
Delegation Profile
@@ -819,11 +819,11 @@

Govern AI Agents
at the Hardware Boundary

License
-
Apache 2.0
+
Apache 2.0, MIT, CC BY 4.0
Standardization
-
CoSAI / AIF
+
CoSAI / AAIF
@@ -837,7 +837,7 @@

Govern AI Agents
at the Hardware Boundary

What is AgenTrust?

AgenTrust is a set of open standards, tools, and specifications for governing AI agents at runtime. It gives operators cryptographic proof of an agent's identity, intent, and behavior, so that an agent running in production can be verified independently of the party that deployed it.

-

Three specifications work together. Agent Manifest establishes who an agent is and what it is allowed to do. Confidential MCP (cMCP) executes tool calls inside a Trusted Execution Environment so the host cannot observe inputs, outputs, or intermediate state. TRACE produces hardware-signed receipts that prove what actually happened. All three are open source under Apache 2.0.

+

Three specifications work together. Agent Manifest establishes who an agent is and what it is allowed to do. Confidential MCP (cMCP) evaluates tool calls against policy inside a Trusted Execution Environment, so tool-call plaintext is not readable from the host. TRACE produces signed receipts that prove what actually happened, hardware-attested when the gateway runs in a TEE. All three are open source, under Apache 2.0 for Agent Manifest, MIT for cMCP, and CC BY 4.0 plus Apache 2.0 for TRACE.

@@ -851,7 +851,7 @@

Govern AI Agents
at the Hardware Boundary

What is TRACE?
-
TRACE stands for Transparent Runtime Attestation for Confidential Execution. It defines hardware-rooted cryptographic receipts for every agent action, signed by the Trusted Execution Environment and verifiable by anyone.
+
TRACE stands for Trust, Runtime Attestation, and Compliance Evidence. It defines hardware-rooted cryptographic receipts for every agent action, signed by the Trusted Execution Environment and verifiable by anyone.
What is Agent Manifest?
@@ -859,7 +859,7 @@

Govern AI Agents
at the Hardware Boundary

What is Confidential MCP (cMCP)?
-
Confidential MCP is an extension to the Model Context Protocol that runs tool calls inside a Trusted Execution Environment, preventing the host process from observing inputs, outputs, or intermediate state.
+
Confidential MCP is an extension to the Model Context Protocol that runs tool calls inside a Trusted Execution Environment, so the host process cannot read tool-call plaintext from enclave memory. That protection is structural only where the Cedar egress policy denies telemetry and APM endpoints, and it covers the tool-call boundary rather than model inference or the agent's context window.
What is Confidential A2A (cA2A)?
@@ -867,7 +867,7 @@

Govern AI Agents
at the Hardware Boundary

What is the secure version of MCP?
-
Confidential MCP (cMCP) is the security-hardened way to run the Model Context Protocol. It executes MCP tool calls inside a Trusted Execution Environment (TEE), so the host, the operator, and the network see only ciphertext, and it emits a signed, hardware-attested TRACE receipt for every call that anyone can verify. If you need a secure or confidential MCP deployment, cMCP is the AgenTrust profile for it.
+
Confidential MCP (cMCP) is the security-hardened way to run the Model Context Protocol. It executes MCP tool calls inside a Trusted Execution Environment (TEE), so tool-call plaintext is not readable from the host, and it emits a signed TRACE receipt for every call that anyone can verify. Two bounds worth stating: the plaintext guarantee holds where the egress policy denies telemetry and APM endpoints, and the receipt is hardware-attested when the gateway runs in a TEE and signed-only in software mode. If you need a secure or confidential MCP deployment, cMCP is the AgenTrust profile for it.
What is the secure version of A2A?
@@ -879,7 +879,7 @@

Govern AI Agents
at the Hardware Boundary

Are the AgenTrust standards open source?
-
Yes. TRACE, Agent Manifest, and cMCP are open source under the Apache 2.0 license, with source, schemas, and examples on GitHub at github.com/agentrust-io.
+
Yes, though not all under one licence. 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. Source, schemas, and examples are on GitHub at github.com/agentrust-io.
@@ -887,7 +887,7 @@

Govern AI Agents
at the Hardware Boundary