Fraud
Remedy execution may pause while fraud is validated.
- Receipt, owner assignment, and review clock remain mandatory.
- Proposed maximum: 72 hours. Proposed review: every 12 hours.
Bounded exceptions framework
Five exceptions, from fraud to legal hold, that may delay a remedy for a set time. The receipt, owner, and clock stay mandatory. The durations are proposals.
Exception classes
Bounded exceptions with required minimums
Each class says what may be delayed and what stays mandatory. The durations are proposed defaults. No standard on this site contains them yet, so an operator that adopts the framework sets its own and publishes them.
Abuse/safety
Full remediation can pause if immediate harm is likely.
- Receipt, owner, and acknowledgment clock are still required.
- Proposed maximum: 48 hours. Proposed review: every 8 hours.
Security
Remedy may be staged to preserve forensic integrity.
- Receipt, owner, and review clock are still required.
- Proposed maximum: 96 hours. Proposed review: every 24 hours.
Legal hold
Remedy may be deferred while counsel confirms constraints.
- Receipt, owner, and acknowledgment clock remain mandatory.
- Proposed maximum: 14 days. Proposed review: every 72 hours.
Irreversibility
Final remedy can pause while reversible alternatives are prepared.
- Receipt, owner, and review clock remain mandatory.
- Proposed maximum: 7 days. Proposed review: every 48 hours.
Operational guidance
Minimum artifact requirements
Every exception entry must include these artifacts for auditability.
- Receipt ID and decision payload linked to the person it decided about.
- A named owner, and someone with authority to escalate who can be reached while the exception runs.
- Clock timestamps for acknowledgment, review, and remedy.
- Justification and expiry date for the exception class.
- A count of how often each class is used, sent to whoever owns the rule. An exception used often is evidence that the rule is wrong.
- Receipt payloads conform to the Agent Receipt schema.