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

docs(okf-v0.2): A-E6 does not say WHERE, and that silence is now load-bearing

Browse source 
Upstream §12 puts okf_version in the root index.md's frontmatter;
catalog's own spec says an index.md has no frontmatter and carries the
marker as a body line. A bundle conforming to one is non-conformant
against the other, so the placement A-E6 leaves unstated is no longer
cosmetic. Their gate cannot settle it: the shape regex is unanchored and
matches in both places, so a green TEST B measures the value and never
the placement. D5 stays unfrozen until catalog has verified against
upstream; A-E6 becomes placement-explicit before the pilot receives it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A2aKJxLejT9S8jYwoZ9fut
This commit is contained in:
Kjell Tore Guttormsen 2026-07-26 21:38:46 +02:00
commit 99cf98749f
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/plan/okf-v0.2-alignment.md
View file

@ -683,6 +683,18 @@ output is the baseline. Materialize it twice with the *same* explicit
emitter renders values verbatim, so this is a property of the value we hand
it. Verifying the raw bytes here is part of the expectation.
**What A-E6 does not yet say is WHERE**, and as of 2026-07-26 that silence is
load-bearing rather than cosmetic. Upstream §12 puts `okf_version` in the root
`index.md`'s frontmatter block; catalog's own spec (`:55`, `:95`) says an
`index.md` has no frontmatter and carries the marker as a body line. A bundle
conforming to one is non-conformant against the other. Catalog verifies against
upstream before touching their §6, and D5 is not frozen until they have. Their
gate cannot settle it either way — the shape regex is unanchored and matches in
both places — so a green TEST B measures the value, never the placement. A-E6
becomes placement-explicit before the pilot receives it, whichever way the
choice lands; an expectation that does not state what it expects is the defect
class this very expectation is named after.
**What would surprise us — report immediately:** any diff outside the frontmatter
block (the profile seam leaks); `at` differing from the `ingested_at` they passed
(a wall-clock crept in — a determinism defect); a collision refusal on a target