review-change

To perform an evidence-driven code review, apply a structured review flow to existing test reports and verification artifacts to evaluate correctness, maintainability, and scope. This returns a formal PASS or FAIL decision with documented blocking findings and rationale.

You need a structured change review when implementation and verification evidence already exist and you must determine if the change is ready, blocked, out of scope, or security-sensitive. It enforces a formal pass or fail decision rather than open-ended feedback.

Yes, you can review security triggers using existing verification artifacts by applying a security lens during the read-only evaluation. The review notes whether security sensitivity was applied and returns blocking findings if risks are detected.

You need to provide the ready-to-review change package and its existing verification artifacts, such as documented test reports. The reviewer evaluates this evidence and returns a PASS or FAIL decision with documented rationale and any blocking findings.

Yes, change management review works as a read-only process that relies entirely on existing evidence and validation outputs. It does not generate new test reports but evaluates the provided artifacts to determine readiness and return a pass or fail decision.

A change review returns a FAIL with blocking findings when the provided evidence indicates issues with correctness, maintainability, scope, or security triggers. The review documents the specific rationale for each blocking finding to explain why the change is not ready.