Standards
The first standards family
The initial family is deliberately small and foundational: seven standards covering identity, trust, security, certification, evidence, accreditation and cryptographic agility. Standards are referenced by the stable IAASO-NNNN:version convention.
| Code | Title | Stage |
|---|---|---|
| IAASO-1001 | Autonomous Agent Identifier StandardCanonical agent identifiers: the UUAID compact form (Profile A) and the IAASO federated form (Profile B), resolution semantics, tombstones and supersession. | Committee Draft |
| IAASO-1101 | Agent Trust Profile StandardThe machine-readable trust profile object: capabilities, assurances, applicable standards references and evaluation posture for an autonomous agent. | Working Draft |
| IAASO-1201 | Agent Security and Runtime Governance StandardSecurity baseline and runtime governance requirements for operating autonomous agents, including access control, audit logging and key rotation. | Working Draft |
| IAASO-1301 | Certification Credential and Status StandardCertification credentials, the ten-value status model (draft through superseded), status history and revocation propagation. | Committee Draft |
| IAASO-1401 | Evidence and Verifiable Trust Streams StandardEvidence objects, transparency statements, Merkle inclusion receipts and anchor references for continuously verifiable trust. | Working Draft |
| IAASO-1501 | Accreditation of Issuers, Assessors, and Verifiers StandardAccreditation objects and workflow for the entities that examine, certify and verify agents, with signed status transitions. | Committee Draft |
| IAASO-1601 | Cryptographic Agility and Post-Quantum Readiness StandardCrypto-agile signature suites (Ed25519 today, ML-DSA-65 reserved), RFC 8785 JCS canonicalization, keccak256 hashing and the crypto inventory. | Working Draft |
ALifecycle stages
Every standard advances through the thirteen-stage draft lifecycle defined in the Standards Governance Manual, Part V. Each stage transition is recorded with the approving body, decision date and rationale.
BMachine-readable artifacts
The normative machine-readable truth for each standard is its shipped JSON Schema and conformance vectors — where prose and schema disagree, the schema wins and the prose receives an erratum. Schemas (v1 and v1.1), OpenAPI descriptions, examples and the conformance runner are published in the open repository at github.com/uuaid.