Frozen Input And Transactional Receipts

Context

Repeated delivery must be safe without changing the set of records approved for processing.

Decision and Origin

Submission fixes the input, and each committed item receives a receipt in the same transaction as its domain change. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Read the selection again during execution: A later selection can differ from the previewed input.

Depend on exactly-once queue delivery: Delivery can repeat; duplicate protection must be committed with the change.

Consequences

An existing receipt prevents reapplying that item within the same job.

Rollback planning relies on receipts and domain history.

Evidence retention is decided but its general purge is not implemented.