Repository navigation
Namespace closure: three prerequisite rows in front of reference-derived-closure - #7773
Merged
Merged
Conversation
…ved-closure namespace-reference-derived-closure carried a six-capability set-difference closing contract in which every row read Unavailable, while the node itself was the only dispatchable thing in the lane -- one startable row standing for three separable pieces of work with different substrates. The cut follows the contract's own triggers, which already record what each capability waits on: namespace-structural-observations 4 caps, P2aStructuralCandidateProducer7515 namespace-cross-file-provenance 1 cap, P2aReferenceDependencyProjection7515 namespace-pool-independence 1 cap, P2aPoolIndependentDependencyProjection7515 The first two are parallel -- no dependency runs between the same-file rules and the cross-file projection. Pool independence depends on cross-file provenance because a differential needs a projector to perturb. No new identity was minted for integration or for the census. namespace-reference-derived-closure keeps its durable identity and now denotes the aggregate handback (its first_slice moved; its boundary, which still covers all six, did not). namespace-ambiguity-discharge keeps its identity and its existing dependency on the closure node. The three new rows are deliberately ExecutionContractUnspecified. Each first_slice names authoring its own closing check as its first act, per v1_lane_binding_survey_note: the contract follows the witness, never precedes it. The derived closing-contract tasks for the two startable rows are the honest fail-closed state, not a gap; pool-independence gets none because it is dependency-held, and could not carry one anyway -- its differential compares an output shape its prerequisite has not yet produced. Also adds roadmap-receipt-continuity (roadmap-runtime, off the namespace spine): a receipt that was valid and is now absent refuses unless an explicit revocation names the exact node, the exact record, a reason and its disposition. Motivated by #7739, where a branch spent real effort reconstructing an acceptance record that already existed because nothing refused when it went missing. Distinct from startable_nodes_missing_closing_contract, which finds nodes that never had a check rather than accepted state that vanished. Evidence, by execution on this tree: - roadmap_authority_test: 42/42 witnesses PASS - generated_artifact_drift_test: 7/7 PASS - ROADMAP.md regenerated via main_wet on dag/tools/generated_artifact_gate.dag; the projection shows reference-derived-closure requiring the two new prerequisites, and derived closing-contract tasks appearing for exactly the two startable unbound rows. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ion/loyal-ram-550
gunbai-bot
Bot
changed the title
briansrls
pushed a commit
that referenced
this pull request
Aug 4, 2026
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Aug 4, 2026
Review 47973 added the authority note to std.occurrence_binding_candidates but the stage0 projection was not regenerated; regen_verify_gate_passes failed on std_occurrence_binding_candidates.rs. Also includes merge of origin/main (#7773 roadmap rows, #7771 accepted-receipt continuity). Co-authored-by: Cursor <cursoragent@cursor.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.
Summary
namespace-structural-observations(N3-A),namespace-cross-file-provenance(N3-B),namespace-pool-independence(N3-C), androadmap-receipt-continuity(GOV).namespace-reference-derived-closureidentity as the aggregate handback andnamespace-ambiguity-dischargeas the census — no new identity minted for either.ExecutionContractUnspecified; eachfirst_slicenames authoring its own closing check, perv1_lane_binding_survey_note(the contract follows the witness, never precedes it).Rationale is in-tree in
namespace_closure_prerequisite_cut_noterather than restated here.Tests
roadmap_authority_test— 42/42 PASSgenerated_artifact_drift_test— 7/7 PASSROADMAP.mdregenerated viamain_wetondag/tools/generated_artifact_gate.dag; re-running after merging auto-heal leaves the tree clean, so the committed projection is canonical.The projection is the discriminating evidence: closure renders
requires all: namespace-structural-observations, namespace-pool-independence, and derived closing-contract tasks appear for exactly the two startable unbound rows, not the dependency-held one.