revoked.aifeed.md

Revocation with receipts

This origin demonstrates the registry side of AIFeed: multi-signature status documents, bounded staleness, and client behaviour when yesterday's VERIFIED becomes today's SUSPENDED.

See both registry states What clients do

The document

{
  "version": "0.1",
  "domain": "revoked.aifeed.md",
  "status": "suspended",
  "reason": "abuse_investigation",
  "revoked_by": "aifeed-demo-governance",
  "keys": [ { "fingerprint": "sha256:..." }, { "fingerprint": "sha256:..." } ],
  "signatures": [ { "...": "two of two required" } ]
}

Why two keys

No single point of failure

A compromised key cannot revoke an origin on its own — or restore one that was suspended.

Bounded staleness

If the registry is unreachable for more than 168 hours, clients downgrade to UNVERIFIED instead of assuming consent.