History

Kjell Tore Guttormsen 59703699a5 fix(structure): the index resolves a parent naming a segment of its own document K3-21 C. `resolve_structure` asks `_segment_lookup` first for a `parent` edge: `(source_file, segment_id)` -> concept name, keyed off each concept's own frontmatter (`DocumentStructure.declared`, no file read again), so a pointer lands only inside the pointing concept's document -- `p1` exists in every document of a multi-document bundle. A value no segment answers to is a document number and is looked up exactly as before; a pointer naming nothing keeps `UNRESOLVED_MARKER`. The rendering rule is untouched: a resolved relation renders as its subject, so `parent: p1977?` becomes `parent: p1977`. Moved on purpose, each named: both segmented goldens' index files (`examples/ingest-golden-segmented{,-okf-v0-2}/expected-bundle/krav/1-{1,2}/ index.md`), whose declared parents s1 and s2 -> s0 rendered `parent: s0?` while s0 stood in the bundle -- four lines, `?` removed. The four goldens `test_the_four_existing_goldens_are_untouched` guards are not among them. `skills/okf-consume/` regenerated, because the golden's index bytes -- and so its ref -- moved. `test_shell_parent`'s byte test now expects the resolved facet. README and CLAUDE.md no longer say the index renders it unresolved. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-11 13:55:03 +02:00
..
example-payload.json	fix(structure): the index resolves a parent naming a segment of its own document	2026-09-11 13:55:03 +02:00
README.md	feat(consume): parent reaches the reader -- excerpt field, body link, checker rule	2026-09-11 12:36:23 +02:00

Kjell Tore Guttormsen 59703699a5 fix(structure): the index resolves a parent naming a segment of its own document

K3-21 C. `resolve_structure` asks `_segment_lookup` first for a `parent`
edge: `(source_file, segment_id)` -> concept name, keyed off each concept's
own frontmatter (`DocumentStructure.declared`, no file read again), so a
pointer lands only inside the pointing concept's document -- `p1` exists in
every document of a multi-document bundle. A value no segment answers to is a
document number and is looked up exactly as before; a pointer naming nothing
keeps `UNRESOLVED_MARKER`. The rendering rule is untouched: a resolved
relation renders as its subject, so `parent: p1977?` becomes `parent: p1977`.

Moved on purpose, each named: both segmented goldens' index files
(`examples/ingest-golden-segmented{,-okf-v0-2}/expected-bundle/krav/1-{1,2}/
index.md`), whose declared parents s1 and s2 -> s0 rendered `parent: s0?`
while s0 stood in the bundle -- four lines, `?` removed. The four goldens
`test_the_four_existing_goldens_are_untouched` guards are not among them.
`skills/okf-consume/` regenerated, because the golden's index bytes -- and so
its ref -- moved. `test_shell_parent`'s byte test now expects the resolved
facet. README and CLAUDE.md no longer say the index renders it unresolved.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-11 13:55:03 +02:00

example-payload.json

fix(structure): the index resolves a parent naming a segment of its own document

2026-09-11 13:55:03 +02:00

README.md

feat(consume): parent reaches the reader -- excerpt field, body link, checker rule

2026-09-11 12:36:23 +02:00

README.md

References

example-payload.json is a real payload, not an illustration, and ../SKILL.md is the skill generated for the same bundle. Both come from the three-concept golden bundle that ships in this repository, examples/ingest-golden-segmented-okf-v0-2/expected-bundle, so anyone reading this file can regenerate them byte for byte and compare. Neither carries content from any corpus.

Regenerate them from the repository root rather than editing either file, with okf being this checkout's own install (for example .venv/bin/okf):

okf skill examples/ingest-golden-segmented-okf-v0-2/expected-bundle \
  --out skills/okf-consume --force --example-question "Hva sier veiledningen om krav?"
python3 -c 'import os, pathlib; p = pathlib.Path("skills/okf-consume/SKILL.md"); p.write_text(p.read_text(encoding="utf-8").replace(os.path.realpath(".") + "/", ""), encoding="utf-8")'
okf check --skill skills/okf-consume/SKILL.md \
  --payload skills/okf-consume/references/example-payload.json

Why each part is there:

--force: the generator refuses to replace an existing SKILL.md (refused (target_occupied)), because a silent overwrite would destroy a hand-edited copy.
--example-question: without it the question is derived from the bundle's own titles and the payload is a different one. tests/test_okf_consume.py asserts this payload byte for byte against the pre-pass for exactly Hva sier veiledningen om krav?, so the question is part of what the file is.
The python3 line: okf skill writes the bundle root and the skill's own path absolute when --out is not under .claude/skills/, and this directory is not. Shipped as generated, the two commands in SKILL.md would name one checkout on one machine. The line strips that checkout's prefix and nothing else, and a test holds the shipped SKILL.md to the generator's output with exactly that prefix removed.
okf check should report conformant: 17 rules over 3 excerpts and 0 withheld entries, 0 findings and exit 0.

The generated name is b-golden-segmented-okf-v0-2-consume while this directory stays skills/okf-consume/. Claude Code takes a project or personal skill's command from its directory name and uses name as a display label, so a copy placed at .claude/skills/okf-consume/ is still /okf-consume.

The payload is here so that its shape can be read without running anything, and so that a reader can see what the members the contract does not name look like in practice: text and text_sha256 on every excerpt (§ 8 permits additional members; § 1 defines an excerpt as delivered content, and without a body the budget gate would measure a skeleton), rank, bundle_id_inherited, and the raw_bytes/encoding_delta pair that gives the known-positive a second, independent check.