docs(ms-ai-architect): R11 §9.7 — idx 26 lukket ut av G7-koen; tredje defekt utenfor begge ankere

Forste G7-entry reparert. Begge kildesider re-hentet live for skriving, sa
§9.6 ble behandlet som premiss og ikke faktum; begge bekrefter malingen
uavhengig.

To funn verdt a bokfore:

Renummererings-artefakten (1,2,3,4,6,7) som §9.4 og koentryen begge sa
'survives either way' var tvungen KUN inne i delete-only-konvolutten. En
ordinaer Edit renummererer gratis til 1-5. Naer arvet som stale constraint.

En TREDJE defekt la utenfor begge ankere: Confidence-stempelet tolv linjer
under lokator 1 vouchet for den falske lista, og ingen maskinsjekk kunne se
det. Samme klasse som idx 17-regresjonen — en edit kan vaere anker-korrekt og
likevel la en falsk pastand sta der sjekkene ikke nar.

Nabodefekt bokfort som idx-26b framfor a foldes inn i en ratifisert entry.

Ko: 5 apne / 2 resolved. Suite 1047/1047.

[skip-docs]

docs/r11-pilot-results.md

@@ -862,6 +862,45 @@ regression was fixed by changing the colon to a period, making the lead-in a
 complete and independently true sentence that the `**Verified**` stamp correctly
 covers; the corpus was swept for the same defect shape with no other occurrence.
 
+### 9.7 idx 26 closed out of the queue — the first G7 entry repaired
+
+**Both sources re-fetched live before writing, not read off §9.6.** The measurement
+above was made in the same session that booked the entry, so it was treated as a
+premise rather than a fact. `how-to-responsible-ai-scorecard` enumerates the
+segments as summary/model overview, data analysis, model performance, cohorts, top
+important factors, fairness insights, causal insights.
+`concept-responsible-ai-dashboard` lists Error analysis and Counterfactual what-if
+among the dashboard components. Both confirm §9.6 independently.
+
+**Operator ratified form (b): relabel, not removal.** Items 4 and 5 leave the
+numbered scorecard list, which renumbers cleanly to **1–5**. The `1,2,3,4,6,7`
+artifact §9.4 and the queue entry both predicted was forced *only inside the
+delete-only envelope*; an ordinary Edit renumbers for free. Carrying that
+constraint forward would have been inheriting a stale cost. The two capabilities
+survive in a blockquote explicitly marked as dashboard components, so
+source-confirmed information is preserved and the reader is warned off exactly the
+conflation that produced the defect. Locator 2 now reads `fairness insights` alone.
+
+**A third defect sat inside neither anchor.** `**Confidence:** Verified (MCP:
+microsoft-learn)`, twelve lines below locator 1, vouched for the false list. No
+machine check could see it: V1/V2/V2b/V3 are string invariants over deleted text,
+and `check-g7-queue.mjs` tests anchors only. The stamp was kept but dated
+`2026-08-03` to record the re-verification. This is the same class as the idx 17
+regression — **an edit can be anchor-correct and leave a false claim standing
+somewhere the checks do not reach.** Read the neighbourhood, not the operation.
+
+**Booked, not folded in: idx-26b.** The post-edit file sweep found
+`| **Accuracy metrics** | Responsible AI Scorecard: Quantitative analyses |` in the
+same table as locator 2 but outside both anchors. "Quantitative analyses" is not a
+scorecard segment — the source calls it *model performance* — and it is a canonical
+**Model Card** section, which this same file lists as one at line 77. So the defect
+is a cross-attribution between two standards, not loose wording. It was entered as
+its own queue member rather than repaired inside a ratified entry, per gap
+discipline: folding unbooked work into a ratified entry launders it.
+
+**Queue state: 5 open, 2 resolved.** Suite 1047/1047; both idx 26 anchors correctly
+stopped matching, and the entry carries its `resolution`.
+
 ## Appendix A — the 15 admitted proposals, hand-verified
 
 Every proposal the classifier (§4 + context condition) admitted over the whole