Fingerprint Approval And Counted Delete Confirmation

Context

Approval can arrive from an old page, and hard deletion has no compensating rollback.

Decision and Origin

Interactive approval must echo the saved impact fingerprint within its 24-hour window; deleting also requires the returned count-based phrase. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Approve using only the job identity: The request would not identify the preview being approved.

Confirm deletion with a checkbox: A checkbox does not confirm the counted deletion phrase.

Expire previews with a scheduled sweep: The present implementation checks expiry when an action is attempted rather than sweeping previews.

Consequences

Approval validates the recorded fingerprint; execution rechecks individual record versions and domain rules without recomputing a whole-job preview.

CRM file submissions bypass the interactive preview.

An expired preview can remain displayed as validated until a control action checks it.