Finalization Stores Closure, Evidence and the Aging Request Atomically

Context

The service must retain evidence for a successful close and record its reporting request, while respecting the approved direction to avoid waiting for reporting.

Decision

The current task combines closure, capture and aging-request acceptance in one transaction. The atomic boundary is retained in this account; the bounded wait is an observed departure from the approved nonwaiting direction.

Alternatives Considered

Request aging only after closure commits. A crash between commits could leave no reporting request unless another durable mechanism records pending work.

Persist a pending request for later fulfillment. This matches the approved nonwaiting direction, but the inspected close has not implemented that mechanism or its requested-or-ready signal.

Consequences

Normal close success retains both evidence and the accepted aging reference. An active aging run can exhaust finalization’s repeat limit and fail the close, releasing only a month without committed recognition. Separate business units share an aging key for the workspace’s calendar month. The task reads other units’ overlapping period state when selecting finalized or reconstructed basis.