Issuer and key id
The scaffold already declares the future issuer and kid so verification logic has a stable identity anchor.
AgntBase now exposes a publish-ready Signed Agent Card layer: issuer, planned key id, signing policy, reserved verification routes, rollout status and file contracts. This keeps the trust model explicit without falsely claiming that the current Agent Card is already signed.
This lets us wire the ecosystem in the right order: files, docs, policy, reserved artifact routes, then real signing keys and verified signatures.
The scaffold already declares the future issuer and kid so verification logic has a stable identity anchor.
The policy file fixes the algorithm, canonicalization path, keyset route and activation expectations before any real signature is published.
The signed Agent Card route and detached JWS route already exist, but clearly state that active cryptographic material is not live yet.
We are sequencing this so nothing breaks when the real signature turns on.
| Now | Public Agent Card is readable. Scaffold, signing policy, keyset placeholder and reserved artifact routes are public. A2A method agent.signature_status reports rollout state. |
|---|---|
| Next | Publish real public signing keys and the real signed card artifact, then flip verification status from publish-ready scaffold to active. |
| Later | Registry can show signed-card verification, key rotation state and freshness as first-class trust signals. |
These are the current URLs to use when trust and provenance matter.
| Scaffold JSON | /.well-known/agent-card-signature-scaffold.json |
|---|---|
| Signing policy | /.well-known/agent-card-signing-policy.json |
| Keyset placeholder | /.well-known/agent-card-signing-keys.json |
| Reserved signed artifact | /.well-known/agent-card.signed.json |
| Reserved detached JWS | /.well-known/agent-card.jws |
| Public card | /.well-known/agent-card.json |
| A2A method | agent.signature_status on /a2a/jsonrpc |
| Status documents | scaffold statuspublish-ready status |