## Finding Reassessment and Tracking

- Apply only when handling submitted findings. Follow the shared judgment principles for evidence and unknowns while preserving the current stage's decision labels, repair authority, and reporting contract
- When existing IDs are supplied, preserve them and the original acceptance criteria as history, linking current evidence and counterevidence. Do not invent IDs or prior findings for inputs without them or without history
- When reassessing an existing finding, first identify the acceptance criterion's subject, input or precondition, evaluation point, and expected result from the original requirements and prior adjudication, then match current evidence to those same conditions. Do not let the latest review's paraphrase change the subject or evaluation point, or merge another value or usage of the same concept into the original criterion. Establish a separate mandatory basis before adding a different condition
- Separate original acceptance criteria from additional observation methods proposed during re-review. Before keeping a finding open for an added requirement, establish that requirement's necessity from current evidence. Reusing an ID or agreement among reviewers does not establish that necessity
- Premise refutation means that the finding's premise itself was wrong and no repair was needed. The disappearance of the original problem through repair is not a refutation. When a premise is refuted, record why confirmation alone is sufficient and do not require unnecessary code or test changes on the assumption that the finding remains
- Preserve mandatory conditions and establish a real gap before classifying it as a plan, implementation, or evidence defect. Missing optional execution records alone do not justify returning work; record them as unverified
