Month-end aging snapshot run

The Lifecycle

The run model describes planning, durable execution and publication rather than invoice state. Superseded captures retain their original results for historical reads.

Transitions Explained

The transition rows identify the initiating action, eligibility checks, resulting records and responsible caller. They retain the pinned evidence for each path.

What Cannot Happen

The invalid-transition rows describe final-state protection and unsupported paths; command eligibility remains distinct from the declared state vocabulary.

Concurrency and Timing

A workspace and month permit one active capture. Version-aware reads reject cursors invalidated by newer publication. Planning runs every fifteen minutes, dispatch every minute, and initial capture waits two hours after month end. A lost execution without its failure step has no job reconciler.