Batch Lifecycle

The Lifecycle

This diagram describes ordinary collections. Fiscal accounting writes system collections directly as Posted and restores them through its separate reopening path. Lower-level creation also supports Archived.

Transitions Explained

The transition rows specify commands, generation outcomes and retirement, including their distinct guards and side effects. Scheduled close retains the schedule whose run is completing; it does not use the same schedule-removal behavior as manual close. Attention effects depend on the deployment switch.

What Cannot Happen

The invalid rows describe refused commands rather than assuming every stored state has a native producer. Carried states remain accepted input to selected recovery paths. The deletion service has a broader status boundary than the ordinary action menu.

Concurrency and Timing

Posting is transient within the native accounting transaction, so another reader does not observe that intermediate state. Stale-row thresholds remain relevant to migrated or otherwise retained rows. Job state and batch state must be read separately when settlement fails.