Repository navigation
Conversation
…arrier The three g1-cited-symbol discriminating controls were modelled as DOCUMENTS. They lived in gunbc.doc_graph_roots as HandAuthoredDocBind rows homed at docs/probes/g1-cited-symbol-control-*.md with PlanHasNoRetirement, and document production carried a slug-matched predicate to subtract them again. The 2026-08-24 measurement bankruptcy (d3bebd0) deleted docs/probes wholesale, so from that day three rows declared a home that does not exist, kept alive by the exemption written to work around them. They are machine discriminators for v2.lens.cited_symbol_resolution, so that is where they now live, as a typed control carrier with one variant per refusal arm (operator ruling 2026-08-25). The new carrier lands before the old rows leave, in one change: no dual-authority interval, and the evidence executes through the new home before the old one disappears. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
… the only inhabitant of Every remaining `home: ProbeDoc` bind in gunbc.doc_graph_roots named a file under docs/probes that the 2026-08-24 measurement bankruptcy (d3bebd0) deleted. Not most of them -- all sixteen, with no survivor. A bind whose document does not exist is not a root. build_doc_graph_report admits an extra root only if it is present in the doc universe and counts what it admitted; doc_graph_registered_plan_roots_all_admitted pins admitted == passed. So these rows made that witness RED, and it was invisible only because doc_reachability_witness_test declares ReadsLiveTree and the floor declines it before the fold -- a live red held out of view by the decline mechanism. The rows are deleted, and the DocHome axis is deleted with them: with ProbeDoc uninhabitable, the variant is dead scaffolding that would let the next author bind a document into a bankrupted directory. Keeping it as the sole surviving variant was not the alternative, since a single-variant coproduct is a type alias whose variant name is never exported. No document is restored. No cited .dag work is deleted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…leted probe bind The outside-index roster is a literal list beside the bind population rather than a projection of it, so deleting the claude paired-entitlement probe bind left two exemption rows naming references no bind carries -- and the partition identity that proves no authored work falls out of every bucket went red by exactly two. The red is the mechanism working; the repair is to delete the exemptions with the population they exempted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…nsumed evidence The earlier commits on this branch deleted the DocHome coproduct along with the sixteen orphan ProbeDoc binds, on the argument that a variant nothing can inhabit is dead scaffolding. That argument was sound about the population as it stood and wrong about the population as it is: the bankruptcy principle is that UNCONSUMED TRANSCRIPTION disappears while CONSUMED EVIDENCE stays attached to its consumer, and the directory a document sits in is not the authority on which of the two it is -- the exact consumer relation is. docs/probes/leading_minus_continuation_silently_truncates_2026-08-23.md is cited by extdeps.cpu_attachment.lotes_azifa072 as its parser-defect receipt (measured: exactly one consumer, tree-wide). It is being re-bound in a follow-up. Deleting the axis here and restoring it one change later is work authored to be thrown away, and it would have put a permanence claim in the carrier note that was false before the week ended. The sixteen bind deletions and the two orphaned exemptions are unchanged; the red this PR closes is closed by those, not by the axis. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Two documents survived the bankruptcy unbound, and their dispositions are opposite because the bankruptcy principle is not 'everything under docs/probes disappears' -- it is that unconsumed transcription disappears while consumed evidence stays attached to its consumer. The directory is not the authority on which one a file is; the exact consumer relation is. BOUND: leading_minus_continuation_silently_truncates_2026-08-23.md. Measured tree-wide, it has exactly one consumer -- extdeps.cpu_attachment.lotes_azifa072 cites it as 'Receipt and reduced cases' for the leading-minus continuation truncation its arithmetic-consistency function tripped over. The bind names that function, and carries a real retirement condition rather than PlanHasNoRetirement: a Markdown file is not the permanent terminal form of a parser guarantee. DELETED: heads_reading_of_the_grammar_2026-08-24.md. No citation, no bind, no executing consumer, authored after the cut. Minting a bind for it purely to green the orphan wall would fabricate a consumer -- the same fabrication as deleting the cited one, pointed the other way. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…grows by review 55729 caught the half of the rename that stops at the file boundary: the FrozenPathDeferral roster for the long cited-symbol witness file still named cited_symbol_planted_doc_graph_controls_all_refuse and cited_symbol_enrolled_population_refusal_proves_gate_not_vacuous, neither of which exists after this PR -- a StaleFrozenPathDeferral, which is the DESIGN section 3 stale-citation class living inside the very roster whose identity join exists to catch it. The prose in ci_layer_roots naming the old function in its --functions CSV is fixed with it. DECLARED RATHER THAN SLIPPED IN: this grows the frozen roster from 16 rows to 18. The module's own note says the population is frozen as-is and that a new witness under an offline home should not be authored there at all. These two are not new coverage arriving in the long lane -- they are the identity join and the arm agreement that together replace the discriminating power of the row being renamed, in the file that already owns it. Splitting them across homes would put the cheap structural half behind the lens's whole decl_facts import closure. If the operator would rather see the identity join in the fast lane, it moves without touching the arm check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
review 55732: the WitnessExclusionRow reason in gunbc.ci_layer_roots prints a claim_batch recipe whose --functions CSV still named both renamed witnesses, so an operator copy-pasting it hit unknown-function refusals on two rows. The freeze roster was updated in lockstep and this recipe was not -- one carrier of the same fact repaired, another left stale, which is the DESIGN section 3 class this PR is otherwise about. The recipe now lists all eighteen enrolled witnesses, matching the freeze roster exactly, and the prose count moves from sixteen to eighteen with it. My earlier commit touched only the timing parenthetical in this same string and missed the CSV a few hundred characters later in the same line -- a reminder that a long single-line prose row hides its own contents from the person editing it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
review 55731: this PR takes the outside-index roster from four rows to two, and three sentences in gunbc.doc_graph_roots plus one in the lens still asserted four -- the lens whose subject is stale citations landing with a stale numeric citation in its own prose. The doc_graph_roots sentences are corrected to two. The lens note is reworded to name the ROSTER as the authority on the count rather than transcribing a number at all, because the number is exactly the thing that just rotted. The one surviving 'four' is the deliberate historical clause recording what the population was until today. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Closing: this branch is not a deliverable. It is a throwaway merge of current main into the tip of the #9181 -> #9183 -> #9186 chain, pushed only so a remote runner could measure whether that chain still holds once main's other 20 commits are in the tree — a question the branch-only greens could not answer, since they were measured on a base 20 commits behind. No PR in the chain was mutated to do it. The branch will be deleted once the measurement returns; the result goes in #9183 and #9186. — sent from clever-bear-323 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-opened by session-dashboard for session
clever-bear-323.Pushing to
tmp-postmerge-probeadvances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan