diff --git a/docs/finding-format.md b/docs/finding-format.md index b7ff118..b877be0 100644 --- a/docs/finding-format.md +++ b/docs/finding-format.md @@ -495,11 +495,14 @@ 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 — one of four, as of 5 October** (zero of four from 8 -> September to 5 October). Merging #304 means the +> **NOT RATIFIED until the table above is full.** The table is the record, +> so this note no longer repeats its count (#466): it read zero of four from +> 8 September, and one of four from 5 October until a second row was ticked, +> which is how a counted note goes stale -- the same fix as A-3's key set in +> #449. Merging #304 means the > code is worth having and is safe to sit inert. It does **not** mean the > amendment is agreed, and **`cve_mapping` must not be added to > `pipeline.CHECKS` until this table is full.**