Five universal pillars. One Ed25519 signature. The credential every accountable agent carries.
agent_id + operator_id required. Every action attributable to a real, named operator under a real jurisdiction.
Ed25519-signed governance_payload. Anyone holding the public key can verify what was claimed at issuance.
4-level enum: minimal / limited / high / critical. Drives the rule pack the agent is governed against at runtime.
Cryptographically chained issuance + amendment history. Tampering is detectable, not just disallowed.
Revocable in real time via /registry/revoke. Stale passports fail verification at every downstream check.
The passport is a JSON document signed by AiEGIS at issuance. The body carries the five pillars. The signature is Ed25519 over the canonical bytes. Every field below is required in production passports.
// Agent passport — issued by /api/agent/issue { "agent_id": "agent_b3a9f1...", // 01 — Accountability "operator_id": "op_acme_corp", "jurisdiction": "EU", // drives rule pack selection "risk_classification": "high", // 03 — minimal | limited | high | critical "policy_bundle": "eu_ai_act+gdpr", "capability_attestation": { // from model provider "model": "claude-opus-4-7", "provider_signature": "..." }, "audit_lineage_hash": "sha256:...", // 04 — chained from previous "issued_at": "2026-05-08T22:00:00Z", "expires_at": "2027-05-08T22:00:00Z", "revocation_check": "call POST /api/agent/verify to check revocation status", "signature": "ed25519:..." // 02 — over canonical bytes of body }
Issuance generates an Ed25519 keypair. AiEGIS holds the private key in your customer-cloud HSM. The public keys are published at /registry/keys; verifiers can call /api/agent/verify server-side or check signatures locally against the published key.
Every verify is a real Ed25519 signature check against canonical bytes — non-negotiable from v1.0.
Sub-15ms p95 verify latency on customer infrastructure (loopback). Sub-300ms over public HTTPS.