SUMMARY: In this design framework, the correction radius means the set of dependent records and decisions that must be examined after a source value changes. It is a working concept, not a formal standard or a claim that every copy should be overwritten.
Separate Four Completion Claims
A reviewer accepts a correction. The source record changes. A dependent service receives the new value. The affected decision is reconsidered. These are four different claims, and evidence for one does not automatically establish the others.
The Second Copy illustrates the gap through a fictional transit gate. The central edit succeeds while the enforcement point continues using an earlier version. A status of complete conceals that distinction unless the completion rule specifies the outcome it covers.
Find Decisions, Not Just Copies
A dependency map should distinguish an active input from a historical record. A cached credential may need refreshing. A derived eligibility result may need a new evaluation. An audit entry may need an annotation linking it to the correction, rather than silent replacement.
Ask what each recipient does with the value. A system that merely stores a receipt presents a different question from one that denies access. Prioritize checks according to the consequences of continuing to use the old answer, not simply the number of copies found.
Give the Interval an Owner
When delivery is delayed, identify who follows up and what the participant can expect next. Distinguish a known pending destination from an unknown dependency. Neither should disappear inside a generic success message.
Where an authorized temporary measure exists, record it separately. Temporary access does not prove that the underlying record reached its destination. Conversely, a successful delivery acknowledgement does not prove that a dependent decision was actually recalculated.
Preserve Meaning Without Spreading More Data
A correction check needs enough context to join the original decision, the accepted change, and the resulting action. It does not need unrestricted copies of every document. Use bounded identifiers and existing access controls; avoid distributing personal details merely to demonstrate that a process ran.
Define completion narrowly enough to verify. Name the destinations checked, the outcome observed, and any unresolved destination outside that claim. Use Trace a Record Correction to rehearse the distinction with synthetic records before applying it to real cases.