---
aimd: "1.0"
mako: "1.0"
type: "article"
entity: "Revocation with receipts"
updated: "2026-09-16"
tokens: 225
language: "en"
canonical: "https://demo.aifeed.md/blog/revocation"
summary: "Multi-signature status documents, bounded staleness, and offline bundles."
alternates:
  - url: "https://demo.aifeed.md/blog/revocation/"
    lang: "en"
  - url: "https://demo.aifeed.md/id/blog/revocation/"
    lang: "id"
media:
  cover:
    url: "https://aifeed.md/og-image.png"
    alt: "Revocation with receipts"
aifeed:
  assets:
    - url: "/assets/blog-revocation.svg"
      type: "image"
    - url: "https://revoked.aifeed.md"
      type: "document"
      title: "revoked demo"
      alt: "revoked demo"
---

[Home](/) / [Blog](/blog/) / Revocation

![](/assets/blog-revocation.svg)

Two governance keys must agree before status changes take effect.

By the AIFeed team September 2026 7 min read crypto

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".

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

See the [revoked demo](https://revoked.aifeed.md) for the full flow, including what a well-behaved client does when a manifest that verified yesterday comes back suspended today.

- [Delta indexes: skipping what did not change](/blog/delta-indexes/)

Share [Email](mailto:?subject=Revocation%20with%20receipts&body=https%3A%2F%2Fdemo.aifeed.md%2Fblog%2Frevocation%2F)
## Media & Unduhan

- [/assets/blog-revocation.svg](/assets/blog-revocation.svg) — image
- [revoked demo](https://revoked.aifeed.md) — document