Start with one change and the decision it needs. Keep the source request, requirement revision, actual authorship, evidence and open questions together. Identify the person who can validate intent and the authority who can accept the change. In this teaching record, those real owners remain unassigned and human validation is unperformed. The teaching contract and literal expected results were fixed before execution. A repeated key with the same payload must preserve the original reservation. A changed payload must conflict, while a distinct key must create useful work. The selected clock values are supplied inputs, so these checks do not establish a full retention window. On the first attempt, the local handler commits a reservation and returns its identifier. The adapter then deliberately discards that completed result and raises a response-loss exception. The harness retains the handler return, but the caller receives no response. This is a local withholding seam, not an observed network outage. The baseline retry returns the original identifier but commits an extra reservation. Its two response-only checks still pass. The full gate finds five failed checks because it retains exact outcomes and committed state. The later conflict makes no additional write; its state mismatch carries forward the duplicate already created by the retry. The correction removes the extra write from the replay path. In its fresh database, the repeat preserves the original reservation, the conflict leaves state unchanged, and a distinct key creates a new reservation. All sixteen selected full checks pass. This execution does not clean duplicates from an existing database or test concurrent callers. Carry the passing observations and the remaining work into the assurance record. Human intent validation, project authorization and broader retention, transport and storage checks remain open. Evidence review does not approve the product promise. Assign accountable owners, renew affected evidence when its basis changes, and record acceptance separately from merge, deployment and release.