open/ms-ai-architect
1
0
Fork 0
Code Issues Releases 1 Activity

feat(ms-ai-architect): #21-#24 ratifisert — og tre av fire loeste seg opp i maalingen

Browse source 
Operatoerratifisering 2026-08-11. Formene er skrevet ÉN gang, i
_meta.ratified_forms; hver av de 17 styrte entriene faar et kort datert
tillegg som peker dit og loefter sperren. To kopier av en policy drifter
fra hverandre, saa formteksten gjentas ikke per entry.

#21 kollapset fra 4 til 1. idx-26y, idx-26af og idx-26ag faller bort fordi
det ankrede uttrykket deres selv er sletteklasse - overclaimet doer MED
slettingen. Maalt foer innsnevringen: alle 13 distinkte URL-er i
microsoft-graph-api-copilot-integration.md er learn.microsoft.com, og
naboene i de to AI Act-filene baerer ingen kvalifikator. Igjen staar
idx-26w: fjern kvalifikatoren, behold tellingen, navngi ALDRI miksen -
aa navngi den krever aa paastaa hvilket verktoey som ga hvilken URL, og
det er samme uverifiserbarhet i ny drakt (idx-26v).

#22 er den eneste virkelig nye formen, og den styrer 14 entries.
Referent-testen per linje: genereringen slettes, artefaktet beholdes.
Etiketten er SELV sletteklasse naar dens egne ord navngir genereringen;
da slettes den med linjene sine og overlevende keep-linjer promoteres.
Etiketten beholdes naar ordene navngir innhold - «Research Coverage» er
den eneste slike blant de 14. ALDRI omdoep: det er derfor idx-26aq sin
rename-hasard forsvinner, overskriften slettes i stedet for aa velge
mellom to lesninger.

#23 og #24 trengte ingen ny form. Maalingen oppl0ste dem: keep-halvdelen
er enten sann og redundant (idx-26ao, 18 gjentatt paa :6 og :356) eller
falsk (idx-26z, 3 mot 5 rader; idx-26ap, 16 mot 8 nummererte kilder).
Der keep-halvdelen er redundant er sletting gratis, der den er falsk er
sletting en korreksjon. Resttilfellet - keep-halvdel baade sann OG unik -
er IKKE ratifisert, fordi det ikke er instansiert.

idx-26ar holdes bevisst UTENFOR. Den ble framlagt som noe som maa avgjoeres
eksplisitt, ikke arves stille, og staar aapen paa den grunnen.

Under skrivingen bar mine egne tillegg defektklassen de beskriver: de to
entriene med to former fikk en peker til _meta.ratified_forms["#22 og #23"],
en noekkel som ikke finnes. Fanget av en sjekk som slaar hver peker opp mot
de faktiske noeklene, og rettet foer commit.

Suite 1052/1052. 17 summaries endret, ingen ankere, ingen status, ingen
andre felt. Ratifisering er ikke anvendelse - alle 17 staar fortsatt aapne.
This commit is contained in:
Kjell Tore Guttormsen 2026-08-11 23:50:06 +02:00
commit 39c947ab26
1 changed files with 25 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

43
scripts/kb-eval/data/g7-review-queue.json
View file

