By the AIFeed teamSeptember 20267 min readcrypto

A registry that cannot be forged and cannot be ignored is the difference between policy and enforcement.

Status lives in documents signed by multiple governance keys. A single compromised key cannot mark an origin as revoked, or quietly restore one that was suspended. Clients re-check status at use time and treat registry silence beyond 168 hours as UNVERIFIED rather than "probably fine".

  1. Fetch the revocation URL from the manifest.
  2. Verify the document signatures against the published governance keys.
  3. Apply the status: active, under_review, or suspended.
  4. Record the document in the audit bundle.

See the revoked demo for the full flow, including what a well-behaved client does when a manifest that verified yesterday comes back suspended today.