Whitepaper V4.1
Appendix F — Agent Identity, Policy and Evidence Schemas
F.1 Agent Birth Certificate — minimum public schema
{
"schema": "ionon.agent-birth-certificate/1.0",
"agent_did": "did:ionon:agent:<handle>:<slug>",
"serial": "IONON-AGENT-...",
"issued_at": "ISO-8601",
"issuer": "did:ionon:issuer:identity",
"principal_reference": "privacy-preserving reference",
"verification_tier_at_birth": "NONE|KYC|KYB|INSTITUTIONAL",
"lineage": "non-transferable",
"status": "ACTIVE|SUSPENDED|REVOKED",
"policy_passport": "urn:ionon:policy:...",
"certificate_hash": "sha256:...",
"evidence": ["signed issuer proof"]
}
The schema can be represented as an IONON-native object while remaining mappable to W3C Verifiable Credentials 2.0. No private personal data needs to be public for a verifier to check issuer, status and integrity.
F.2 Agent Policy Passport — minimum control schema
{
"schema": "ionon.policy-passport/1.0",
"principal": "...",
"agent": "...",
"legal_entity": "...",
"jurisdiction": ["US"],
"roles": ["procurement"],
"allowed_tools": ["mcp://..."],
"allowed_chains": ["ethereum"],
"allowed_assets": ["USDC", "IONON"],
"counterparty_policy": "allowlist-or-risk-policy",
"per_action_limit": "...",
"daily_limit": "...",
"human_approval_above": "...",
"valid_from": "...",
"expires_at": "...",
"kill_switch": true,
"evidence_level": "FULL"
}
F.3 Order / Mandate — normalized economic intent
An Order must identify originator, asset, amount, destination, deadline, max cost/slippage, policy context, idempotency key and signature. The Order remains independent of the final route so the Router can compare permitted execution paths without changing user intent.
F.4 Evidence record
Every material action should emit a tamper-evident record that binds:
principal + agent + order + policy version + simulation + approval + route + signatures + transaction receipts + timestamps.
This evidence object is the bridge between software automation, internal controls, external audit and dispute resolution.