Operation Effect Lifecycle

Operation Effect Lifecycle A lifecycle diagram generated by Archify. 01 / Attempt and effect rail 02 / Uncertain effect + Confirmed not applied / fenced 03 / Outcomes PREPARED · admitted, reserved · Attempt and effect rail · authorized 01 PREPARED admitted, reserved authorized DISPATCHED · committed before call · Attempt and effect rail 02 DISPATCHED committed before call SUCCEEDED · adapter result · Attempt and effect rail 03 SUCCEEDED adapter result CONFIRMED_APPLIED · settled, cost capped · Attempt and effect rail 04 CONFIRMED_APPLIED settled, cost capped Node COMPLETED · checkpoint evidence · Attempt and effect rail · graph 05 Node COMPLETED checkpoint evidence graph UNKNOWN · timeout or lost reply · Uncertain effect · never auto-retried UNKNOWN timeout or lost reply never auto-retried Reconciliation · read-only host lookup · Uncertain effect · authenticated Reconciliation read-only host lookup authenticated NOT_APPLIED · CONFIRMED_NOT_APPLIED · Confirmed not applied / fenced · maxAttempts NOT_APPLIED CONFIRMED_NOT_APPLIED maxAttempts Fenced · old ownership epoch · Confirmed not applied / fenced · recovery Fenced old ownership epoch recovery exception or lost response effect exists effect absent retry, same logical operation recovery bumps epoch Legend start active state waiting decision terminal success failure / exit neutral

Commit Before Effect

  • • DISPATCHED is durable before any adapter is called
  • • Settlement never charges more than the reservation

Uncertainty Is Explicit

  • • A timeout or restart is not proof that an action did not happen
  • • Reconciliation is an authenticated, read-only lookup; UNKNOWN is never retried automatically

Fencing and Retry

  • • Recovery increments the run epoch and returns unresolved attempts without calling adapters
  • • Retry reuses the logical operation only from CONFIRMED_NOT_APPLIED within maxAttempts