Repository navigation
Accept the namespace binding kernel, so P2a is honestly startable - #7545
Merged
Merged
Conversation
…nt' into roadmap/kernel-authority-amendment
#7508 merged the supplied-candidate binding kernel, resolving P2a's implementation dependency — but no RoadmapAcceptanceReceipt existed, so the roadmap still said its own prerequisite was unaccepted. node_is_startable reads exactly that, so P2a was being worked on while not startable under the roadmap's own definition. Two truths for one fact. The criteria digest 2eba4715cdef42eb is the post-#7530 value and was DERIVED BY EXECUTION, not transcribed: #7530 rewrote this node's boundary, red_control and out_of_scope to cut authority from retirement, and roadmap_criteria_digest covers brief + red_control + handback, so any pre-amendment digest is stale by construction. node_criteria_digest was run against the live node on this tree. Proven end-to-end rather than by inspection: namespace-binding-kernel goes 2 -> 0 occurrences in the regenerated ROADMAP.md, which only happens if the receipt matches the node and the node leaves the active set. A wrong digest leaves the row in place. witness_stale_criteria_digest_refuses_acceptance returns true. Also removes dag/tools/kernel_digest_probe.dag, a throwaway probe that the autosave committed while it was being used to compute the digest. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
gunbai-bot
Bot
changed the title
Two conflicts, both in the roadmap carrier. dag/gunbc/roadmap_authority.dag: both sides added a note around scm_prerequisite_acceptance_note — this branch added namespace_binding_kernel_acceptance_note before it, main added scm_p0_acceptance_evidence_note after it. Both kept. Main had ALSO edited scm_prerequisite_acceptance_note itself (to record P0 acceptance and its twenty-two executing journey witnesses), which is why the two sides shared no identical line and a naive union left the row declared twice. Main's newer text is kept and this branch's stale pre-P0 copy deleted — verified by assertion before deleting, not by eye. ROADMAP.md is a generated artifact, so it was regenerated from the authority rather than hand-merged; hand-resolving a generated file makes the committed bytes disagree with their source and detonates on the next .dag PR. Verified after resolution: no conflict markers anywhere in the tree; the kernel node is still absent from ROADMAP.md, so the acceptance receipt remains effective; scm_p0_acceptance_evidence_note is present, so main's work survived; scm_prerequisite_acceptance_note is declared exactly once. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Six commits behind. roadmap_authority.dag auto-merged cleanly this time; only ROADMAP.md conflicted, and it is a generated artifact, so it was regenerated from the authority rather than hand-resolved. Hand-resolving a generated file makes the committed bytes disagree with their source and detonates on the next .dag PR. Verified after: the kernel row stays absent from ROADMAP.md so the acceptance receipt remains effective, and no conflict markers survive. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Status reconciliation, not new work. Operator ruling 2026-08-01.
The gap
#7508 merged the supplied-candidate binding kernel, so
namespace-reference-derived-closure's implementation dependency was resolved. Butnamespace-binding-kernelhad noRoadmapAcceptanceReceipt, so the roadmap still said its own prerequisite was unaccepted:node_is_startablereads exactly that list, so P2a was being actively worked on while not honestly startable under the roadmap's own definition. Two different truths for one fact.The digest is derived, not transcribed
2eba4715cdef42ebis the post-#7530 value. #7530 rewrote this node'sboundary,red_controlandout_of_scopeto cut the kernel's authority from retirement, androadmap_criteria_digestcovers brief + red_control + handback — so any pre-amendment digest is stale by construction.It was obtained by running
node_criteria_digestagainst the live node on this tree, not copied from a prior receipt and not computed by hand. The probe used to compute it is deleted in this PR (the autosave had committed it mid-use).Evidence
Proven end-to-end rather than by inspection:
namespace-binding-kernelgoes 2 → 0 occurrences in the regeneratedROADMAP.md. That transition only happens if the receipt matches the node and the node consequently leavesactive_roadmap_nodes(). A wrong digest leaves the row in place — this is the discriminating observation, not a formatting change.witness_stale_criteria_digest_refuses_acceptancereturnstrue.ROADMAP.mdregenerated from the authority (20/20 lines): the kernel row leaves andnamespace-reference-derived-closuremoves up a level, which is the derived consequence of its parent being accepted.Receipt contents
Red control is
occurrence_binding_resolve_malformed_transport_refuses_holds— the first arm #7530's amended row requires. The sibling arms all execute in the same witness module and were green on the exact-head run that merged #7508: absent vs wrong-role identity distinct, duplicate supplied identity refused, wrong-category excluded, zero/one/two giving unbound/bound/ambiguous, exact declaration identity surviving, canonical fold invoked once.Handback names
dag/std/occurrence_binding_resolve.dag, its witness, and the v1 adapter.namespace_binding_kernel_acceptance_noterecords all of the above on the carrier, including the reason the digest moved.Not in scope
No node is added, no boundary reworded, no implementation touched.