Quality Assurance

Use this capability to judge whether a change has been adequately verified before merge. This is the reviewer's lens — flag missing evidence and link to the developer-facing rule rather than re-deriving it.

The severity labels used throughout (Critical, Major, Minor) are owned by the project's review severity model; consult it for each tier's definition, fixed floors, and verdict mapping.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Verification Evidence

See verification-evidence.md for:

• Commands run, exit status, and relevant output
• The evidence-adequacy decision flow from changed surface to covered-or-flag
• Whether a result was ever capable of coming out differently, and the fixture and harness failures that make a green or red check carry no information
• Manual checks matched to changed output surfaces
• Skipped required checks and residual risk
• Second-pass verification after fixing Critical or Major findings