Capture and publish the month-end aging snapshot
What It Does
Historical aging uses durable planning and publication around a fixed knowledge cutoff. Failed attempts preserve current publication; single-transaction rollback does not prove chunk cleanup.
The Flow
The numbered hops identify the participating services, synchronization boundary and evidence. Branch conditions in the frontmatter explain where preparation, completion and recovery diverge.
When Something Fails
Each hop records its rollback, retry or compensation boundary and the result visible to callers or operators. External outcomes can remain unresolved after local preparation commits; the listed recovery behavior defines what remains pending.
Open Design Questions
Establish chunk-failure cleanup and recovery of a lost execution before depending on automatic historical capture recovery.