Start with a privacy decision whose identity, eligibility, exceptions, retention and destination scope have already been resolved. In this fictional scenario, approval is assumed only for teaching. Profiles and analytics are the two live destinations. Each begins with a synthetic target row and an unrelated control row. Real privacy approval was not performed. With failure injected before the analytics deletion, the defective handler returns complete. Profiles no longer contains the target, but analytics still does. Independent queries read the full subject and value rows from each named live connection. The baseline gate rejects that false completion. The unrelated subject's full row remains in both stores. The corrected handler keeps the failed attempt unresolved and names analytics as unavailable. The recovery retry removes the remaining live target. Repeating that completed request preserves both live row sets and the completion result. Attempt metadata intentionally changes from two to three, so the whole snapshots are not identical. A separate, deliberately wrong reporting adapter swaps the destination statuses after a real corrected call. The aggregate still says unresolved, and the independently read rows still match. The exact named snapshot fails. This designed control tests whether the result stays attached to the right destination; it is not another discovered product defect. The harness actually restores the earlier analytics backup. The target returns while cached request state still says complete. Explicit reconciliation reopens the request without increasing attempts; a further deletion removes the restored live row. The backup still contains the target and control before cleanup. No automatic restore monitor or backup erasure was demonstrated. For your own system, copy the free record and name the decision owner, destinations, implementation revision and required observations. Preserve failures and separate a new replay from historical evidence. That work is proposed. This campaign did not test crash recovery, concurrent writers, real recipients or deadlines, and it does not establish legal compliance.