---
aimd: "1.0"
mako: "1.0"
type: "article"
entity: "Client guide — what to do on SUSPENDED"
updated: "2026-09-16"
tokens: 165
language: "en"
canonical: "https://revoked.aifeed.md/guide"
summary: "The five-step reaction a compliant agent follows when status changes."
alternates:
  - url: "https://revoked.aifeed.md/guide/"
    lang: "en"
  - url: "https://revoked.aifeed.md/id/guide/"
    lang: "id"
media:
  cover:
    url: "https://aifeed.md/og-image.png"
    alt: "Client guide — what to do on SUSPENDED"
---

[Home](/) / Client guide

# What a compliant client does

## The five steps

- Re-check the registry URL from the manifest before using restricted content.

- Verify the document's signatures against the published governance keys.

- If status is suspended , treat restricted uses as denied immediately.

- If the registry is unreachable for more than 168 hours, downgrade to UNVERIFIED .

- Keep the document in the audit bundle; never silently fall back to HTML scraping.

## In code

```
node examples/agent/compliant-agent.js https://revoked.aifeed.md --json
# status: SUSPENDED → restricted uses refused
```

## Audit bundles

The offline bundle records the manifest, signatures, and the registry document as it was seen, so a later review can reconstruct exactly why a decision was made.