Trust that can be checked

Material governance events — ratifications, status changes, accreditation actions, revocations — are recorded as structured governance events in a hash-chained ledger operated on the UUAID trust infrastructure. Ledger heads are periodically anchored to the Polygon blockchain, so the record's integrity does not depend on trusting IAASO's servers: any party can independently verify that history has not been rewritten.

Events are signed (UUAID SignatureEnvelope: JCS canonicalization, Ed25519, crypto-agile by design — Art. XVII) and remain verifiable across cryptographic transitions.

Certification and accreditation status is not a private letter — it is a public, queryable state (Art. X §5, Art. XI §4). IAASO does not run a duplicate registry: the live UUAID registry at api.uuaid.org is the sole subject registry, and registry.uuaid.org is its public face. Anyone can resolve an agent's identifier and check its certification standing — current, suspended, revoked, or expired — without asking permission.

Where continuous assurance applies, status carries freshness semantics: stale or contradictory evidence has status consequences (Art. XI §5). No false permanence (Art. IX §5).

Article XV §4 makes a deliberately uncomfortable promise: standards history, public records, and trust-state references remain exportable, inspectable, and preservable — such that continuity is not destroyed by institutional conflict. If IAASO were ever captured or corrupted, the community could take the record and continue without it.

This is the deepest anti-capture safeguard: an institution whose records can walk away has no incentive to betray them. The same doctrine governs dissolution (Art. XX): standards legitimacy cannot be covertly transferred to a private or opaque structure.