Skip to content

AGENTS.md

Latest commit

 

History

History
128 lines (100 loc) · 4.18 KB

AGENTS.md

File metadata and controls

128 lines (100 loc) · 4.18 KB

AGENTS.md

Agent-readable metadata for PEAC Protocol. Last reviewed: 2026-04-01

Identity

  • Protocol: PEAC (wire formats: interaction-record+jwt (current), peac-receipt/0.1 (frozen legacy))
  • Specification: https://www.peacprotocol.org
  • Key Discovery: iss -> /.well-known/peac-issuer.json -> jwks_uri -> JWKS
  • Algorithm: EdDSA (Ed25519)

Capabilities

  • Receipt Issuance and Verification: Signed receipts (interaction-record+jwt JWS) for verifiable interaction evidence
  • Purpose Declaration: Structured intent via PEAC-Purpose header
  • Agent Identity: Proof-of-control binding (see AGENT-IDENTITY.md)
  • Policy Discovery: Machine-readable terms at /.well-known/peac.txt

Proof Methods

Method Standard Description
http-message-signature RFC 9421 HTTP Message Signatures
dpop RFC 9449 DPoP token binding
mtls RFC 8705 Mutual TLS client certificate
jwk-thumbprint RFC 7638 JWK Thumbprint confirmation

MCP Integration

PEAC receipts attach to MCP tool responses via the Evidence Carrier Contract.

JSON-RPC Response (_meta carrier):

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [...],
    "_meta": {
      "org.peacprotocol/receipt_ref": "sha256:abc123...",
      "org.peacprotocol/receipt_jws": "eyJhbGciOiJFZERTQSIsInR5cCI6ImludGVyYWN0aW9uLXJlY29yZCtqd3QiLC..."
    }
  }
}

HTTP Transport:

PEAC-Receipt: eyJhbGciOiJFZERTQSIsInR5cCI6ImludGVyYWN0aW9uLXJlY29yZCtqd3QiLC...

The PEAC-Receipt header carries a compact JWS (never a bare receipt_ref).

A2A Agent Card Extension

For A2A (Agent-to-Agent Protocol, Linux Foundation) discovery via /.well-known/agent-card.json:

Agent Card (capabilities.extensions[] array, A2A v1.0.0):

{
  "name": "Example Agent",
  "supportedInterfaces": [
    {
      "url": "https://agent.example",
      "protocolBinding": "http+json",
      "protocolVersion": "1.0.0"
    }
  ],
  "capabilities": {
    "extensions": [
      {
        "uri": "https://www.peacprotocol.org/ext/traceability/v1",
        "description": "PEAC evidence traceability for agent interactions",
        "required": false
      }
    ]
  }
}

Evidence carrier in A2A metadata (TaskStatus, Message, Artifact):

{
  "metadata": {
    "https://www.peacprotocol.org/ext/traceability/v1": {
      "carriers": [
        {
          "receipt_ref": "sha256:abc123...",
          "receipt_jws": "eyJhbGciOi..."
        }
      ]
    }
  }
}

The extension URI key maps to a nested object containing the carrier array. This follows the A2A metadata convention. A2A v1.0.0 Agent Card shape is required; v0.3.0 compatibility was removed in v0.13.0 (DD-186). Cards without a valid supportedInterfaces[0].url are rejected.

Discovery

Path Content Specification
/.well-known/peac.txt Policy manifest PEAC-TXT.md
/.well-known/peac-issuer.json Issuer config and key discovery PEAC-ISSUER.md
/.well-known/agent-card.json A2A Agent Card (PEAC extension) DISCOVERY-PROFILE.md

Purpose Tokens

Canonical PEAC purpose vocabulary:

Token Description
train Model training data collection
search Traditional search indexing
user_action Agent acting on user behalf
inference Runtime inference / RAG
index Content indexing (store)

Contact