You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hub, quickstart, demos, telemetry, and the cA2A extension page were each
carrying their own stylesheet and their own palette. Quickstart was dark navy
on Montserrat/Roboto, demos and the extension page were the old light navy
theme, and telemetry duplicated the editorial styles inline.
Add a shared .at-page layer to design-system.css: header, hero, section
rhythm, cards and grids, the hairline flow strip, callouts, buttons, code
blocks with a copy bar, terminal, stepper, check rows, verdict panel, tables,
footer, one breakpoint. A page now opts in with <body class="at-page"> and
writes no CSS of its own, so the four subpages carry zero page-level styles.
supernav.js reads its colours from the same tokens instead of a hardcoded
palette, which also aligns the four MkDocs subdomains that load both files
from here. Drops the nine-colour dot set, adds Quickstart, and resolves the
active item for /quickstart and /extensions/ca2a.
On the hub, remove the hand-built domain nav: it duplicated the supernav list
verbatim one row below it. Rather than rewrite its 500 lines of inline CSS,
remap its legacy variables onto the editorial tokens once, so the page
resolves through one palette rather than two.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
<pclass="sub">This page is what the cA2A v0.1 extension URI resolves to. The URI is an identifier, not an endpoint: A2A agents put it in their Agent Card to advertise the profile, and clients echo it in the <code>A2A-Extensions</code> header to opt in.</p>
<p>This page is what the cA2A v0.1 extension URI resolves to. The URI is an identifier, not an endpoint: A2A agents put it in their Agent Card to advertise the profile, and clients echo it in the <code>A2A-Extensions</code> header to opt in.</p>
<strong>No agent is served on this domain.</strong> agentrust-io.com and its subdomains publish specifications and documentation. They do not host an A2A agent, an MCP server, or a Signed Agent Card. The card linked below is a reference example whose interface URL points at <code>example.com</code> deliberately.
62
+
<divclass="callout caution">
63
+
<p><strong>No agent is served on this domain.</strong> agentrust-io.com and its subdomains publish specifications and documentation. They do not host an A2A agent, an MCP server, or a Signed Agent Card. The card linked below is a reference example whose interface URL points at <code>example.com</code> deliberately.</p>
164
64
</div>
165
65
166
-
<h2>What the extension adds</h2>
167
-
168
66
<p>A2A's Signed Agent Card answers one question: did the domain owner issue this card. cA2A adds a trust envelope around a delegated task, carried entirely in A2A extension metadata. It defines no new wire format and no new endpoint. Removing every cA2A key from a message leaves a valid A2A task, which is what lets a cA2A deployment interoperate with peers that have never heard of the profile.</p>
<tr><td>Task payload</td><td>Sealing to the peer's attested measurement</td></tr>
175
73
<tr><td>(none)</td><td>A per-hop provenance record linking to its parent, forming the delegation DAG</td></tr>
176
74
</table>
75
+
</section>
177
76
178
-
<h2>Declaring support</h2>
179
-
77
+
<sectionid="declare">
78
+
<spanclass="label">Declaring support</span>
79
+
<h2>One entry in the Agent Card</h2>
180
80
<p>An agent supporting the profile advertises the URI under <code>capabilities.extensions</code> in its Agent Card:</p>
181
81
182
82
<pre><code>{
@@ -194,26 +94,47 @@ <h2>Declaring support</h2>
194
94
<p><code>required</code> is <code>false</code> because the profile is an overlay. A cA2A peer must treat a message carrying no cA2A keys as ordinary A2A input rather than synthesise a partial trust state from their absence, so a card that advertises cA2A still serves plain A2A clients.</p>
195
95
196
96
<p>A complete reference card, valid against the A2A v1.0 <code>AgentCard</code> definition, is at <ahref="/examples/ca2a-agent-card.json">/examples/ca2a-agent-card.json</a>.</p>
97
+
</section>
197
98
198
-
<h2>Status</h2>
199
-
99
+
<sectionid="status">
100
+
<spanclass="label">Status</span>
101
+
<h2>Developer preview, stated plainly</h2>
200
102
<p>cA2A v0.1 is a developer preview and will change shape before v1. The delegation chain is verified and the payload is sealed, but binding that seal to a hardware-verified peer measurement is not yet wired: the reference transport runs in software mode with <code>assurance="none"</code>. Running the peer path end to end off hardware is not evidence that cA2A is attested across trust domains.</p>
103
+
</section>
201
104
202
-
<h2>Normative sources</h2>
203
-
204
-
<p>This page is orientation. The binding is specified in the cA2A documentation, and that is the text to implement against:</p>
205
-
105
+
<sectionid="normative">
106
+
<spanclass="label">Normative sources</span>
107
+
<h2>This page is orientation</h2>
108
+
<p>The binding is specified in the cA2A documentation, and that is the text to implement against:</p>
206
109
<ul>
207
110
<li><ahref="https://ca2a.agentrust-io.com/docs/spec/transport/">Transport binding</a>, including the namespaced metadata keys and what ships today versus what does not</li>
208
111
<li><ahref="https://ca2a.agentrust-io.com/docs/spec/profile/">Profile</a>, the normative requirements P-1 onward</li>
0 commit comments