feat(consume): --follow-parent carries the enclosing section's text, from room the cut left
K3-21 B. The second form of `parent`: `okf consume --follow-parent` (`consume.attach_parent_text`) puts the enclosing concept's text inside an excerpt's `parent`, with that concept's own `sha256` so a claim resting on it is cited as that concept. It runs AFTER the cut, on the room the cut left, in rank order, so the delivered set, its order, the withheld list and the denominators are the same with the flag as without it -- inherited text cannot displace an excerpt, the mechanism a consumer measured when copied-in ancestor text pushed the right section to withheld place 504 and 1 069. A text that does not fit is cut to the longest prefix that does and marked `truncated`; a parent the payload already holds, or one a higher-ranked excerpt already carried, travels once. OFF; the defaults are chosen on the measurement that follows this commit. `delivered_text` is the one normalisation an excerpt's `text` and a parent's share. Contract SS 8 point 6 gains the MAY; the template tells the reader what `text`, `sha256` and `truncated` mean. README and CLAUDE.md name the flag. Moved on purpose: the SS 7.4 known-positive again (14 455 / 14 083 / 372 -> 14 721 / 14 346 / 375), and `skills/okf-consume/` regenerated with it. `tests/test_parent_text.py::test_no_room_means_no_text_and_no_lost_excerpt` changed from its red form: it asked through `build_payload` at `limit == spent`, where the knapsack's 500 B buckets admit nothing at all (`budget_admits_nothing`); it now holds the rule at `attach_parent_text`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
ca83dadf53
commit
839bd61349
8 changed files with 158 additions and 25 deletions
|
|
@ -220,7 +220,10 @@ are permitted; the checker reads only the members this section names.
|
|||
(`parent_unfollowable`) a `parent` that is not both members, that names its
|
||||
own excerpt, or whose `concept_id` is in neither `excerpts` nor `withheld` —
|
||||
together those name every concept the pre-pass considered (§ 5.2), so a
|
||||
pointer outside them names nothing in the bundle.
|
||||
pointer outside them names nothing in the bundle. A pre-pass MAY also carry
|
||||
the enclosing concept's text inside `parent` — `text`, with that concept's
|
||||
own `sha256`, and `truncated` where it was cut to fit — and then only from
|
||||
the room its cut left, so that inherited text never displaces an excerpt.
|
||||
|
||||
## 9. Prohibitions
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue