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

docs(cli): the new default's K2 digest, measured on the bundle it produces

Browse source 
The default move landed in the previous commit; this is the number it costs a
consumer, measured rather than predicted. `okf build` with no flag over the
43-document reference corpus now yields 517 concepts in 969 files, content
digest `42c8646d...`, `merged + coded rejections = 43 = N`, 817.6 s. The
delivered 2026-09-03 bundle (629 concepts, 1108 files, `9cd74519...`) is
unchanged on disk and reproducing it needs `--outline-run 0 --no-unit-fold`
AND the stamp it was built with -- "the opt-out flags" alone is true and
incomplete, so the report says both.

README and CLAUDE.md now state which two rules are on, what each opt-out is,
and that the proposer's own defaults did not move. One CLAUDE.md sentence was
false as of the move ("a no-flag build stays byte-identical") and is corrected
in place rather than deleted: adding a flag still leaves the default
byte-identical; moving it does not, which is why it took an operator decision.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-09-08 21:14:51 +02:00
commit efa92ce170
3 changed files with 63 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/2026-09-08-k3-runde3-per-filtype.md
View file

@ -363,6 +363,33 @@ tender PDF is 9 either way, which was the other half of that check.
The default is the operator's decision and it is implemented as given. The
measurement above is the report back, not an argument for reversing it.
### The K2 bundle on the new default, and what `9cd74519…` still names
The injection asks for the K2 digest re-measured on the new default and written
down as the current one. Three bundles were built this session, all from the
same 43-document corpus, all with `--bundle-id k2-trinn1-20260903 --okf-version
0.2` and the **default epoch stamp** (`1970-01-01T00:00:00Z`), which is why
none of them can be compared to the delivered bundle's digest directly:
| build | flags | concepts | files | content digest |
|---|---|---|---|---|
| the delivered bundle, 2026-09-03 | two-script path, `--ingested-at 2026-09-03T00:00:00Z` | 629 | 1108 | `9cd74519…` |
| Arm B control | `--outline-run 0 --no-unit-fold` equivalent | 629 | 1108 | `f09035d9…` |
| the D1 pair's other half | `--keep-table-heading` | 629 | 1108 | `432ca424…` |
| **the new default** | none | **517** | **969** | **`42c8646d…`** |
`merged + coded rejections = 43 = N` on all three, exit 0.
**`9cd74519…` names a bundle, not a configuration.** It is the delivered
2026-09-03 tree and it is unchanged on disk, which is the control this session
re-ran. Reproducing it needs the stamp it was built with as well as the
opt-out flags, so "it now holds only under `--outline-run 0 --no-unit-fold`" is
true and incomplete: it also needs `--ingested-at 2026-09-03T00:00:00Z`. The
digest a consumer should compare against from today is `42c8646d…`, for the
command in the table above, and the 629 → 517 concept move is what a re-run
costs them.
## 9. Tests
`1397 → 1414`. Seventeen new, and which of them were red first is stated rather