docs(ms-ai-architect): R11 §9.5 — fire subtraksjoner ratifisert + anvendt; verifisert skår 1 → 4 av 46 [skip-docs]

docs/r11-pilot-results.md

@@ -657,6 +657,53 @@ so re-derive references after the first write and anchor on
 `file_text_verbatim` — never on the line number, which already differs from
 `real_line` in 9 of 17 records.
 
+### 9.5 Ratified and applied — the first corpus edit
+
+Operator ratification 2026-08-03, applied the same session in `957ebef`.
+**Four subtractions written to three publicly distributed KB files.**
+
+| idx | file | what was deleted | form |
+|---|---|---|---|
+| **17** | `rag-caching-optimization.md` | the three score-threshold bands | as attested, trailing colon **kept** |
+| **19** | `rag-caching-optimization.md` | `- Automatic indexing av vectors` | as attested |
+| **33** | `ai-threat-modeling-stride.md` | `(via Azure Resource Graph)` + the whole Purview bullet | as attested |
+| **14** | `feedback-loops-continuous-improvement.md` | `/ SharePoint` only | **reduced** — `Automatically` kept |
+
+**Held back, and why** — each is a live item, not a rejection:
+
+- **idx 26** — the renumbering artifact (`1,2,3,4,6,7`) is unresolved. Delete-only
+  cannot renumber; accepting the artifact is a judgement not yet made.
+- **idx 27** — cond 3 still `human_must_confirm`; the sweep settled only cond 2.
+- **idx 36** — applying it alone yields a severity table more precise than the
+  prose at 310 that cites it. The companion edit is out of envelope → **G7**.
+- **idx 18** — no reduction exists; the correct fix spans a section and a
+  verification-table row → **G7**.
+
+**idx 19 was promoted by the operator, not by the checker.** §9.3 deliberately
+declined to count it, since its cond 2 stood at `human_must_confirm` and clearing
+it would have meant a checker promoting its own doubt. The ratifier resolved the
+omission question — pre-existing silence in the code sample at 275-292 is not
+made worse by deleting an affirmatively false bullet — and that is the authority
+the gate was waiting for. **Verified score: 1 → 4 of 46**, all four by
+ratification.
+
+**The driver.** `scripts/kb-eval/apply-o2-ratified.mjs` (+ 11 tests). Every string
+comes from the tracked returns, never transcription; the single amendment
+(idx 14) is a derivation that asserts its own effect and aborts on a drifted
+record. Anchoring is on `file_text_verbatim` — which matters concretely here,
+because idx 17 and 19 share a file and the first shifts the second's line
+numbers. The run aborts, writing nothing, on an anchor that is not unique, a
+remainder that is not deletion-only, or a novel word form. Writes are atomic.
+
+**The V1 consequence, predicted in §9.4 and now measured.** `check-o2-returns.mjs`
+reports `machine-clean O2 candidates: 13/17` (was 16/17) with four new V1
+findings — idx 14, 17, 19, 33, each `file_text_verbatim NOT FOUND in the file`.
+This is correct behaviour, not a regression: the returns directory is evidence of
+a **pre-edit** corpus, and V1 asks whether the quoted text is still there. The
+test suite is unaffected (1032/1032) because it drives `checkRow` with a
+synthetic stub. **Any future reading of that CLI's V1 tally must subtract the
+applied rows** — the number is only meaningful against an unedited corpus.
+
 ## Appendix A — the 15 admitted proposals, hand-verified
 
 Every proposal the classifier (§4 + context condition) admitted over the whole