open/llm-ingestion-okf
1
0
Fork 0
Code Issues Releases 4 Activity

docs: measurement prose names no document by its numbers — green

Browse source 
Section totals, a page count and build sizes identified one reference
document and one generated HTML corpus to anyone who knows them. They are
written as N, M, an offset of N or a share in docstrings, comments, help
text, reports, README, CLAUDE.md and the changelog; no measured relation
changes. Sums that let N be worked back are written in words. The
`okf quality --fasit` bar is 999/1000 (99.9 %), just under the known-good
arm's measured share, and every build measured keeps its verdict.

Red with the local list widened to those numbers: 52 tracked files. Green: 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-09-23 14:51:17 +02:00
commit 81d7194e20
33 changed files with 412 additions and 398 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/plan/okf-assets-section-6-4.md
View file

@ -14,11 +14,11 @@ concepts. So a picture is neither permitted nor forbidden — it is unaddressed,
and a producer that carries one is guessing about where it goes and what a
consumer may assume.
The need is not hypothetical. Measured on a Norwegian reference standard published both as a 701-page
The need is not hypothetical. Measured on a reference standard published both as a long
PDF and as a NISO-STS XML delivery: the process text is carried in full, and 12 `Tabell N-N`
and 9 `Figur N-N` captions stand over nothing, because the publisher ships
those tables as raster images in **both** deliveries. Section 84 says
its classes "are given in table 84-2" and table 84-2 is a JPEG. A bundle
those tables as raster images in **both** deliveries. One section says
its classes "are given in table N-N" and that table is a JPEG. A bundle
built from that document reads as complete and is not.
## The proposed wording