IC
That is exactly the failure mode an approval gate should defend against. We treat approval as being tied to the reviewed revision and evidence, not as a timeless permit. At decision and delivery time the workflow checks whether the task revision, code lineage, dependency state or test evidence changed. If they drifted, the approval is stale and the changed evidence must be reviewed again. The useful distinction is between “a human approved this snapshot” and “this snapshot is still the one being delivered.”