How can generated records represent corrections without erasing earlier evidence?

A clinic administrator assembles evidence that access reviews were performed by someone outside the scheduling team. Review REV-0318 cites roster ROS-0204, which places the reviewer in administration. The agent marks the independence requirement as supported.

A workforce coordinator issues ROS-0205 and marks ROS-0204 as superseded. The corrected roster places the reviewer in scheduling for the relevant period. The access review still happened, but its evidence no longer supports the same conclusion about independence. The administrator must reopen that finding and seek an acceptable follow-up review.

A generated release could contain both roster versions, the correction notice, the original assessment and the dependency between the assessment and ROS-0204. A simulated environment could introduce the correction after the agent has assembled its first package.

This teaches dependency-aware revision. The agent should identify which conclusion relied on the changed record, explain the effect and retain the earlier package as history. It should not discard every finding merely because one supporting record was corrected.