Repository navigation
D8 arms: the text cut without word-bound claims, and an attribution instruction (#316, under #305) - #317
Conversation
…ction (#316) Two comparison-only seams for #305's D8, measured apart as a 2 x 2: - whole-entry-text-cut-v2 (`text2`): the text cut that also omits every claim bound to a word meaning (m*, the lexeme_entity_candidate path) as lexeme_claim_excluded, before the quotas, so the freed slot flows down and is refilled as the text cut refills. Coverage names the reason. - voltaire-whole-entry-v7-fixed-lead-cap200-nudge-attrib-v1: nudge-v1's text with one ATTRIBUTION IN REASONS paragraph after the after-lead section, at cap 200 under selection-output-v5. The live cut, the publishing path, configuration and migrations are unchanged; every existing pinned sha holds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The independent review of 427060c found nothing required. Its recommendations, applied: - The refill test counts every offered key once (sorted lists, no duplicates, equal to counts.offered) instead of comparing sets. - The first D8 test adds a live-cut arm, which still offers the word-bound claim and never omits it as lexeme_claim_excluded. - Coverage reads its omission reasons from Packet.omission_reasons/0. - Docs: text2 sends what text sends only where the page's pool offers no word-bound claim (meaning places are ranked by citations); the cut list names text2; the fingerprint rule names D8's arms; the packet moduledoc lists every omission reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
Independent exact-head review of 59733e9Branch Read-only: git and file reads only. No Verdict: nothing REQUIRED. Both changes do what §3a and §3b ask. The live cut, the publishing path, every existing pinned text and sha, config, REQUIREDNone. RECOMMENDEDR1. The compare dry run cannot show what §5 R1 expects to read from it
The earliest-expiry gap predates this PR. Stage 1's R1 asked for the same two observables. The Either:
Tell the executor one more thing either way. The cut omits every word-bound claim in the page's pool, not only those R2. The docs name one route by which
|
D8 under #305 (#316): the two changes to D7's nudge arm, each on its own seam, so the batch can measure them apart as a 2 × 2. Comparison-only. Nothing here touches the live cut, the publishing path, a configuration,
mix.lockor a migration, so it deploys by fast-forward with no restart.What changes
1. The cut
whole-entry-text-cut-v2(Packet,text2inCompare)claimwhose bound meaning is a word (m*) is not offered. These are thelexeme_entity_candidatepath ofLinkedClaims.for_scope/2, where the claim's subject is the lexeme. Sense-boundrefers_toclaims are offered as before.lexeme_claim_excluded, besidetext_cut_excludedincut/4, before the quotas. The claim kind's unused room flows down, and the freed slot is refilled exactly as the text cut refills.whole_entry_cuts/0andomission_reasons/0list the new cut and reason, andCoverage's omission list names the reason so the comparison report counts it rather than calling itunknown.Compare's cut table gains"text2" => "whole-entry-text-cut-v2", anddd.runtime's usage line names it.text_bearing?/1, the quotas,whole-entry-cut-v1, the evidence fingerprint and the publishing path.freeze/2accepts the new packets because their omitted reason is listed.verify/1never reads the cut's name.text2's candidates, fingerprint and prompt equaltext's; only the packet hash differs, throughpolicy.cut.2. The instruction
voltaire-whole-entry-v7-fixed-lead-cap200-nudge-attrib-v1(sha2566938459b2118d8b9670ffa9ede62e4da8e776f408623f280bd89b28408344e1e)Packet.attribution_section/0, sha2565dd2e125…), inserted after the AFTER THE LEAD section and before OUTPUT AND SAFETY. It is built with the same string-replace pattern as the nudge.Packet, and named inWholeEntry's comparison, fixed-lead and cap tables (200). That gives itselection-output-v5byContract's existing raised-cap rule.ac08a3d8….Tests
comparison_instructions_test.exs:compare_test.exs, on the love fixture with a title-match claim added:lexeme_claim_excludedand keeps the sense-bound ones; v1 and the live cut keep both.counts.offered.runtime-packet-v4.parse_arms/1accepts:text2.packet_test.exs:Checks at head
59733e9:mix precommitin a private partition (MIX_TEST_PARTITION=_d8a,MIX_ENV=test DD_NO_OBAN=1): 19 doctests, 3,416 tests, 0 failures. The only warnings are the test build's migration-module redefinitions, which predate this PR.427060c, made six RECOMMENDED points;59733e9applies five of them. The sixth, the dry run's per-page list of excluded claims, is met by the run folder's read-onlyexpiry.exs. The second review, at59733e9, is posted below.Not in this PR
run/d8-<date>/, which is outside the repository.The live cut may one day retire word-bound claims too. That is a publishing-path change, and it waits for a qualifying arm (#316 §10).
Refs #316, #305.
🤖 Generated with Claude Code
Summary by CodeRabbit