## REVIEWER GUIDANCE (read this BEFORE concluding)

Past blind-reviewer iterations on this same arc have produced false-positive findings of the form **"X is missing"** when X is actually **conditionally rendered on a non-zero count** (`{% if count %}` template branch). To avoid wasting fix cycles:

- If you observe an "absent" UI element (a filter button, a card section, a pill), GREP THE TEMPLATE for the rendering branch BEFORE declaring it a bug.
- Specifically: `web/templates/_approvals_content.html` and `web/templates/cockpit.html` both gate verdict-related elements on `{% if <something>_count %}`. Empty queues correctly hide them.
- "Section B: GO/NO-GO Decisions" not appearing on `/approvals` is correct empty-state UX when no inception is awaiting decision (current state: 0 — see `fw inception status`). The 9 captured-DEFER inceptions are intentionally parked (commit `aedfa7259`) and surface via `/inception?decision=defer`, NOT `/approvals`.
- "NO-GO filter button" not appearing is correct when `nogo_count == 0`. The button DOES render on `{% if nogo_count %}` (template line 224).

If you flag absence as a bug, your finding MUST cite the line number you grep'd that proves the missing render branch is unconditional.

---

