[Go to site: main page, start]

Open standards & artifacts for accountable systems.

Worked examples

Permanent link /examples

Worked examples

End-to-end worked scenarios that prove standards can ship with receipts, clocks, and enforceable remedies.

View featured example Browse scenarios

Why these matter

One complete example answers four critiques.

Each scenario proves the standards are enforceable, faster to ship, and measurable without audit theater.

Summary

Start with a single end-to-end example

Pick the featured scenario first, then use the required signals checklist to validate what your team ships.

Key takeaways

  • Every scenario includes receipts, owners, clocks, and remedies.
  • Required signals ensure enforceability, not just documentation.
  • Examples double as adoption templates for release gates.

Featured scenario

Automated account lock & eligibility flip

A full walkthrough that shows receipts, clocks, and remedies working together. Featured because it demonstrates the full adoption chain without special-case shortcuts.

What this scenario demonstrates

Use the featured example as the baseline template before reviewing the broader catalog.

  • Receipt and owner metadata issued at decision time.
  • Visible clocks for review, appeal, and remedy.
  • Remediation path that ties into bindings and evidence packs.
View featured example

Scenarios

End-to-end worked scenarios

Each scenario includes the receipt, owner, clocks, and evidence bundle required for audit-ready compliance.

Automated account lock & eligibility flip

A real-time fraud lock shows how receipts, owners, clocks, and remedies survive high-risk automation.

  • Receipt
  • Clocks
  • Remedy
View worked example

Content moderation takedown

A rapid removal flow with receipts, contested exceptions, and remedy commitments.

  • Receipt
  • Exceptions
  • Remedy
View worked example

Fraud hold with delayed notice

A delayed-notice hold that keeps clocks visible while preserving investigation integrity.

  • Clocks
  • Exceptions
  • Evidence
View worked example

Irreversible payment with compensation

An irreversible action flow that binds compensation and review clocks to receipts.

  • Irreversible
  • Remedy
  • Binding
View worked example

Automated eligibility denial

Eligibility denial with a named owner, appeal path, and enforceable remedy clocks.

  • Receipt
  • Clocks
  • Appeal
View worked example

Required signals

What every worked example must show

Use this checklist to validate that a scenario is enforceable and not just explanatory.

  • Receipt issued at the moment the decision is enforced.
  • Named owner + authority path with escalation rights.
  • Clocks for acknowledgment, review, and remedy.
  • Exception handling with bounded duration and review cadence.
  • Remedy path with reversal, compensation, or safe fallback.
  • Generated artifacts (decision log, evidence pack list, audit trail).

Need a reference bundle? Start with the Diagnostic Export Kit to see how outputs map to receipts, evidence lists, and stakeholder summaries.

How to use

Turn the example into binding adoption

These scenarios double as copy-paste templates for change requests and release gates.

  • Start with the receipt payload and map it to your own system state and logging tools.
  • Translate the owner + authority block into your on-call rotation and escalation policies.
  • Connect the evidence pack list to the Evidence Pack requirements before your next audit window.
  • Use the Binding vectors to tie the example to procurement language, release gates, and runbooks.