Snapshots and Job Events Supply the Closing Evidence

Context

Reviewers need evidence of what justified closure and who acted. Current storage distributes that evidence across customer records and operational execution history.

Decision

Describe the existing snapshot and run model without claiming record-history capture. The earlier design’s standard-history promise remains a finding for Product to resolve.

Alternatives Considered

Capture Platform record history for close records. The inspected close does not implement it; the sources do not establish a reason to reject capture or its effect on cancellation attribution.

Keep all evidence in job history alone. Customer export withholds those operational tables, so the business request and retained checklist need their own records.

Consequences

The record operation reconstructs evidence from the snapshot and linked runs. Export omits job events but retains run outputs, including some warning and failure data. Each corrected close receives a separate snapshot without overwriting earlier captured evidence.