What this scenario demonstrates
Read this one first. The other scenarios vary it.
- Receipt and owner metadata issued at decision time.
- Visible clocks for review, appeal, and remedy.
- A remedy path tied to bindings and evidence packs.
Worked examples
Six worked scenarios that follow one automated decision from enforcement to remedy, and eight comparisons of oversight added on versus built in.
Featured scenario
Automated account lock & eligibility flip
The account lock is the baseline scenario. It runs every step from receipt to remedy, and no step relies on a special case.
End-to-end worked scenarios
Each scenario shows the receipt, the owner, the clocks, and the evidence an auditor would ask for.
Automated account lock & eligibility flip
A real-time fraud lock that still issues a receipt, names an owner, runs three clocks, and restores access when no fraud is confirmed.
- Receipt
- Clocks
- Remedy
Content moderation takedown
A rapid removal that issues a receipt, bounds its exceptions, and restores the content if the takedown is overturned.
- Receipt
- Exceptions
- Remedy
Fraud hold with delayed notice
A hold whose notice is delayed for the investigation, while its review clocks keep running and stay on record.
- Clocks
- Exceptions
- Evidence
Irreversible payment with compensation
A payment that cannot be reversed, so the receipt commits to compensation and review deadlines instead.
- Irreversible
- Remedy
- Binding
Decision-model gate on refunds
A refund agent gated by a typed decision model, with the threshold held as policy, a sampled review queue, and decisions that record what decided them.
- Threshold
- Chain
- Reasons
Automated eligibility denial
An eligibility denial on an income mismatch, with a named owner, an appeal path, and remedy clocks the owner is held to.
- Receipt
- Clocks
- Appeal
Domain comparisons
Architecture vs standard governance
Eight comparisons. Each sets oversight added after the fact beside a system where a challenge reaches the owner of the rule.
Government public services
Benefits and debt automation where an upheld challenge has to reach the rule's owner.
- Rule owners
- Contestability
- Restoration
Loan approval systems
Credit scoring where an applicant gets reasons, and a pattern of upheld challenges changes the rule.
- Stoppability
- Contestability
- Time-to-halt
Financial fraud detection
Real-time account protection that must restore legitimate access on a deadline and on the record.
- Time-to-restore
- Receipt
- Repair log
Healthcare diagnostic AI
Clinical risk tools where clinicians' overrides are counted against the model's rule.
- Overrides
- Contestability
- Reversibility
FHIR resources for healthcare interop
Denials, appeals, and repair status as FHIR resources that payers, providers, and regulators share.
- Interoperability
- Repair status
- Decision clocks
Customer service chatbots
Support bots where reaching a person is a right, and failed requests count against the design.
- Contestability
- Stoppability
- Care floors
Retail personalization
A boundary case. Most recommendations decide nothing a person could challenge. Prices, credit offers, and job ads do.
- Boundary case
- Reasons
- Rollback
An AI agent acting for one person
A boundary case. The person who grants the agent its authority is usually the one its mistakes land on, and no institution answers for the delegation.
- Boundary case
- Expiry
- Independent records
Each example names the context it belongs to, the standards to bind, and the check to run first. Retail personalization and an agent acting for one person are boundary cases. Which systems this is for
Required signals
What every worked example must show
A scenario missing any of these describes a decision. It does not show one that can be enforced or challenged.
- Receipt issued at the moment the decision is enforced.
- A named owner who can change the decision, and who it escalates to.
- Clocks for acknowledgment, review, and remedy.
- Exception handling with bounded duration and review cadence.
- Remedy path with reversal, compensation, or safe fallback.
- Upheld challenges counted against the rule and sent to its owner.
- Generated artifacts (decision log, evidence pack list, appeal record).
Turn the example into binding adoption
Each scenario can be copied into a change request or a release gate.
- 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.