AI request lifecycle

The Lifecycle

Transitions Explained

The runtime writes estimated before checking switches and reserving capacity. Successful admission is followed by reserved and dispatched bookkeeping. The loop records a completed or failed result; unmeasured completion briefly passes through pending. Settlement and task totals share a transaction, followed by a separate allowance movement. Exceptions inside the protected block attempt a release, while process death and earlier failures wait for stale-request recovery.

What Cannot Happen

Settled and refused requests cannot undergo another ordinary status transition or settlement. This applies to accounting status, not every metadata field: attempt, capture and recovery-alert writers do not all require an unsettled status.

Concurrency and Timing

Admission, hold recording, request settlement and period movement are separate failure boundaries. Recovery charges stale requests at their estimate after twenty-four hours. A terminal request with incomplete period accounting is excluded from that sweep.