From be0847e42fede96da459a5d00a373f57dd3b8afb Mon Sep 17 00:00:00 2001 From: Shubham Date: Tue, 10 Nov 2026 17:39:07 +1300 Subject: [PATCH] A-4: sign my own row Ticks only my row in A-4's ratification table (cve_mapping joining the check vocabulary). Nothing is ratified by this, and nothing changes in code: cve_mapping stays out of pipeline.CHECKS until the table is full. Touches only this row, so it merges in either order with #381, which signs Samika's. --- docs/finding-format.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/finding-format.md b/docs/finding-format.md index 24e90fe..ca60bcb 100644 --- a/docs/finding-format.md +++ b/docs/finding-format.md @@ -495,7 +495,7 @@ somewhere later reports it as agreed, sourced from nothing. |---|---|---| | **Arsh** | Owns `analysis/findings.py`, where the vocabulary is validated, and `pipeline.CHECKS`, which would dispatch it | ⬜ | | **Ankeet** | The AI layer switches on `check`; `ai/explain.py` and `ai/Modelfile` would meet a name they have never seen, and this is the first check whose `found` means "worth checking" rather than "this is wrong" | ⬜ | -| **Shubham** | `policy_compliance` shares the results list, and a new check changes what a scan's totals mean | ⬜ | +| **Shubham** | `policy_compliance` shares the results list, and a new check changes what a scan's totals mean | ✅ | | **Samika** | Wrote it; the dashboard and `analysis/report.py` render by check, and `risk` now carries a severity ceiling keyed on this name | ⬜ | > **NOT RATIFIED — zero of four, as of 8 September.** Merging #304 means the