@ -5,7 +5,14 @@
"ratified": "2026-08-03", "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.", "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.", "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" "evidence": "docs/r11-pilot-results.md §9.4, §9.5, §9.6; docs/ref-kb-correctness-program-2026-06.md §8 G7",
"ratified_forms": {
"note": "Forms ratified by the operator over MANY entries at once. Recorded here in ONE copy: two copies of a policy drift apart, and a rule stated only in a per-entry summary cannot be found by a session reading a different entry. Each governed entry carries a short dated pointer to the form that governs it; the form text itself lives only here. Ratification is not application - a governed entry stays `open` until its edit is made.",
"#21": "PROVENANCE QUALIFIER ON A KEEP-CLASS LINE. Ratified 2026-08-11.\nSCOPE FIRST, because the question was raised over four entries and only ONE survived measurement. idx-26y, idx-26af and idx-26ag do NOT fall under this form: in each, the anchored line is itself a call count or a call enumeration, which the idx-26j form already deletes, so the provenance overclaim dies WITH the deletion and needs no separate decision. Measured before the scope was narrowed rather than after: microsoft-graph-api-copilot-integration.md carries 13 distinct URLs and ALL 13 are on learn.microsoft.com, so its keep-class neighbour \"**Total kilder:** 11 MCP-verified URLs\" carries no overclaim at all; the keep-class neighbours in ai-act-annex-iii-checklist.md and ai-act-compliance-guide.md (\"**Total sources referenced:** 8\" and \"16\") carry no provenance qualifier in the first place.\nTHE FORM: where a KEEP-class line (a count of the artifact's own sources or URLs) carries a provenance qualifier that overclaims, DELETE THE QUALIFIER AND KEEP THE COUNT. Do NOT name the actual provenance mix.\nTHE GROUND is idx-26j's ground: naming the mix requires asserting which tool produced which URL, and no artifact in this repo records that. Rewriting \"fra MCP-research\" as \"5 fra MCP-research, 2 fra web\" would replace an unverifiable qualifier with a MORE specific unverifiable claim - the idx-26v hazard, where the repair authors the defect class it closes. Deleting the qualifier removes tokens and adds none, leaving only what the file itself can adjudicate.\nGOVERNS: idx-26w.",
"#22": "WHAT \"DELETE THE LINE\" MEANS FOR BLOCK FORM. Ratified 2026-08-11. The widest form ratified since idx-26j; it governs 14 entries.\nTHE REFERENT TEST, applied line by line inside the block:\n - Referent is THE GENERATION (calls made, calls enumerated, tools used, when the document was generated) -> DELETE. Nothing can adjudicate it. Re-verified 2026-08-11 rather than inherited: the only files under scripts/, docs/, tests/ and hooks/ that mention MCP calls are this queue, r11-footer-class-2026-08-11.json, docs/r11-pilot-results.md and docs/ref-kb-direction-note-2026-06.md - all analysis, none a run record.\n - Referent is THE ARTIFACT (a count of sources, URLs or documents the file itself lists) -> KEEP. It is countable against the file.\nTHE LABEL RULE, which is what the question actually turned on. The label or heading above the block is ITSELF a member of the delete class when its own words name the generation - \"MCP Calls: 6\", \"Total MCP Calls: 4\", \"MCP-kall utfoert\", \"MCP-statistikk\", \"MCP-research metadata\", \"MCP research summary\", \"MCP-soek utfoert\", \"MCP Calls Summary\", \"Verifiseringsmetode\". Delete it together with the lines it labels, and PROMOTE any surviving keep-class line to the enclosing level. The label is KEPT UNCHANGED when its words name content or coverage rather than process - \"Research Coverage\" (idx-26am) is the only such label in the 14.\nNEVER RENAME A LABEL. Renaming authors a new claim (idx-26v). This is not a side condition, it is what makes the form safe - and it is why idx-26aq needs no decision about its parenthetical: \"### MCP-soek (7 unique sources)\" is FALSE read as sources (the block above enumerates 10) and true only read as calls, but the heading is DELETED rather than renamed, so the reading never has to be chosen.\nGENERATION TIMESTAMPS INSIDE THE BLOCK are delete class under the same test (\"**Dato for research:** 2026-06-19\", \"**Research timestamp:** April 2026\", \"**Dato generert:** 2026-02-04\"). One-step consequence of idx-26j's referent, not a new form - the reasoning idx-26u and idx-26ac each recorded and neither applied.\nEXPLICITLY NOT COVERED, and this is a scope decision rather than a judgement on merit: idx-26ar (zero-etl-fabric-patterns.md) carries the enumeration with NO count and sits outside the 58 this question was scoped over. It was put to the operator as requiring an explicit decision rather than silent inheritance, and is left open on that ground - the discipline idx-26j's scope addendum named after booking stopped at 7.\nGOVERNS: idx-26x, idx-26z, idx-26aa, idx-26ac, idx-26ad, idx-26af, idx-26ag, idx-26ai, idx-26aj, idx-26ak, idx-26al, idx-26am, idx-26ao, idx-26aq.",
"#23": "A LINE THAT MIXES THE DELETE CLASS AND THE KEEP CLASS. Ratified 2026-08-11.\nTHE FORM: do NOT split the line. MEASURE the keep-class half against the file first, then DELETE THE WHOLE LINE.\nWHY THAT LOSES NOTHING - measured in both members rather than argued:\n - idx-26ao, genaiops-llm-specific-practices.md:383. \"18 kilder\" is TRUE (18 numbered sources) and restated TWICE more, at :6 in the header block and at :356 in the heading \"### Microsoft Learn-kilder (18 dokumenter)\". Deletion removes nothing the file does not still say.\n - idx-26z, chain-of-thought-prompting.md:500. \"3 unike Microsoft Learn-kilder\" is FALSE - the file's own \"### Microsoft Learn (Verified via MCP)\" table has 5 rows and 5 distinct Learn URLs. \"4 MCP-kall\" is also wrong against 3 enumerated. BOTH numbers in that line are wrong, so splitting it would have preserved a falsehood.\nTHE POINT: the hazard was that deletion takes a true claim with it. MEASUREMENT DISSOLVES THE HAZARD instead of trading it for authoring. Where the keep half is redundant, deletion is free; where it is false, deletion is a correction.\nNOT RATIFIED, BECAUSE NOT INSTANTIATED: the residual case where a keep half is BOTH true AND unique in its file. Neither member is that case. A future member that is must come back as a new question rather than inherit this form.\nGOVERNS: idx-26z, idx-26ao. idx-26ao ALSO falls under #22 - the heading and the three call bullets above its line go in the SAME edit, or the deletion produces the idx-26aq residue.",
"#24": "A DELETE-CLASS COUNT RESTATED IN THE DOCUMENT HEADER BLOCK. Ratified 2026-08-11.\nTHE FORM: delete the whole parenthetical \"(8 MCP-oppslag, 16 kilder)\" at mlops-security-access-control.md:5, leaving \"**Confidence:** HIGH - Basert paa offisiell Microsoft Learn dokumentasjon\".\nTHE MEASUREMENT THAT TURNED A RE-AUTHORING INTO A DELETION: the header was treated as mixed - one delete-class half, one keep-class half - which would have forced a rewrite inside the reference contract's structured header. It is NOT mixed. \"16 kilder\" is FALSE: the file enumerates 8 numbered sources and carries 10 distinct URLs, 9 of them on learn.microsoft.com. No reading yields 16. \"8 MCP-oppslag\" is unverifiable on the idx-26j ground. BOTH halves fail, so there is nothing to preserve and no replacement to write. What remains asserts no count and is grounded.\nZERO WORDS AUTHORED - the header keeps its field name and its claim; only the false and the unverifiable are removed.\nGOVERNS: idx-26ap, whose second locator (the footer \"**MCP Calls:** 8\" at :744) is deleted by the idx-26j form in the same edit."
}
}, },
"entries": [ "entries": [
{ {
@ -404,7 +411,7 @@
"class": "replacement", "class": "replacement",
"status": "open", "status": "open",
"raised": "2026-08-09", "raised": "2026-08-09",
"summary": "Booked while closing idx-26o, from the same what-remains check that produced idx-26t. '**Total sources cited**: 7 unique URLs fra MCP-research' passes as ARITHMETIC and fails as PROVENANCE - measured, not inferred. The count is right: 7 numbered entries, 7 distinct URLs. But only 5 of those URLs are on learn.microsoft.com; source 6 is https://a2a-protocol.org/latest/specification/ and source 7 is https://www.jsonrpc.org/specification. The microsoft-learn MCP server serves learn.microsoft.com and nothing else, so 2 of the 7 cannot have come from MCP research, and the qualifier 'fra MCP-research' overclaims for them. This is the counting class's provenance sibling: the defect is not in the number but in what the number is asserted to be a count OF. The contrast inside the same batch makes the shape visible - idx-26n's line on the neighbouring file names 'MCP-research + tavily-research' and so does cover its non-Learn sources, while this one names MCP alone and does not. NOT REPAIRED: the ratified footer form governs counts and their referent, and it has never been extended to provenance qualifiers - doing so unasked would widen a form that stands in 21 files. Candidate resolutions, neither ratified: name the actual provenance mix, or drop the provenance qualifier and let the line be a pure count. Raised as an open operator question in STATE.", "summary": "Booked while closing idx-26o, from the same what-remains check that produced idx-26t. '**Total sources cited**: 7 unique URLs fra MCP-research' passes as ARITHMETIC and fails as PROVENANCE - measured, not inferred. The count is right: 7 numbered entries, 7 distinct URLs. But only 5 of those URLs are on learn.microsoft.com; source 6 is https://a2a-protocol.org/latest/specification/ and source 7 is https://www.jsonrpc.org/specification. The microsoft-learn MCP server serves learn.microsoft.com and nothing else, so 2 of the 7 cannot have come from MCP research, and the qualifier 'fra MCP-research' overclaims for them. This is the counting class's provenance sibling: the defect is not in the number but in what the number is asserted to be a count OF. The contrast inside the same batch makes the shape visible - idx-26n's line on the neighbouring file names 'MCP-research + tavily-research' and so does cover its non-Learn sources, while this one names MCP alone and does not. NOT REPAIRED: the ratified footer form governs counts and their referent, and it has never been extended to provenance qualifiers - doing so unasked would widen a form that stands in 21 files. Candidate resolutions, neither ratified: name the actual provenance mix, or drop the provenance qualifier and let the line be a pure count. Raised as an open operator question in STATE.\nRATIFIED 2026-08-11 - open question #21 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#21\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. CONSEQUENCE HERE: delete the qualifier only - \"**Total sources cited**: 7 unique URLs fra MCP-research\" becomes \"**Total sources cited**: 7 unique URLs\". The count is verified true (7 numbered entries, 7 distinct URLs) and is untouched. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "footer of this file (last line after the idx-26o deletion); Kilder section sources 1-7, of which 6 (a2a-protocol.org) and 7 (jsonrpc.org) are not learn.microsoft.com; idx-26o resolution; idx-26t (sibling finding, same batch)", "evidence": "footer of this file (last line after the idx-26o deletion); Kilder section sources 1-7, of which 6 (a2a-protocol.org) and 7 (jsonrpc.org) are not learn.microsoft.com; idx-26o resolution; idx-26t (sibling finding, same batch)",
"anchors": [ "anchors": [
"**Total sources cited**: 7 unique URLs fra MCP-research" "**Total sources cited**: 7 unique URLs fra MCP-research"
@ -416,7 +423,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - the block states per-tool counts with NO total, so no internal cross-check exists. MEASURED at :919-:924: a \"**MCP-statistikk:**\" label followed by five bullets - 3 microsoft_docs_search calls, 2 microsoft_docs_fetch calls, 1 microsoft_code_sample_search call, then \"25+ unike Microsoft Learn URLs referert\" and \"15+ PowerShell code samples inkludert\". THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the last two bullets are NOT call counts. The URL bullet is the KEEP class (a source count). The code-samples bullet is neither a call count nor a source-URL count - it is a content inventory, a third category the ratified form has never addressed. Deleting only the three call bullets leaves the \"**MCP-statistikk:**\" label standing over two bullets that are not call statistics, so the label's referent silently changes under the edit - the same referent-drift the ratified form exists to stop. Also worth recording for whoever adjudicates: both survivors are approximations (\"25+\", \"15+\") with no exact referent, so they are not checkable either, but they are outside this class. Candidate scopes, NEITHER ratified: (a) delete the three call bullets and re-label the heading, (b) delete the heading and the three call bullets and re-attach the two survivors. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - the block states per-tool counts with NO total, so no internal cross-check exists. MEASURED at :919-:924: a \"**MCP-statistikk:**\" label followed by five bullets - 3 microsoft_docs_search calls, 2 microsoft_docs_fetch calls, 1 microsoft_code_sample_search call, then \"25+ unike Microsoft Learn URLs referert\" and \"15+ PowerShell code samples inkludert\". THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the last two bullets are NOT call counts. The URL bullet is the KEEP class (a source count). The code-samples bullet is neither a call count nor a source-URL count - it is a content inventory, a third category the ratified form has never addressed. Deleting only the three call bullets leaves the \"**MCP-statistikk:**\" label standing over two bullets that are not call statistics, so the label's referent silently changes under the edit - the same referent-drift the ratified form exists to stop. Also worth recording for whoever adjudicates: both survivors are approximations (\"25+\", \"15+\") with no exact referent, so they are not checkable either, but they are outside this class. Candidate scopes, NEITHER ratified: (a) delete the three call bullets and re-label the heading, (b) delete the heading and the three call bullets and re-attach the two survivors. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: \"**MCP-statistikk:**\" names the generation, so the label goes with the three call bullets. The two survivors (\"25+ unike Microsoft Learn URLs referert\", \"15+ PowerShell code samples inkludert\") are promoted to the enclosing level. No rename. Their being approximations is noted in this entry and is outside this class. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-advisor/references/copilot-extensibility/enterprise-governance-copilot-deployment.md:919-924 (the MCP-statistikk block, file ends at :925); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); idx-26j resolution (ratified form); docs sec. 9.16", "evidence": "skills/ms-ai-advisor/references/copilot-extensibility/enterprise-governance-copilot-deployment.md:919-924 (the MCP-statistikk block, file ends at :925); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); idx-26j resolution (ratified form); docs sec. 9.16",
"anchors": [ "anchors": [
"**MCP-statistikk:**", "**MCP-statistikk:**",
@ -433,7 +440,7 @@
"class": "replacement", "class": "replacement",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: flag provenance_mix, and the ONLY member of all 58 in bucket \"tvetydig\". MEASURED at :544: \"**MCP calls:** 7 (3x docs_search, 2x docs_fetch, 1x code_sample_search, 1x ToolSearch)\". The verdict FLIPS between two defensible readings. Read as \"tool calls of any kind\", 3+2+1+1 = 7 and the line is consistent. Read as \"MCP calls\" - which is what the label says - the microsoft-learn components sum to 6, ToolSearch is not a microsoft-learn MCP tool, and the stated 7 is ONE TOO HIGH. THAT DIRECTION MATTERS BEYOND THIS FILE: sec. 9.16 measured 10 of 11 inconsistent members as stated < sum, and this file under the MCP-only reading is one of only two places in the whole class where the deviation runs the other way. It is part of the evidence that killed \"all deviations run the same way\" as an ABSOLUTE claim - the 91% tendency survives, the absolute does not. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. OPEN QUESTION #21 APPLIES: this is the idx-26w provenance class - the defect is not the number but what the number is asserted to be a count OF. STATE records that all four members of this class (idx-26w plus the three booked here) are to be decided TOGETHER, not one at a time. Neighbour :543 \"**Total kilder:** 11 MCP-verified URLs, 4+ code samples\" is the KEEP class (a source count) and is anchored here so a deletion cannot take it silently.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: flag provenance_mix, and the ONLY member of all 58 in bucket \"tvetydig\". MEASURED at :544: \"**MCP calls:** 7 (3x docs_search, 2x docs_fetch, 1x code_sample_search, 1x ToolSearch)\". The verdict FLIPS between two defensible readings. Read as \"tool calls of any kind\", 3+2+1+1 = 7 and the line is consistent. Read as \"MCP calls\" - which is what the label says - the microsoft-learn components sum to 6, ToolSearch is not a microsoft-learn MCP tool, and the stated 7 is ONE TOO HIGH. THAT DIRECTION MATTERS BEYOND THIS FILE: sec. 9.16 measured 10 of 11 inconsistent members as stated < sum, and this file under the MCP-only reading is one of only two places in the whole class where the deviation runs the other way. It is part of the evidence that killed \"all deviations run the same way\" as an ABSOLUTE claim - the 91% tendency survives, the absolute does not. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. OPEN QUESTION #21 APPLIES: this is the idx-26w provenance class - the defect is not the number but what the number is asserted to be a count OF. STATE records that all four members of this class (idx-26w plus the three booked here) are to be decided TOGETHER, not one at a time. Neighbour :543 \"**Total kilder:** 11 MCP-verified URLs, 4+ code samples\" is the KEEP class (a source count) and is anchored here so a deletion cannot take it silently.\nRATIFIED 2026-08-11 - open question #21 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#21\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. CONSEQUENCE HERE: #21 does NOT apply to this entry. Measured - all 13 distinct URLs in this file are on learn.microsoft.com, so the keep-class neighbour \"**Total kilder:** 11 MCP-verified URLs, 4+ code samples\" carries no overclaim and is untouched. The anchored line \"**MCP calls:** 7 (...)\" is a call count and is deleted by the idx-26j form, which disposes of its ToolSearch provenance problem as a side effect rather than by a decision of its own. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-advisor/references/copilot-extensibility/microsoft-graph-api-copilot-integration.md:543-544 (file ends at :545); dataset r11-footer-class-2026-08-11.json (form=line, b=tvetydig, flags=[provenance_mix]); idx-26w (same provenance class, open); docs sec. 9.16 point 5 (the direction finding)", "evidence": "skills/ms-ai-advisor/references/copilot-extensibility/microsoft-graph-api-copilot-integration.md:543-544 (file ends at :545); dataset r11-footer-class-2026-08-11.json (form=line, b=tvetydig, flags=[provenance_mix]); idx-26w (same provenance class, open); docs sec. 9.16 point 5 (the direction finding)",
"anchors": [ "anchors": [
"**MCP calls:** 7 (3x docs_search, 2x docs_fetch, 1x code_sample_search, 1x ToolSearch)", "**MCP calls:** 7 (3x docs_search, 2x docs_fetch, 1x code_sample_search, 1x ToolSearch)",
@ -446,7 +453,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM plus flag direction_stated_gt_enumerated. Bucket inkonsistent. MEASURED at :494-:500: a \"### MCP-kall utført\" heading, three numbered items (microsoft_docs_search, microsoft_code_sample_search, microsoft_docs_fetch), then \"**Totalt:** 4 MCP-kall, 3 unike Microsoft Learn-kilder.\" THIS IS THE SINGLE COUNTEREXAMPLE IN THE CLASS: stated 4 EXCEEDS the enumerated 3, while all ten other inconsistent members state a total BELOW their sum. sec. 9.16 records it as the finding that falsified \"all deviations run the same way\" as an absolute; the tendency (91%) survives, the absolute does not, and the earlier \"zero the other way\" was an artefact of measuring half the population. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the total line is MIXED. One sentence carries a call count (4 MCP-kall) AND a source count (3 unike Microsoft Learn-kilder). Deleting the line as written would delete a KEEP-class claim along with the call count. Splitting it means AUTHORING a replacement sentence - which is precisely the hazard named in idx-26v, \"the replacement authors the defect class it closes\". Note also that the surviving source count was NOT verified here; this entry books the counting defect, it does not certify that 3 unique Learn sources is true. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM plus flag direction_stated_gt_enumerated. Bucket inkonsistent. MEASURED at :494-:500: a \"### MCP-kall utført\" heading, three numbered items (microsoft_docs_search, microsoft_code_sample_search, microsoft_docs_fetch), then \"**Totalt:** 4 MCP-kall, 3 unike Microsoft Learn-kilder.\" THIS IS THE SINGLE COUNTEREXAMPLE IN THE CLASS: stated 4 EXCEEDS the enumerated 3, while all ten other inconsistent members state a total BELOW their sum. sec. 9.16 records it as the finding that falsified \"all deviations run the same way\" as an absolute; the tendency (91%) survives, the absolute does not, and the earlier \"zero the other way\" was an artefact of measuring half the population. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the total line is MIXED. One sentence carries a call count (4 MCP-kall) AND a source count (3 unike Microsoft Learn-kilder). Deleting the line as written would delete a KEEP-class claim along with the call count. Splitting it means AUTHORING a replacement sentence - which is precisely the hazard named in idx-26v, \"the replacement authors the defect class it closes\". Note also that the surviving source count was NOT verified here; this entry books the counting defect, it does not certify that 3 unique Learn sources is true. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open questions #22 AND #23 are both settled, and this entry is governed by BOTH. The two forms are recorded ONCE each, in _meta.ratified_forms[\"#22\"] and _meta.ratified_forms[\"#23\"] of this queue; neither is restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: both forms apply to one edit. \"### MCP-kall utfoert\" plus the three numbered call items go under #22; the mixed total goes whole under #23, because both of its numbers are false (3 stated against 5 rows in this file's own Verified table, 4 stated against 3 enumerated). Nothing survives the block, so nothing is promoted. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-advisor/references/prompt-engineering/chain-of-thought-prompting.md:494-500 (file ends at :505); dataset r11-footer-class-2026-08-11.json (form=block, b=inkonsistent, flags=[direction_stated_gt_enumerated]); docs sec. 9.16 point 5; idx-26v (replacement-authors-the-defect hazard)", "evidence": "skills/ms-ai-advisor/references/prompt-engineering/chain-of-thought-prompting.md:494-500 (file ends at :505); dataset r11-footer-class-2026-08-11.json (form=block, b=inkonsistent, flags=[direction_stated_gt_enumerated]); docs sec. 9.16 point 5; idx-26v (replacement-authors-the-defect hazard)",
"anchors": [ "anchors": [
"### MCP-kall utført", "### MCP-kall utført",
@ -459,7 +466,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - no total, so nothing to cross-check against. MEASURED at :587-:591: a \"### Verifiseringsmetode\" heading and three bullets - \"**MCP-søk** — 3 søk mot microsoft-learn (2026-02-04)\", \"**Fetch** — 2 fullstendige dokumenter hentet via microsoft_docs_fetch\", and \"**Code samples** — Søk mot microsoft_code_sample_search (ingen direkte treff ...)\". THIS FILE IS PART OF THE EVIDENCE FOR THE FOURTH ESCAPE FORM (sec. 9.16 point 2): the count rides on the ACTION WORD (\"MCP-søk ... 3 søk\"), not on the word \"kall\" or a tool identifier, so sweep A was blind to it and :589 was rescued only by its neighbouring line. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the third bullet records a call WITH NO NUMBER AT ALL. \"Delete the line\" is undefined for a call record that carries no count - it is neither a false number nor a checkable one, and the ratified form was written for a stated count. Candidate scopes, none ratified: delete all three bullets and the heading; delete the two numbered bullets only; or treat the numberless bullet as outside the class. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - no total, so nothing to cross-check against. MEASURED at :587-:591: a \"### Verifiseringsmetode\" heading and three bullets - \"**MCP-søk** — 3 søk mot microsoft-learn (2026-02-04)\", \"**Fetch** — 2 fullstendige dokumenter hentet via microsoft_docs_fetch\", and \"**Code samples** — Søk mot microsoft_code_sample_search (ingen direkte treff ...)\". THIS FILE IS PART OF THE EVIDENCE FOR THE FOURTH ESCAPE FORM (sec. 9.16 point 2): the count rides on the ACTION WORD (\"MCP-søk ... 3 søk\"), not on the word \"kall\" or a tool identifier, so sweep A was blind to it and :589 was rescued only by its neighbouring line. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the third bullet records a call WITH NO NUMBER AT ALL. \"Delete the line\" is undefined for a call record that carries no count - it is neither a false number nor a checkable one, and the ratified form was written for a stated count. Candidate scopes, none ratified: delete all three bullets and the heading; delete the two numbered bullets only; or treat the numberless bullet as outside the class. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: \"### Verifiseringsmetode\" names the generation method, so heading and all three bullets go. No keep-class line stands under it, so nothing is promoted. The neighbouring \"**Dato generert:** 2026-02-04\" is a generation timestamp and is delete class under the same test. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-advisor/references/prompt-engineering/domain-specific-prompt-optimization.md:587-591 (file ends at :603); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); docs sec. 9.16 point 2 (fourth escape form, this file named)", "evidence": "skills/ms-ai-advisor/references/prompt-engineering/domain-specific-prompt-optimization.md:587-591 (file ends at :603); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); docs sec. 9.16 point 2 (fourth escape form, this file named)",
"anchors": [ "anchors": [
"### Verifiseringsmetode", "### Verifiseringsmetode",
@ -486,7 +493,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - per-tool counts with no call total. MEASURED at :932-:937: a \"**MCP-research metadata:**\" label and five bullets - search 4, fetch 3, code_sample 1, then \"**Total sources:** 10\" and \"**Dato for research:** 2026-06-19\". THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the block mixes three categories under one label. The three call bullets are the class. \"**Total sources:** 10\" is the KEEP class. \"**Dato for research:** 2026-06-19\" is a GENERATION TIMESTAMP - a fourth thing. Under the referent ratified on idx-26j (current provenance, one referent for the whole block) a generation-time date falls in the same category as a generation-time call count, which would make its deletion a ONE-STEP CONSEQUENCE OF AN EXISTING RATIFICATION rather than a new form - exactly the reasoning recorded for the file-size line in idx-26u. That consequence is NAMED HERE, NOT APPLIED: extending the form unasked is what idx-26w refused to do, and the same restraint applies. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - per-tool counts with no call total. MEASURED at :932-:937: a \"**MCP-research metadata:**\" label and five bullets - search 4, fetch 3, code_sample 1, then \"**Total sources:** 10\" and \"**Dato for research:** 2026-06-19\". THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the block mixes three categories under one label. The three call bullets are the class. \"**Total sources:** 10\" is the KEEP class. \"**Dato for research:** 2026-06-19\" is a GENERATION TIMESTAMP - a fourth thing. Under the referent ratified on idx-26j (current provenance, one referent for the whole block) a generation-time date falls in the same category as a generation-time call count, which would make its deletion a ONE-STEP CONSEQUENCE OF AN EXISTING RATIFICATION rather than a new form - exactly the reasoning recorded for the file-size line in idx-26u. That consequence is NAMED HERE, NOT APPLIED: extending the form unasked is what idx-26w refused to do, and the same restraint applies. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: \"**MCP-research metadata:**\" names the generation, so label plus the three call bullets plus \"**Dato for research:** 2026-06-19\" all go. \"**Total sources:** 10\" is the sole survivor and is promoted. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-engineering/references/mlops-genaiops/infrastructure-as-code-mlops.md:932-937 (file ends at :949); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); idx-26u (generation-time metadata, same category argument); idx-26j resolution", "evidence": "skills/ms-ai-engineering/references/mlops-genaiops/infrastructure-as-code-mlops.md:932-937 (file ends at :949); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); idx-26u (generation-time metadata, same category argument); idx-26j resolution",
"anchors": [ "anchors": [
"**MCP-research metadata:**", "**MCP-research metadata:**",
@ -502,7 +509,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - no call total. MEASURED at :579-:584: a \"### MCP research summary\" heading and five bullets - \"**Total searches:** 3\", \"**Document fetches:** 2\", \"**Code samples:** 1\", \"**Unique sources:** 7 Microsoft Learn articles\", \"**Research timestamp:** April 2026\". THIS FILE IS THE STRONGEST EVIDENCE FOR THE FOURTH ESCAPE FORM: sec. 9.16 point 2 records that it was invisible IN ITS ENTIRETY to sweeps A and B, because the counting rides on \"Total searches\" - no \"kall\", no tool identifier next to a digit - and it entered the class ONLY through sweep D. A single sweep cannot prove its own completeness; this file is what that costs when it is assumed. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED, AND THIS ONE IS SHARP: the KEEP-class line \"**Unique sources:** 7 Microsoft Learn articles\" sits in the SAME BULLET LIST as the three call lines. Any scope defined at list level - \"delete the MCP research summary block\" - takes a keep-class claim with it. The timestamp bullet raises the same category question as idx-26ac and idx-26u. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - no call total. MEASURED at :579-:584: a \"### MCP research summary\" heading and five bullets - \"**Total searches:** 3\", \"**Document fetches:** 2\", \"**Code samples:** 1\", \"**Unique sources:** 7 Microsoft Learn articles\", \"**Research timestamp:** April 2026\". THIS FILE IS THE STRONGEST EVIDENCE FOR THE FOURTH ESCAPE FORM: sec. 9.16 point 2 records that it was invisible IN ITS ENTIRETY to sweeps A and B, because the counting rides on \"Total searches\" - no \"kall\", no tool identifier next to a digit - and it entered the class ONLY through sweep D. A single sweep cannot prove its own completeness; this file is what that costs when it is assumed. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED, AND THIS ONE IS SHARP: the KEEP-class line \"**Unique sources:** 7 Microsoft Learn articles\" sits in the SAME BULLET LIST as the three call lines. Any scope defined at list level - \"delete the MCP research summary block\" - takes a keep-class claim with it. The timestamp bullet raises the same category question as idx-26ac and idx-26u. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: \"### MCP research summary\" names the generation, so heading plus Total searches, Document fetches, Code samples and Research timestamp all go - the sharp part of this entry, a keep-class line sitting in the SAME bullet list, is resolved by promoting it rather than by scoping at list level. \"**Unique sources:** 7 Microsoft Learn articles\" survives and is promoted. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-engineering/references/mlops-genaiops/model-versioning-registry-management.md:579-584 (file ends at :590); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); docs sec. 9.16 point 2 (this file named as invisible to sweeps A and B); idx-26ac and idx-26u (timestamp category)", "evidence": "skills/ms-ai-engineering/references/mlops-genaiops/model-versioning-registry-management.md:579-584 (file ends at :590); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); docs sec. 9.16 point 2 (this file named as invisible to sweeps A and B); idx-26ac and idx-26u (timestamp category)",
"anchors": [ "anchors": [
"### MCP research summary", "### MCP research summary",
@ -531,7 +538,7 @@
"class": "replacement", "class": "replacement",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM plus flag provenance_mix. Bucket ikke_sjekkbar - no call total. MEASURED at :521-:525: the heading \"### MCP-søk utført 2026-02\" over three bullets - \"microsoft_docs_search: 2 queries\", \"WebSearch: 4 queries\", \"tavily_extract: 5 URLs\". TWO OF THE THREE TOOLS ARE NOT MCP microsoft-learn. The heading asserts MCP provenance for all three, so the overclaim is structural: it is carried by the heading, not by any single bullet, which is a shape idx-26w did not have (there the qualifier sat inside the counted line itself). A second, independent problem: the three bullets do not share a unit - \"queries\" twice and \"URLs\" once - so even summing them is not well defined, and no total is stated. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. OPEN QUESTION #21 APPLIES: this is the idx-26w provenance class - the defect is not the number but what the number is asserted to be a count OF. STATE records that all four members of this class (idx-26w plus the three booked here) are to be decided TOGETHER, not one at a time. Neighbour \"**Total sources referenced:** 8 (5 primary, 3 secondary)\" is the KEEP class and is anchored so it cannot be removed with the block.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM plus flag provenance_mix. Bucket ikke_sjekkbar - no call total. MEASURED at :521-:525: the heading \"### MCP-søk utført 2026-02\" over three bullets - \"microsoft_docs_search: 2 queries\", \"WebSearch: 4 queries\", \"tavily_extract: 5 URLs\". TWO OF THE THREE TOOLS ARE NOT MCP microsoft-learn. The heading asserts MCP provenance for all three, so the overclaim is structural: it is carried by the heading, not by any single bullet, which is a shape idx-26w did not have (there the qualifier sat inside the counted line itself). A second, independent problem: the three bullets do not share a unit - \"queries\" twice and \"URLs\" once - so even summing them is not well defined, and no total is stated. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. OPEN QUESTION #21 APPLIES: this is the idx-26w provenance class - the defect is not the number but what the number is asserted to be a count OF. STATE records that all four members of this class (idx-26w plus the three booked here) are to be decided TOGETHER, not one at a time. Neighbour \"**Total sources referenced:** 8 (5 primary, 3 secondary)\" is the KEEP class and is anchored so it cannot be removed with the block.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: this entry is governed by #22, NOT by #21. \"### MCP-soek utfoert 2026-02\" names the generation and carries the overclaim structurally, so heading and all three bullets go together and the overclaim dies with them - no provenance decision is needed. \"**Total sources referenced:** 8 (5 primary, 3 secondary)\" carries no qualifier, survives, and is promoted. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-governance/references/responsible-ai/ai-act-annex-iii-checklist.md:521-527 (file ends at :534); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[provenance_mix]); idx-26w (same class, open); STATE open question #21", "evidence": "skills/ms-ai-governance/references/responsible-ai/ai-act-annex-iii-checklist.md:521-527 (file ends at :534); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[provenance_mix]); idx-26w (same class, open); STATE open question #21",
"anchors": [ "anchors": [
"### MCP-søk utført 2026-02", "### MCP-søk utført 2026-02",
@ -547,7 +554,7 @@
"class": "replacement", "class": "replacement",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM plus flag provenance_mix. Bucket ikke_sjekkbar - no call total. MEASURED at :732-:735: the label \"**MCP-søk utført 2026-02-03:**\" over three bullets - \"microsoft_docs_search: 3 queries\", \"WebSearch: 2 queries\", \"microsoft_docs_fetch: 3 URLs\". Same structural shape as idx-26af: the MCP claim is carried by the LABEL and one of the three tools (WebSearch) is not MCP microsoft-learn, so the overclaim cannot be repaired by editing any single bullet. Units again differ across bullets (queries, queries, URLs) with no stated total. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. OPEN QUESTION #21 APPLIES: this is the idx-26w provenance class - the defect is not the number but what the number is asserted to be a count OF. STATE records that all four members of this class (idx-26w plus the three booked here) are to be decided TOGETHER, not one at a time. Neighbour \"**Total sources referenced:** 16 (7 primary, 9 secondary/tertiary)\" is the KEEP class and is anchored.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM plus flag provenance_mix. Bucket ikke_sjekkbar - no call total. MEASURED at :732-:735: the label \"**MCP-søk utført 2026-02-03:**\" over three bullets - \"microsoft_docs_search: 3 queries\", \"WebSearch: 2 queries\", \"microsoft_docs_fetch: 3 URLs\". Same structural shape as idx-26af: the MCP claim is carried by the LABEL and one of the three tools (WebSearch) is not MCP microsoft-learn, so the overclaim cannot be repaired by editing any single bullet. Units again differ across bullets (queries, queries, URLs) with no stated total. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. OPEN QUESTION #21 APPLIES: this is the idx-26w provenance class - the defect is not the number but what the number is asserted to be a count OF. STATE records that all four members of this class (idx-26w plus the three booked here) are to be decided TOGETHER, not one at a time. Neighbour \"**Total sources referenced:** 16 (7 primary, 9 secondary/tertiary)\" is the KEEP class and is anchored.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: this entry is governed by #22, NOT by #21. Same shape as idx-26af - \"**MCP-soek utfoert 2026-02-03:**\" names the generation and carries the overclaim, so label and all three bullets go and the overclaim dies with them. \"**Total sources referenced:** 16 (7 primary, 9 secondary/tertiary)\" survives and is promoted. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-governance/references/responsible-ai/ai-act-compliance-guide.md:732-737 (file ends at :744); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[provenance_mix]); idx-26w and idx-26af (same class); STATE open question #21", "evidence": "skills/ms-ai-governance/references/responsible-ai/ai-act-compliance-guide.md:732-737 (file ends at :744); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[provenance_mix]); idx-26w and idx-26af (same class); STATE open question #21",
"anchors": [ "anchors": [
"**MCP-søk utført 2026-02-03:**", "**MCP-søk utført 2026-02-03:**",
@ -575,7 +582,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - per-tool counts with no call total. MEASURED at :458-:463: a \"### MCP Calls Summary\" heading over four bullets - search 3 calls, fetch 2 calls, code_sample 1 call, then \"**Totalt unike URLer:** 6 verified Microsoft Learn articles\". THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the KEEP-class bullet sits inside the same list under a heading that names the whole block \"MCP Calls Summary\", so a heading-level scope removes a source count that is not part of the class - the idx-26ad problem in a second file. NOTED FOR THE ADJUDICATOR, NOT BOOKED: that surviving bullet has a label/value tension of its own - it counts ARTICLES under a URL label, the same shape as idx-26ae and idx-26ah - so deleting the call bullets does not leave a clean block behind. That is a keep-side observation and is deliberately left out of this entry's scope rather than widened into it. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - per-tool counts with no call total. MEASURED at :458-:463: a \"### MCP Calls Summary\" heading over four bullets - search 3 calls, fetch 2 calls, code_sample 1 call, then \"**Totalt unike URLer:** 6 verified Microsoft Learn articles\". THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the KEEP-class bullet sits inside the same list under a heading that names the whole block \"MCP Calls Summary\", so a heading-level scope removes a source count that is not part of the class - the idx-26ad problem in a second file. NOTED FOR THE ADJUDICATOR, NOT BOOKED: that surviving bullet has a label/value tension of its own - it counts ARTICLES under a URL label, the same shape as idx-26ae and idx-26ah - so deleting the call bullets does not leave a clean block behind. That is a keep-side observation and is deliberately left out of this entry's scope rather than widened into it. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: \"### MCP Calls Summary\" names the generation, so heading plus the three call bullets go. \"**Totalt unike URLer:** 6 verified Microsoft Learn articles\" survives and is promoted. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-governance/references/responsible-ai/ai-risk-taxonomy-classification.md:458-463 (file ends at :474); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); idx-26ad (same list-level scope problem); idx-26ae, idx-26ah (label/value shape)", "evidence": "skills/ms-ai-governance/references/responsible-ai/ai-risk-taxonomy-classification.md:458-463 (file ends at :474); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); idx-26ad (same list-level scope problem); idx-26ae, idx-26ah (label/value shape)",
"anchors": [ "anchors": [
"### MCP Calls Summary", "### MCP Calls Summary",
@ -591,7 +598,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket konsistent - MEASURED at :562-:565, \"### MCP Calls: 6\" followed by 3x microsoft_docs_search, 2x microsoft_docs_fetch, 1x microsoft_code_sample_search, and 3+2+1 = 6. Consistency does not save it: the ground is unverifiability. WHAT MAKES THIS ONE STRUCTURALLY DIFFERENT: THE TOTAL IS CARRIED BY A MARKDOWN HEADING, not by a body line. sec. 9.16 records the method finding that a digit-less heading can hide a whole structural form; this is its inverse - a heading that IS the count. \"Delete the line\" therefore means deleting a section heading, and the document structure around it is part of the edit: the block sits between \"---\" separators, and the very next heading \"### Unique Sources: 8 verified Microsoft Learn URLs\" is KEEP class at the SAME level and carries its own count in the same shape. Deleting one heading and keeping its structural twin is a judgement the ratified form does not make. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket konsistent - MEASURED at :562-:565, \"### MCP Calls: 6\" followed by 3x microsoft_docs_search, 2x microsoft_docs_fetch, 1x microsoft_code_sample_search, and 3+2+1 = 6. Consistency does not save it: the ground is unverifiability. WHAT MAKES THIS ONE STRUCTURALLY DIFFERENT: THE TOTAL IS CARRIED BY A MARKDOWN HEADING, not by a body line. sec. 9.16 records the method finding that a digit-less heading can hide a whole structural form; this is its inverse - a heading that IS the count. \"Delete the line\" therefore means deleting a section heading, and the document structure around it is part of the edit: the block sits between \"---\" separators, and the very next heading \"### Unique Sources: 8 verified Microsoft Learn URLs\" is KEEP class at the SAME level and carries its own count in the same shape. Deleting one heading and keeping its structural twin is a judgement the ratified form does not make. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: the heading IS the count, so \"### MCP Calls: 6\" is deleted together with its three bullets - the whole section, not a body line. Its structural twin \"### Unique Sources: 8 verified Microsoft Learn URLs\" is keep class and is untouched. The judgement this entry said the ratified form did not make is now made: the twin survives because its referent is the artifact, not because it looks alike. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-governance/references/responsible-ai/algorithmic-accountability-auditability.md:560-567 (file ends at :572); dataset r11-footer-class-2026-08-11.json (form=block, b=konsistent, flags=[]); docs sec. 9.16 (heading-borne count); idx-26ak (second heading-borne instance)", "evidence": "skills/ms-ai-governance/references/responsible-ai/algorithmic-accountability-auditability.md:560-567 (file ends at :572); dataset r11-footer-class-2026-08-11.json (form=block, b=konsistent, flags=[]); docs sec. 9.16 (heading-borne count); idx-26ak (second heading-borne instance)",
"anchors": [ "anchors": [
"### MCP Calls: 6", "### MCP Calls: 6",
@ -607,7 +614,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket inkonsistent - MEASURED at :774-:777: \"### Total MCP Calls: 4\" followed by microsoft_docs_search 3 queries, microsoft_docs_fetch 2 deep reads, microsoft_code_sample_search 1 query. The components sum to 6 against a stated 4 - the class's dominant direction (stated < sum), which sec. 9.16 measured at 10 of 11. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. STRUCTURALLY this is the second heading-borne total, the same shape as idx-26aj: the number lives in a \"###\" heading, so the edit is a structural one, and the following heading \"### Total Unique URLs: 9\" is KEEP class at the same level with its own two-bullet breakdown (Primary 4 + Secondary 5 = 9, internally consistent). Decide the two heading-borne cases together or the corpus ends up with two different treatments of one shape. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket inkonsistent - MEASURED at :774-:777: \"### Total MCP Calls: 4\" followed by microsoft_docs_search 3 queries, microsoft_docs_fetch 2 deep reads, microsoft_code_sample_search 1 query. The components sum to 6 against a stated 4 - the class's dominant direction (stated < sum), which sec. 9.16 measured at 10 of 11. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. STRUCTURALLY this is the second heading-borne total, the same shape as idx-26aj: the number lives in a \"###\" heading, so the edit is a structural one, and the following heading \"### Total Unique URLs: 9\" is KEEP class at the same level with its own two-bullet breakdown (Primary 4 + Secondary 5 = 9, internally consistent). Decide the two heading-borne cases together or the corpus ends up with two different treatments of one shape. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: identical treatment to idx-26aj, which is why the two were decided together. \"### Total MCP Calls: 4\" and its three bullets go; \"### Total Unique URLs: 9\" and its internally consistent 4+5 breakdown are untouched. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-governance/references/responsible-ai/model-monitoring-drift-detection.md:774-781 (file ends at :782); dataset r11-footer-class-2026-08-11.json (form=block, b=inkonsistent, flags=[]); idx-26aj (same heading-borne shape); docs sec. 9.16 point 5", "evidence": "skills/ms-ai-governance/references/responsible-ai/model-monitoring-drift-detection.md:774-781 (file ends at :782); dataset r11-footer-class-2026-08-11.json (form=block, b=inkonsistent, flags=[]); idx-26aj (same heading-borne shape); docs sec. 9.16 point 5",
"anchors": [ "anchors": [
"### Total MCP Calls: 4", "### Total MCP Calls: 4",
@ -623,7 +630,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM (two lines), no flags. Bucket ikke_sjekkbar - no total. MEASURED at :374-:375: \"**MCP-søk utført:** 3 søk (microsoft-learn)\" and \"**Sider hentet:** 3 full-fetch (concept-responsible-ai, assurance-ai, concept-responsible-ai-dashboard)\". Another fourth-escape-form instance (sec. 9.16 point 2): the count rides on the action word \"MCP-søk utført\", with no \"kall\" and no tool identifier next to a digit. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the block is two lines with no heading and no wrapper, so there is no structural boundary to delete to - \"the line\" is ambiguous between one line and both. The second line differs from every other member of the class in one respect worth recording: IT NAMES THE THREE FETCHED DOCUMENTS, so unlike a bare count it is in principle checkable against the file's own source list. THAT CHECK WAS NOT RUN - it is a different check from the class's internal cross-check, and asserting a verdict without running it is the exact failure this programme keeps catching. Whoever adjudicates should either run it or record that it was not run. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM (two lines), no flags. Bucket ikke_sjekkbar - no total. MEASURED at :374-:375: \"**MCP-søk utført:** 3 søk (microsoft-learn)\" and \"**Sider hentet:** 3 full-fetch (concept-responsible-ai, assurance-ai, concept-responsible-ai-dashboard)\". Another fourth-escape-form instance (sec. 9.16 point 2): the count rides on the action word \"MCP-søk utført\", with no \"kall\" and no tool identifier next to a digit. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the block is two lines with no heading and no wrapper, so there is no structural boundary to delete to - \"the line\" is ambiguous between one line and both. The second line differs from every other member of the class in one respect worth recording: IT NAMES THE THREE FETCHED DOCUMENTS, so unlike a bare count it is in principle checkable against the file's own source list. THAT CHECK WAS NOT RUN - it is a different check from the class's internal cross-check, and asserting a verdict without running it is the exact failure this programme keeps catching. Whoever adjudicates should either run it or record that it was not run. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: both anchored lines are call counts and both go. No keep-class line stands with them, so nothing is promoted. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-governance/references/responsible-ai/responsible-ai-framework-overview.md:373-375 (file ends at :381); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); docs sec. 9.16 point 2", "evidence": "skills/ms-ai-governance/references/responsible-ai/responsible-ai-framework-overview.md:373-375 (file ends at :381); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); docs sec. 9.16 point 2",
"anchors": [ "anchors": [
"**MCP-søk utført:** 3 søk (microsoft-learn)", "**MCP-søk utført:** 3 søk (microsoft-learn)",
@ -636,7 +643,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - no total. MEASURED at :476-:480: a \"**Research Coverage:**\" label over four bullets - \"3 MCP microsoft-learn docs_search calls\", \"3 MCP microsoft-learn docs_fetch calls (full documentation)\", \"9 unique source URLs from Microsoft Learn\", and a \"Coverage:\" bullet that is prose with no number. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the label \"Research Coverage\" spans four different kinds of statement - two call counts (the class), one source count (KEEP), and one prose enumeration of topics. There is no scope that removes the class without either leaving a label over a changed referent or taking non-class content with it. This is the idx-26x problem in a second file, and the two should be decided under one rule rather than file by file. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.", "summary": "Booked 2026-08-11 from the hand-classified footer class measured in docs sec. 9.16: 58 members in 58 files, dataset scripts/kb-eval/data/r11-footer-class-2026-08-11.json (tracked). Operator decision #17 that day split the class - the 42 line-form unflagged members take one class-wide record, and the 16 that carry a decision the ratified form does not settle get their own entry. This is one of those 16. Reason: BLOCK FORM, no flags. Bucket ikke_sjekkbar - no total. MEASURED at :476-:480: a \"**Research Coverage:**\" label over four bullets - \"3 MCP microsoft-learn docs_search calls\", \"3 MCP microsoft-learn docs_fetch calls (full documentation)\", \"9 unique source URLs from Microsoft Learn\", and a \"Coverage:\" bullet that is prose with no number. THE RATIFIED FORM (idx-26j, 2026-08-09): current provenance, one referent for the whole footer block, and the unverifiable MCP-calls line is DELETED rather than corrected to the sum. The ground is UNVERIFIABILITY, not arithmetic - the consistency bucket governs BOOKKEEPING, never whether something is deleted. WHAT IS UNDECIDED: the label \"Research Coverage\" spans four different kinds of statement - two call counts (the class), one source count (KEEP), and one prose enumeration of topics. There is no scope that removes the class without either leaving a label over a changed referent or taking non-class content with it. This is the idx-26x problem in a second file, and the two should be decided under one rule rather than file by file. OPEN QUESTION #22 APPLIES: \"delete the line\" is undefined for block form. This entry is booked, not repaired, and no deletion should be applied to it until the block-form deletion scope is ratified.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: the label is KEPT - \"**Research Coverage:**\" names coverage, not process, and is the only such label among the 14. The two call bullets go; the source-URL bullet and the prose Coverage bullet stay under the unchanged label. No promotion, no rename, no referent drift. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-security/references/ai-security-engineering/prompt-injection-defense-patterns.md:476-480 (file ends at :484); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); idx-26x (same mixed-label shape)", "evidence": "skills/ms-ai-security/references/ai-security-engineering/prompt-injection-defense-patterns.md:476-480 (file ends at :484); dataset r11-footer-class-2026-08-11.json (form=block, b=ikke_sjekkbar, flags=[]); idx-26x (same mixed-label shape)",
"anchors": [ "anchors": [
"**Research Coverage:**", "**Research Coverage:**",
@ -824,7 +831,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "PULLED OUT OF THE CLASS ENTRY idx-26an the same session it was written. It was classified 2026-08-11 as line-form with no flag and no open decision, and a residue screen run before any corpus edit falsified that. MEASURED at :383: \"**Totalt:** 18 kilder, 8 MCP-kall.\" THE LINE IS MIXED. 8 MCP-kall is the delete class - an unverifiable call count. 18 kilder is the KEEP class, and unlike the call count it is CHECKABLE: the file carries a heading \"### Microsoft Learn-kilder (18 dokumenter)\" at :356 over a numbered source list. So \"delete the line\", the ratified form, would delete a verifiable claim along with an unverifiable one. This is the same structural defect as idx-26z, where \"**Totalt:** 4 MCP-kall, 3 unike Microsoft Learn-kilder.\" mixes the two classes in one sentence - and the same hazard idx-26v named: splitting the line means AUTHORING a replacement, which is how a repair authors the defect class it closes. THE RATIFIED FORM (idx-26j, 2026-08-09) still governs the call count; what is undecided is the scope of the edit on a mixed line. Note also :6, \"**Konfidensgrad:** Høy (basert på 18 MCP-kilder fra Microsoft Learn)\" - the header restates the 18. That is the KEEP-class number, so it is not a residue of the call count, but any re-authoring of :383 has to leave :6 coherent with it. Decide together with idx-26z.\nADDENDUM 2026-08-11, later the same day - a dated correction, not a silent reopening (sec. 9.2). THE FORM CLASSIFICATION IS WRONG AND THE ANCHOR SET WAS INCOMPLETE. The dataset records this file as form=line. It is BLOCK FORM. MEASURED at :377-383: the heading \"### MCP-kall utfoert\" (spelled with the o-slash in the file) stands over three tool bullets - docs_search 3 soek, docs_fetch 3 hentinger, code_sample_search 2 soek - which sum to 8 and agree with the stated total. That is the same shape as idx-26z (chain-of-thought-prompting.md), which the SAME dataset classified as block. Identical structure, opposite classification.\nCONSEQUENCE, WHICH IS WHY THIS IS BOOKED RATHER THAN NOTED: applying the ratified \"delete the line\" to :383 alone would leave the heading standing over three call bullets asserting the same unverifiable claim - exactly the idx-26aq residue, this time produced by an edit whose own entry failed to anchor the survivors. The four locators are anchored here rather than described in prose, so none survives only in a summary (the 795d494 failure). THIS ENTRY THEREFORE FALLS UNDER OPEN QUESTION #22 AS WELL AS #23, and #22 must be ratified before any deletion is applied to it.\nHOW IT WAS FOUND, and what the net cost: a sweep of ALL 46 line-form members of the 58 for an enumeration hidden above the anchor (a heading naming MCP/calls/research, or two or more tool-naming list items, within 12 lines above). Three hits, hand-read. Two are net noise - inferencing-optimization-caching.md, where the matched heading is a code-samples section and the anchor already carries its own full breakdown on one line, and ai-impact-assessment-framework.md, where the matched lines carry no per-tool counts. This one is real. One of 46, so the misclassification is isolated, not systemic - measured rather than assumed.\nTHE KEEP-CLASS HALF IS MEASURED, NOT ASSUMED, and it settles the #23 question for this file without authoring anything: \"18 kilder\" is TRUE - the file enumerates 18 numbered sources - and it is restated TWICE more, at :6 in the header block and at :356 in the heading \"### Microsoft Learn-kilder (18 dokumenter)\". Deleting the whole mixed line therefore loses no checkable claim. Contrast idx-26z, where the same measurement falsifies the keep half instead: \"3 unike Microsoft Learn-kilder\" against 5 rows in that file's own Verified table.", "summary": "PULLED OUT OF THE CLASS ENTRY idx-26an the same session it was written. It was classified 2026-08-11 as line-form with no flag and no open decision, and a residue screen run before any corpus edit falsified that. MEASURED at :383: \"**Totalt:** 18 kilder, 8 MCP-kall.\" THE LINE IS MIXED. 8 MCP-kall is the delete class - an unverifiable call count. 18 kilder is the KEEP class, and unlike the call count it is CHECKABLE: the file carries a heading \"### Microsoft Learn-kilder (18 dokumenter)\" at :356 over a numbered source list. So \"delete the line\", the ratified form, would delete a verifiable claim along with an unverifiable one. This is the same structural defect as idx-26z, where \"**Totalt:** 4 MCP-kall, 3 unike Microsoft Learn-kilder.\" mixes the two classes in one sentence - and the same hazard idx-26v named: splitting the line means AUTHORING a replacement, which is how a repair authors the defect class it closes. THE RATIFIED FORM (idx-26j, 2026-08-09) still governs the call count; what is undecided is the scope of the edit on a mixed line. Note also :6, \"**Konfidensgrad:** Høy (basert på 18 MCP-kilder fra Microsoft Learn)\" - the header restates the 18. That is the KEEP-class number, so it is not a residue of the call count, but any re-authoring of :383 has to leave :6 coherent with it. Decide together with idx-26z.\nADDENDUM 2026-08-11, later the same day - a dated correction, not a silent reopening (sec. 9.2). THE FORM CLASSIFICATION IS WRONG AND THE ANCHOR SET WAS INCOMPLETE. The dataset records this file as form=line. It is BLOCK FORM. MEASURED at :377-383: the heading \"### MCP-kall utfoert\" (spelled with the o-slash in the file) stands over three tool bullets - docs_search 3 soek, docs_fetch 3 hentinger, code_sample_search 2 soek - which sum to 8 and agree with the stated total. That is the same shape as idx-26z (chain-of-thought-prompting.md), which the SAME dataset classified as block. Identical structure, opposite classification.\nCONSEQUENCE, WHICH IS WHY THIS IS BOOKED RATHER THAN NOTED: applying the ratified \"delete the line\" to :383 alone would leave the heading standing over three call bullets asserting the same unverifiable claim - exactly the idx-26aq residue, this time produced by an edit whose own entry failed to anchor the survivors. The four locators are anchored here rather than described in prose, so none survives only in a summary (the 795d494 failure). THIS ENTRY THEREFORE FALLS UNDER OPEN QUESTION #22 AS WELL AS #23, and #22 must be ratified before any deletion is applied to it.\nHOW IT WAS FOUND, and what the net cost: a sweep of ALL 46 line-form members of the 58 for an enumeration hidden above the anchor (a heading naming MCP/calls/research, or two or more tool-naming list items, within 12 lines above). Three hits, hand-read. Two are net noise - inferencing-optimization-caching.md, where the matched heading is a code-samples section and the anchor already carries its own full breakdown on one line, and ai-impact-assessment-framework.md, where the matched lines carry no per-tool counts. This one is real. One of 46, so the misclassification is isolated, not systemic - measured rather than assumed.\nTHE KEEP-CLASS HALF IS MEASURED, NOT ASSUMED, and it settles the #23 question for this file without authoring anything: \"18 kilder\" is TRUE - the file enumerates 18 numbered sources - and it is restated TWICE more, at :6 in the header block and at :356 in the heading \"### Microsoft Learn-kilder (18 dokumenter)\". Deleting the whole mixed line therefore loses no checkable claim. Contrast idx-26z, where the same measurement falsifies the keep half instead: \"3 unike Microsoft Learn-kilder\" against 5 rows in that file's own Verified table.\nRATIFIED 2026-08-11 - open questions #22 AND #23 are both settled, and this entry is governed by BOTH. The two forms are recorded ONCE each, in _meta.ratified_forms[\"#22\"] and _meta.ratified_forms[\"#23\"] of this queue; neither is restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: both forms apply to ONE edit, and splitting them across two would reproduce the idx-26aq residue this entry exists to record. \"### MCP-kall utfoert\" plus the three tool bullets go under #22; \"**Totalt:** 18 kilder, 8 MCP-kall.\" goes whole under #23, because the 18 is true and restated at :6 and :356. Nothing is promoted; the header at :6 is left exactly as it is, since 18 is keep class there too. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-engineering/references/mlops-genaiops/genaiops-llm-specific-practices.md:383 (the mixed total), :356 (the 18-source heading and numbered list), :6 (header restating 18); dataset r11-footer-class-2026-08-11.json (classified form=line, flags=[] - the gap this entry records); idx-26z (same mix), idx-26v (replacement-authors-the-defect hazard)", "evidence": "skills/ms-ai-engineering/references/mlops-genaiops/genaiops-llm-specific-practices.md:383 (the mixed total), :356 (the 18-source heading and numbered list), :6 (header restating 18); dataset r11-footer-class-2026-08-11.json (classified form=line, flags=[] - the gap this entry records); idx-26z (same mix), idx-26v (replacement-authors-the-defect hazard)",
"anchors": [ "anchors": [
"**Totalt:** 18 kilder, 8 MCP-kall.", "**Totalt:** 18 kilder, 8 MCP-kall.",
@ -842,7 +849,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "PULLED OUT OF THE CLASS ENTRY idx-26an the same session it was written. It was classified 2026-08-11 as line-form with no flag and no open decision, and a residue screen run before any corpus edit falsified that. MEASURED: the footer at :744 states \"**MCP Calls:** 8 (microsoft-learn docs search + fetch, code samples)\", and the DOCUMENT HEADER at :5 restates the same unverifiable count - \"**Confidence:** HIGH — Basert på offisiell Microsoft Learn dokumentasjon (8 MCP-oppslag, 16 kilder)\". Deleting the footer line under the ratified form would leave the number alive in the file's own header block. That is the residue class G7 exists for, and it is the idx-26ab situation in a second file - except that here the survivor sits in the reference contract's bold-label header rather than in body prose, so the second edit touches the file's structured metadata and cannot be a bare line deletion. The header line also carries \"16 kilder\", a source count and therefore KEEP class, in the same sentence - so the second locator is itself mixed and needs re-authoring rather than removal. THE RATIFIED FORM (idx-26j, 2026-08-09) governs the call count in both places; what is undecided is how the header line is re-authored without asserting something new. NOT REPAIRED HERE. The 2026-08-11 hand classification applied prose_repeat to one file only and missed this one; the gap is recorded rather than quietly patched, and the header block of all 58 members was then swept for the same shape - it returned this file and genaiops-llm-specific-practices.md and nothing else.", "summary": "PULLED OUT OF THE CLASS ENTRY idx-26an the same session it was written. It was classified 2026-08-11 as line-form with no flag and no open decision, and a residue screen run before any corpus edit falsified that. MEASURED: the footer at :744 states \"**MCP Calls:** 8 (microsoft-learn docs search + fetch, code samples)\", and the DOCUMENT HEADER at :5 restates the same unverifiable count - \"**Confidence:** HIGH — Basert på offisiell Microsoft Learn dokumentasjon (8 MCP-oppslag, 16 kilder)\". Deleting the footer line under the ratified form would leave the number alive in the file's own header block. That is the residue class G7 exists for, and it is the idx-26ab situation in a second file - except that here the survivor sits in the reference contract's bold-label header rather than in body prose, so the second edit touches the file's structured metadata and cannot be a bare line deletion. The header line also carries \"16 kilder\", a source count and therefore KEEP class, in the same sentence - so the second locator is itself mixed and needs re-authoring rather than removal. THE RATIFIED FORM (idx-26j, 2026-08-09) governs the call count in both places; what is undecided is how the header line is re-authored without asserting something new. NOT REPAIRED HERE. The 2026-08-11 hand classification applied prose_repeat to one file only and missed this one; the gap is recorded rather than quietly patched, and the header block of all 58 members was then swept for the same shape - it returned this file and genaiops-llm-specific-practices.md and nothing else.\nRATIFIED 2026-08-11 - open question #24 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#24\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. CONSEQUENCE HERE: both locators go in one edit. The footer \"**MCP Calls:** 8 (...)\" at :744 is deleted by the idx-26j form; the header parenthetical \"(8 MCP-oppslag, 16 kilder)\" at :5 is deleted whole, because 16 is false against 8 enumerated sources and 8 MCP-oppslag is unverifiable. The header line keeps its field name and its remaining claim. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-engineering/references/mlops-genaiops/mlops-security-access-control.md:744 (footer count) and :5 (header restating 8 MCP-oppslag alongside 16 kilder); dataset r11-footer-class-2026-08-11.json (classified form=line, flags=[] - the gap this entry records); idx-26ab (prose-repeat precedent); memory: KB reference contract uses a bold-label header", "evidence": "skills/ms-ai-engineering/references/mlops-genaiops/mlops-security-access-control.md:744 (footer count) and :5 (header restating 8 MCP-oppslag alongside 16 kilder); dataset r11-footer-class-2026-08-11.json (classified form=line, flags=[] - the gap this entry records); idx-26ab (prose-repeat precedent); memory: KB reference contract uses a bold-label header",
"anchors": [ "anchors": [
"**MCP Calls:** 8 (microsoft-learn docs search + fetch, code samples)", "**MCP Calls:** 8 (microsoft-learn docs search + fetch, code samples)",
@ -855,7 +862,7 @@
"class": "multi-locator", "class": "multi-locator",
"status": "open", "status": "open",
"raised": "2026-08-11", "raised": "2026-08-11",
"summary": "SURFACED BY APPLYING idx-26an, in the per-file residue search AFTER the edit rather than before it. Deleting the footer line \"**Total MCP calls:** 6\" at :396 was correct under the ratified form and it removed a contradiction, but it left the same unverifiable claim standing ten lines above, in a form no line-based screen enumerates: seven MCP calls listed one per line at :388-394, under a heading that carries the count itself.\nTWO DEFECTS, NOT ONE, and they need separate decisions.\n(a) THE ENUMERATION IS THE SAME UNVERIFIABLE CLASS AS THE DELETED TOTAL. The ratified ground for deletion is unverifiability - no artifact in the repo records MCP calls per file - and that ground applies with MORE force to a list asserting seven specific calls with specific query strings than to a bare number. The deletion did not narrow the claim; it removed the summary of it and left the detail.\n(b) THE HEADING REFERENT IS MISLABELLED, and the two readings disagree. Measured: the source block directly above is numbered 1..10 with no gaps, and \"**Unique URLs:** 10\" at :396 is therefore enumerable and TRUE - keep class, untouched. So \"(7 unique sources)\" is FALSE read as sources, since there are 10, and true only read as calls, since there are 7 bullets. Rewriting the parenthetical means authoring a new claim, which is the idx-26v hazard, so it is not a free rename.\nHEADING-BORNE, SO IT JOINS OPEN QUESTION #22 beside idx-26aj and idx-26ak rather than this file line-form. Same shape as idx-26ak: heading carrying the total, per-tool bullets beneath, a sibling keep-class count alongside. Deciding this one alone would decide #22 by precedent for the other two, so decide the three together.\nCORRECTION TO A RESOLVED ENTRY, written into idx-26j as a dated addendum in the same pass rather than left standing: idx-26j put this file :396 in its \"not checkable\" bucket, defined as a total with no per-tool numbers to sum. That is falsified - the per-tool numbers exist, they are just ten lines up and past a heading. The arithmetic test WAS applicable here, and it fails: 6 stated against 7 enumerated. The other three in that bucket were re-checked against HEAD before this was written and all three hold (multi-turn-conversation-management.md:683 and ai-services-networking-security.md:620 name tools without numbers; adaptive-cards-copilot-responses.md:517 is the mirror case, per-tool numbers with no total). One of four wrong, not four of four - the bucket is dented, not void.\nPOPULATION MEASURED BEFORE BOOKING: 5 files of 389 carry an enumerated MCP-call list; 1 is a false positive, 3 are already booked (idx-26z, idx-26ai, idx-26ak), and this is the only unbooked one. The form is small and now fully enumerated, not an open-ended sweep.", "summary": "SURFACED BY APPLYING idx-26an, in the per-file residue search AFTER the edit rather than before it. Deleting the footer line \"**Total MCP calls:** 6\" at :396 was correct under the ratified form and it removed a contradiction, but it left the same unverifiable claim standing ten lines above, in a form no line-based screen enumerates: seven MCP calls listed one per line at :388-394, under a heading that carries the count itself.\nTWO DEFECTS, NOT ONE, and they need separate decisions.\n(a) THE ENUMERATION IS THE SAME UNVERIFIABLE CLASS AS THE DELETED TOTAL. The ratified ground for deletion is unverifiability - no artifact in the repo records MCP calls per file - and that ground applies with MORE force to a list asserting seven specific calls with specific query strings than to a bare number. The deletion did not narrow the claim; it removed the summary of it and left the detail.\n(b) THE HEADING REFERENT IS MISLABELLED, and the two readings disagree. Measured: the source block directly above is numbered 1..10 with no gaps, and \"**Unique URLs:** 10\" at :396 is therefore enumerable and TRUE - keep class, untouched. So \"(7 unique sources)\" is FALSE read as sources, since there are 10, and true only read as calls, since there are 7 bullets. Rewriting the parenthetical means authoring a new claim, which is the idx-26v hazard, so it is not a free rename.\nHEADING-BORNE, SO IT JOINS OPEN QUESTION #22 beside idx-26aj and idx-26ak rather than this file line-form. Same shape as idx-26ak: heading carrying the total, per-tool bullets beneath, a sibling keep-class count alongside. Deciding this one alone would decide #22 by precedent for the other two, so decide the three together.\nCORRECTION TO A RESOLVED ENTRY, written into idx-26j as a dated addendum in the same pass rather than left standing: idx-26j put this file :396 in its \"not checkable\" bucket, defined as a total with no per-tool numbers to sum. That is falsified - the per-tool numbers exist, they are just ten lines up and past a heading. The arithmetic test WAS applicable here, and it fails: 6 stated against 7 enumerated. The other three in that bucket were re-checked against HEAD before this was written and all three hold (multi-turn-conversation-management.md:683 and ai-services-networking-security.md:620 name tools without numbers; adaptive-cards-copilot-responses.md:517 is the mirror case, per-tool numbers with no total). One of four wrong, not four of four - the bucket is dented, not void.\nPOPULATION MEASURED BEFORE BOOKING: 5 files of 389 carry an enumerated MCP-call list; 1 is a false positive, 3 are already booked (idx-26z, idx-26ai, idx-26ak), and this is the only unbooked one. The form is small and now fully enumerated, not an open-ended sweep.\nRATIFIED 2026-08-11 - open question #22 is settled. The governing form is recorded ONCE, in _meta.ratified_forms[\"#22\"] of this queue; it is deliberately not restated here, because two copies of a policy drift apart. Any sentence above saying no deletion should be applied until the block-form deletion scope is ratified is hereby LIFTED. CONSEQUENCE HERE: \"### MCP-soek (7 unique sources)\" is heading-borne and names the generation, so it is deleted together with the seven enumerated calls at :388-394. The rename question raised in defect (b) therefore never has to be answered - the mislabelled parenthetical dies with the heading rather than being rewritten. \"**Unique URLs:** 10\" is keep class, verified enumerable against a 1..10 source block, and is untouched. NOT YET APPLIED: ratification and application are separate acts, and this entry stays open until its edit is made and verified.",
"evidence": "skills/ms-ai-engineering/references/azure-ai-services/ai-services-cost-optimization.md:386-396 (file ends at :397); numbered source block at :331-384 enumerates 1..10; idx-26an resolution (residue sweep, 2026-08-11); idx-26aj and idx-26ak (same heading-borne shape, open question #22); idx-26j resolution and its 2026-08-11 addendum (the falsified not-checkable classification); dataset r11-footer-class-2026-08-11.json", "evidence": "skills/ms-ai-engineering/references/azure-ai-services/ai-services-cost-optimization.md:386-396 (file ends at :397); numbered source block at :331-384 enumerates 1..10; idx-26an resolution (residue sweep, 2026-08-11); idx-26aj and idx-26ak (same heading-borne shape, open question #22); idx-26j resolution and its 2026-08-11 addendum (the falsified not-checkable classification); dataset r11-footer-class-2026-08-11.json",
"anchors": [ "anchors": [
"### MCP-søk (7 unique sources)", "### MCP-søk (7 unique sources)",