docs(p11): okf 0.8.1 measured - source-quota carries the denominators, one prior constant ranked the price schedule out [skip-docs]
P11 (order 20260910T225652Z), NOK 0, no push. PATH okf is 0.8.1 (uv tool list, __version__, --help flags). src/ untouched. (ix) on 0.8.1 shipped: 629/623/6 and 629/620/9 - PM's predicted denominators, now measured. --no-source-quota alone gives back 629/621/8 and 629/617/12 in both arms; the exact numbers are an interaction with tie-shared-rank (both arms) and stem-prefix (open arm). --title-covered never fires here (byte- identical payload). 0.8.1 with the three new rules off reproduces the 0.7.0 payloads' delivered lists and budgets. P10 section 6 diagnosed: a bisect over okf's own history (known-positive at both ends) puts the price schedule's loss at okf 38104b7, whose only consume code change is DOCUMENT_PRIOR_EXPONENT 1.0 -> 0.5; putting that one constant back in a copy returns the old payload byte for byte. tie-shared-rank is ruled out; known_positive 10349 -> 12563 is a version marker, not the mechanism. On 0.8.1 the schedule is over_budget_after_knapsack, not below_k. okf check on 0.8.1 has 15 rules, not 16: rule 16 (bundle_mismatch) is on okf main 7cca9e0, in no tag. Run from an export of 7cca9e0 the K3-15 pair is rc 1 and the right pair rc 0 - a real cross-corpus mismatch, not an okf defect. Offer rows on four corpora: identifiers unchanged (65/50, 435, 982, 272). The P10 doc gets dated additions in sections 4 and 6; the old sentences stand. Test docstring: +2 lines naming the 0.8.1 rule count, no behaviour change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
d8dadbf236
commit
ce22b0e0e6
3 changed files with 421 additions and 0 deletions
|
|
@ -1,6 +1,8 @@
|
|||
"""Load-bearing gate for order 20260910T051343Z (P10): a delivered excerpt nobody named is NAMED.
|
||||
|
||||
**The measured hole.** P9 ran ``okf check`` (0.7.0, 15 rules) over this repository's payloads and
|
||||
(P11 measured the count again on 0.8.1: still 15 -- the 16th rule, ``bundle_mismatch``, is on okf
|
||||
main ``7cca9e0`` and in no tag yet; ``docs/2026-09-11-p11-okf-081.md`` section 5)
|
||||
got rc 0 on ``payload-n100.json`` and rc 1 on BOTH K2 payloads -- **20 findings, every one of them
|
||||
``excerpt_unnamed``**: "an excerpt a reader cannot name is one an answer cannot cite, whatever its
|
||||
rank (SS 8)". That diagnosis is right and it is not a solution: on po's side the same absence is
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue