fix(ms-ai-architect): idx-26j presisert — 80/20-funnet forutsatte en nevner det selv kaller udefinert

To rettelser i bokfoeringen, ingen endring i korpuset.

1. 80/20-PAASTANDEN MOTSA SEG SELV. Entryen sa samtidig at fottekstens referent
er udefinert OG at 80/20 'matcher hverken 10/5 foer eller 12/5 etter' - et
konkret avvik regnet ut fra én ANTATT nevner. Soesterfila teller samme slags
paastand paa en annen partisjon ('15 (8 verified fra MCP, 7 baseline/code
samples)' folder code samples inn paa baseline-siden og teller ikke
listeposisjoner). Omskrevet: defekten er at linja ikke KAN sjekkes, ikke at et
bestemt tall spriker. Ikke 'fiks' prosentene mot en antatt nevner - avgjoer
referenten foerst.

2. 'Status: GA' PAA LINJE 4 ER ADJUDISERT, IKKE OVERSETT. idx-26g advarer neste
leser mot aa triagere denne klassen som sitat-hygiene, og samme streng staar i
fila denne oekten nettopp stemplet. Den er IKKE falsifisert av stempelet: linje 4
ligger i bold-label-headeren over '## Innhold', og filas foerste Confidence-
stempel er seksjons-terminalt paa :59.

MEN det egentlige funnet er stoerre enn begge filene: feltets referent er
udefinert KORPUS-BREDT. Maalt over skills/*/references/ blander '**Status:**' to
vokabularer som svarer paa ulike spoersmaal - dokumentmodenhet (Established
Practice 43, Gjeldende 18, Reference 7, Komplett 2) og produkttilgjengelighet
(GA 252, Preview 2, 'GA - avvikles 31. mars 2029' 2). Korpuset baerer alt
presedensformen for en fil som spenner begge: 'GA / Preview (varies by feature)'
(2 filer). Denne fila spenner Transparency Notes (GA), Model Cards (praksis) og
scorecard-en (public preview) samtidig.

Konsekvens for idx-26g: header-spoersmaalet er ikke fil-lokalt. Aa avgjoere det
én fil om gangen setter konvensjonen for 389 filer ved uhell.

Suite 1047/1047. Koe: 8 aapne / 10 resolved.
This commit is contained in:
Kjell Tore Guttormsen 2026-08-09 10:24:07 +02:00
commit 0470674801
2 changed files with 22 additions and 4 deletions

View file

@ -1472,7 +1472,25 @@ framing of a ratification prompt.
**Booked, not fixed:** `idx-26j` — the same file's footer provenance block, which no entry
has ever measured. `Total MCP calls: 5` enumerates components summing to 6; the line has
no defined referent (original generation run, or current state?); the `80% / 20%` split
matches neither the list's 10/5 before this edit nor its 12/5 after; and this edit itself
introduced a two-dialect compound pair (`model-` on line 101 against the ratified
`modell-` in the rewritten row) that no check can see, because the stamp claims
**cannot be checked at all**, which is the defect rather than any particular mismatch —
read as list positions it fits neither 10/5 before nor 12/5 after, but that reading is an
assumption, and the sibling file counts the same kind of claim on a different partition
(*"15 (8 verified fra MCP, 7 baseline/code samples)"*), so no denominator can be asserted.
This edit also introduced a two-dialect compound pair (`model-` on line 101 against the
ratified `modell-` in the rewritten row) that no check can see, because the stamp claims
verification against source, not orthographic consistency.
**One locator adjudicated out of scope rather than missed.** The header carries
`**Status:** GA` at line 4 — the string idx-26g flags in the sibling as a false status
claim of this same class. It is not falsified by this edit's stamp: line 4 sits in the
bold-label header block above `## Innhold`, and the file's first `Confidence` stamp is
section-terminal at line 59, so no stamp reaches it. The real finding is that the field's
referent is undefined **corpus-wide**. Measured across `skills/*/references/`, `**Status:**`
mixes two vocabularies answering different questions — document maturity (`Established
Practice` 43, `Gjeldende` 18, `Reference` 7, `Komplett` 2) and product availability (`GA`
252, `Preview` 2, `GA — avvikles 31. mars 2029` 2) — and the corpus already carries the
precedent form for a file spanning both: `GA / Preview (varies by feature)`, 2 files. This
file spans Transparency Notes (GA), Model Cards (practice) and the scorecard (public
preview) at once. **So idx-26g's header question is not local to either file — it is a
corpus-wide field-semantics decision, and settling it one file at a time would set the
convention by accident.**