platform · AVC

Failure is part of the operating model.

Side effects, rollback, operator action and recovery evidence remain explicit.

RecoveryRecoverable
Failure
A bounded workflow stopped before its success criterion was verified.
Rollback
Reversible side effects are inventoried and restored through approved steps.
Human action
Review residual risk and decide whether authority may be restored.
Evidence
Incident identity, step receipts and monitored resolution evidence.
Incident lifecycle

Detect → contain → recover → verify.

Every transition is event-backed and operator-visible.

  1. 01
    Detect

    Correlate failure and health events into an incident identity.

    complete
  2. 02
    Contain

    Bound retries, inventory side effects and open circuits when needed.

    active
  3. 03
    Recover

    Run approved mitigation or rollback steps with receipts.

    queued
  4. 04
    Verify

    Monitor restored behavior and attach resolution evidence.

    queued
Failure model

Failure becomes an incident, not a hidden retry loop.

Events are correlated into incidents with bounded retries, circuit breakers, dead-letter handling and operator-visible state.

Recovery plan

Mitigation steps emit their own evidence.

A recovery plan records what failed, which side effects occurred, what was retried or rolled back and which owner action remains.

Completion

Recovery requires proof, not an agent claim.

Resolved state follows mitigation evidence and monitoring. A cheerful completion message is not, regrettably, a control system.