History

Kjell Tore Guttormsen ab6e24aa22 feat(consume): the payload says when the bundle looks like it does not cover the question C4. `coverage` gains two keys, and every key it had keeps its bytes: - `absent_terms`: the question's words the bundle holds in NO form -- not as written, and not through a relative it uses (`bm25.query_groups`, the same bridge the ranking reads through); - `weak`: true when one such word exists or nothing was delivered. A reading with its rule in the open, never a verdict about the bundle. It is computed for both rankings (`bm25.absent_terms` serves the fusion). The retrieval gate's `marked` -- the one reading both gates share -- reads `weak` beside its own bar, never instead of it; the known-negative that strips the payload's words now strips both readings. Words that only FRAME a question are stopwords in both languages (`how often`, `hvor ofte`, `hva står i`, `what does it say`), and so are the Norwegian function words spelled without their letters (`naar`, `paa`), the way ASCII-only text writes them. Read as topic words they would be "absent" from any collection that never uses them, which is what the synthetic sets showed on three answered questions before the list was extended. The working method says what to do with it, in one sentence each: the skill template's step 3 and the MCP server's instructions (1 253 bytes, under the 2 048 a client keeps) -- rephrase in the bundle's words, and if it stays weak, say the bundle does not cover the question. The search gate's table for this commit is kept in local state. Suite on a clean tree after `git add`: 2397 passed, 2 skipped, 4 xfailed. ruff, ruff format, mypy --strict clean. Retrieval gate unchanged at the rows the previous commit left red. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-21 07:12:43 +02:00
..
example-payload.json	feat(consume): the payload says when the bundle looks like it does not cover the question	2026-09-21 07:12:43 +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 ab6e24aa22 feat(consume): the payload says when the bundle looks like it does not cover the question

C4. `coverage` gains two keys, and every key it had keeps its bytes:

- `absent_terms`: the question's words the bundle holds in NO form -- not as
  written, and not through a relative it uses (`bm25.query_groups`, the same
  bridge the ranking reads through);
- `weak`: true when one such word exists or nothing was delivered.

A reading with its rule in the open, never a verdict about the bundle. It is
computed for both rankings (`bm25.absent_terms` serves the fusion). The
retrieval gate's `marked` -- the one reading both gates share -- reads `weak`
beside its own bar, never instead of it; the known-negative that strips the
payload's words now strips both readings.

Words that only FRAME a question are stopwords in both languages (`how
often`, `hvor ofte`, `hva står i`, `what does it say`), and so are the
Norwegian function words spelled without their letters (`naar`, `paa`), the way
ASCII-only text writes them. Read as topic words they would be "absent" from
any collection that never uses them, which is what the synthetic sets showed
on three answered questions before the list was extended.

The working method says what to do with it, in one sentence each: the skill
template's step 3 and the MCP server's instructions (1 253 bytes, under the
2 048 a client keeps) -- rephrase in the bundle's words, and if it stays weak,
say the bundle does not cover the question.

The search gate's table for this commit is kept in local state.

Suite on a clean tree after `git add`: 2397 passed, 2 skipped, 4 xfailed.
ruff, ruff format, mypy --strict clean. Retrieval gate unchanged at the rows
the previous commit left red.

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

2026-09-21 07:12:43 +02:00

example-payload.json

feat(consume): the payload says when the bundle looks like it does not cover the question

2026-09-21 07:12:43 +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.