Exceptions

Bounded exceptions framework

Bounded exceptions that preserve receipts, owners, and clocks even under fraud, security, or legal holds.

Why exceptions matter

Make universal MUSTs credible

Exceptions only delay specific actions. They never erase receipts, owners, or clocks.

Exception classes

Bounded exceptions with required minimums

Every class defines what is delayed, what remains mandatory, and the maximum duration.

Fraud

Remedy execution may pause while fraud is validated.

  • Receipt, owner assignment, and review clock remain mandatory.
  • Max duration: 72 hours. Review cadence: every 12 hours.

Abuse / safety

Full remediation can pause if immediate harm is likely.

  • Receipt, owner, and acknowledgment clock still required.
  • Max duration: 48 hours. Review cadence: every 8 hours.

Security

Remedy may be staged to preserve forensic integrity.

  • Receipt, owner, and review clock still required.
  • Max duration: 96 hours. Review cadence: every 24 hours.

Irreversibility

Final remedy can pause while reversible alternatives are prepared.

  • Receipt, owner, and review clock remain mandatory.
  • Max duration: 7 days. Review cadence: 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 impacted person.
  • Named owner and escalation authority with on-call coverage.
  • Clock timestamps for acknowledgment, review, and remedy.
  • Justification and expiry date for the exception class.
  • Receipt payloads conform to the Agent Receipt schema.