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>
This commit is contained in:
parent
735468f600
commit
ab6e24aa22
12 changed files with 183 additions and 8 deletions
|
|
@ -827,6 +827,14 @@ the passage that answers, under the nearest heading above it, marked with
|
|||
they widen a signal (`--cost-vocabulary`, `--rarity-weight`) belong to it and
|
||||
are refused without it. The rest of this section describes the fusion.
|
||||
|
||||
**The payload says when the bundle looks like it does not cover a question.**
|
||||
`coverage.absent_terms` lists the question's words the bundle holds in no form
|
||||
— not as written and not through a relative it uses — and `coverage.weak` is
|
||||
true when one such word exists or nothing was delivered. It is a reading with
|
||||
its rule in the open, not a verdict: the reader rephrases in the bundle's own
|
||||
words, and if it stays weak, says the bundle does not cover the question. Words
|
||||
that only frame a question (`how often`, `hva står i`) are not topic words.
|
||||
|
||||
`--cost-vocabulary` is off by default and widens one question class: it lets a
|
||||
declared list of cost/price/quantity terms bridge a question and a document that
|
||||
name money with different words. The gate is the question — one naming no such
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue