Snapshot versions share a ledger and publish after validation

Context

Staff need to distinguish absent, skipped, failed and published months across applications. Reruns must preserve earlier versions.

Decision

Applications record versioned monthly runs in the shared snapshot ledger, with owner-restricted writes and a final transaction that validates and publishes the new current version.

Alternatives Considered

Keep a separate ledger in each application: Shared operational status and missing-period inspection would need additional aggregation.

Overwrite published periods: Earlier reported figures would no longer have a retained version.

Consequences

Each owner accesses the ledger through its database role. Reruns allocate another version. Large runs may stage committed chunks before the final publication transaction.