Not every finding is a defect: quasi-static signals, proven protocols, and crossings that cannot occur all need a documented way to be accepted. The waiver policy is that way — a narrow, evidence-backed, expiring permission for a specific finding. This topic defines what may be waived, what the waiver must contain, who reviews it, and the anti-patterns that reviews exist to catch.
Lesson | After it you can... |
|---|---|
Separate legitimate waiver classes from design defects. | |
Assemble the evidence a waiver needs, using the template. | |
Route a waiver through review, scope it, and expire it on change. | |
Recognise blanket, cosmetic, undocumented, and copy-forward waivers. |
A narrow, evidence-backed, expiring permission for a specific finding — not a fix, not a dismissal, and not transferable to any other finding.