Kjell Tore Guttormsen
59c6c280b1
Operatør-ratifisert 2026-08-03. G7 var gapet for korreksjoner som er RIKTIGE men større enn O2-konvolutten (én lokator + kun-sletting). Uten eier falt de stille ut: O2-triagen avviser dem, O3 dekker dem ikke, og review-sporet hadde ingen inngangskø. Formvalget ble tatt på §9.6-målingen, ikke på preferanse: - 2 av 4 anvendte subtraksjoner etterlot en rest -> rester er delete-only- konvoluttens NORMALE biprodukt, ikke et unntak. - 2 av 5 medlemmer (idx 17, 33) er ERSTATNINGER, ikke fler-lokator. En delete-orientert O4-klasse med egen retur-kontrakt ville ikke fikset dem — altså feil dimensjonert mot evidensen. Køen absorberer begge klasser. Artefakter (TDD, test-først): - data/g7-review-queue.json — 6 entries, tracked - lib/g7-queue.mjs — validateQueue, lukkede vokabular - check-g7-queue.mjs — exit 1 ved drift eller skjemafeil - tests/kb-eval/test-g7-queue.test.mjs — 15 tester Kontrakten: ankere er ORDRETTE strenger, aldri linjenummer (line != real_line i 9 av 17 R11-records). En åpen entry hvis anker slutter å matche gir anchor_drift og exit 1 — den kan ikke falle stille ut, som er hele hensikten. En resolved entry MÅ føre resolution, ellers er "resolved" ikke til å skille fra "stille droppet". Ingenting i køen er maskin-anvendbart per definisjon. Innhold: 5 åpne (26, 27, 33, 36, 18), 1 lukket (17). idx 27 kom hit ved å falle ut av O2 på cond 3; idx 26 ved operatørens avvisning av delvis fiks. Suite 1047/1047. [skip-docs]
86 lines
6.9 KiB
JSON
86 lines
6.9 KiB
JSON
{
|
|
"_meta": {
|
|
"gap": "G7",
|
|
"form": "(b) named queue into the human review phase",
|
|
"ratified": "2026-08-03",
|
|
"rationale": "Measured in R11 §9.6: 2 of the 4 subtractions applied in 957ebef left a residue, so residues are the normal by-product of a delete-only envelope rather than an exception. Two of the members are replacements, not multi-locator cases, which a deletion-oriented O4 class would not have fixed. A queue absorbs both classes; an O4 return contract would have been mis-sized against the evidence.",
|
|
"contract": "Anchors are verbatim strings, never line numbers (line ≠ real_line in 9 of 17 R11 records). An open entry whose anchor no longer occurs in its file is drift, and check-g7-queue.mjs fails rather than passing it silently. Nothing in this queue is machine-appliable by definition — every entry is outside the O2 envelope. Resolution is a human review act.",
|
|
"evidence": "docs/r11-pilot-results.md §9.4, §9.5, §9.6; docs/ref-kb-correctness-program-2026-06.md §8 G7"
|
|
},
|
|
"entries": [
|
|
{
|
|
"id": "idx-17",
|
|
"file": "skills/ms-ai-engineering/references/rag-architecture/rag-caching-optimization.md",
|
|
"class": "replacement",
|
|
"status": "resolved",
|
|
"raised": "2026-08-03",
|
|
"summary": "The idx 17 subtraction (957ebef) deleted the three score-threshold bands but left the lead-in ending in a colon, promising an enumeration that no longer existed, immediately followed by a **Verified** stamp. The subtraction was correct; the paragraph it left was not. V1/V2/V2b/V3 are string invariants over deleted text and cannot see document coherence, so the machine could not have caught it.",
|
|
"evidence": "docs/r11-pilot-results.md §9.6",
|
|
"anchors": [],
|
|
"resolution": "Operator-ratified 2026-08-03: colon changed to a period, making the lead-in a complete and independently true sentence that the **Verified** stamp correctly covers. Corpus swept for the same defect shape (bold lead-in ending in colon, blank line, **Verified**) — no other occurrence."
|
|
},
|
|
{
|
|
"id": "idx-33",
|
|
"file": "skills/ms-ai-security/references/ai-security-engineering/ai-threat-modeling-stride.md",
|
|
"class": "replacement",
|
|
"status": "open",
|
|
"raised": "2026-08-03",
|
|
"summary": "The idx 33 subtraction removed AI asset inventory via Azure Resource Graph and the Purview Insider Risk Management bullet from an unsupported Defender for Cloud AISPM attribution. Correct — but the same capabilities survive in this file under Cloud Adoption Framework Secure AI attribution, stamped 'Verified MCP 2026-04', and are asserted in four other corpus files. The edit's benefit is corpus-wide smaller than the single line suggested. Whether the CAF attribution is itself supported has not been checked.",
|
|
"evidence": "docs/r11-pilot-results.md §9.5 (cross-corpus check), §9.6",
|
|
"anchors": [
|
|
"Oppdatert 2026-04: inkluderer nå AI asset inventory via Azure Resource Graph"
|
|
]
|
|
},
|
|
{
|
|
"id": "idx-26",
|
|
"file": "skills/ms-ai-governance/references/responsible-ai/transparency-documentation-standards.md",
|
|
"class": "multi-locator",
|
|
"status": "open",
|
|
"raised": "2026-08-03",
|
|
"summary": "The Responsible AI Scorecard component list names Error analysis (item 4) and Counterfactual analysis (item 5). Both were measured false against first-party docs 2026-08-03: the canonical scorecard segments are summary/model overview, data analysis, model performance, cohorts, top important factors, fairness insights and causal insights; Error analysis and Counterfactual analysis are Responsible AI *dashboard* components. The delete-only reduction could only remove item 5, because line 300 asserts Error analysis as scorecard content too — so a partial fix would have left a known-false claim standing while introducing a renumbering artifact (1,2,3,4,6,7). Operator declined the partial fix 2026-08-03 and sent the whole case here. Correct repair spans both locators.",
|
|
"evidence": "docs/r11-pilot-results.md §9.6; https://learn.microsoft.com/azure/machine-learning/how-to-responsible-ai-scorecard",
|
|
"anchors": [
|
|
"4. **Error analysis**: Error rates per cohort, confusion matrices",
|
|
"| **Risk assessment** | Responsible AI Scorecard: Error analysis, fairness assessment |"
|
|
]
|
|
},
|
|
{
|
|
"id": "idx-27",
|
|
"file": "skills/ms-ai-governance/references/responsible-ai/transparency-documentation-standards.md",
|
|
"class": "replacement",
|
|
"status": "open",
|
|
"raised": "2026-08-03",
|
|
"summary": "Failed out of O2 on cond 3 (§9.6): the cited source DOES establish the mechanism — faqs-generative-orchestration states 'Makers can require user confirmation before executing tools that modify data' — so deleting the Plugin-actions row would destroy source-confirmed information. The defect is modality, not fabrication: the file presents confirmation prompts as a built-in disclosure, whereas the source makes them maker-configured. The Chat-interface row in the same table is imprecise for the same reason: the FAQ documents a default transparency message ('Just so you are aware, I sometimes use AI to answer your questions.'), not a 'Powered by AI' badge. Repair is a replacement, outside the delete-only envelope.",
|
|
"evidence": "docs/r11-pilot-results.md §9.6; https://learn.microsoft.com/microsoft-copilot-studio/faqs-generative-orchestration",
|
|
"anchors": [
|
|
"| **Plugin actions** | Confirmation prompts før sensitive actions (send email, delete file) |",
|
|
"| **Chat interface** | \"Powered by AI\" badge i chat window |"
|
|
]
|
|
},
|
|
{
|
|
"id": "idx-36",
|
|
"file": "skills/ms-ai-security/references/ai-security-engineering/ai-threat-modeling-stride.md",
|
|
"class": "multi-locator",
|
|
"status": "open",
|
|
"raised": "2026-08-03",
|
|
"summary": "Applying idx 36 alone yields a severity table more precise than the prose that cites it, so a companion edit is required for the prose to match the narrowed table. Held back from 957ebef as out of envelope.",
|
|
"evidence": "docs/r11-pilot-results.md §9.4, §9.5",
|
|
"anchors": [
|
|
"Øker severity bar; krever mer robust adversarial defenses"
|
|
]
|
|
},
|
|
{
|
|
"id": "idx-18",
|
|
"file": "skills/ms-ai-engineering/references/rag-architecture/rag-caching-optimization.md",
|
|
"class": "multi-locator",
|
|
"status": "open",
|
|
"raised": "2026-08-03",
|
|
"summary": "No reduction exists. The surviving claim is a whole titled section on Azure AI Search built-in caching plus a **Verified** row in the verification table, so no deletion confined to a single locator can repair the file. This is the member that most clearly motivated G7.",
|
|
"evidence": "docs/r11-pilot-results.md §9.3, §9.4",
|
|
"anchors": [
|
|
"**Automatic Caching Behavior:**",
|
|
"| Azure AI Search caching | **Verified** | Microsoft Learn docs (4, 6) |"
|
|
]
|
|
}
|
|
]
|
|
}
|