Bind the namespace reference-derived closure contract

[briansrls]

Summary

Binds the previously unspecified execution contract for namespace-reference-derived-closure, stopping the roadmap belt from treating the derived closing row as undispatchable.

The new substrate contract transcribes the node's six clauses into a closed capability frontier. It consumes the merged P1 supplied-candidate binding kernel for reference outcomes, keeps unavailable production behavior typed, and derives completion from the missing-capability set. The bound acceptance witness is deliberately red and enrolled as QuarantineProbeExpectRed; controlled fixtures cannot satisfy production acceptance.

Six-clause handback

• (a) same-file earlier neighbour: contract controls green; production admission red with P2aStructuralCandidateProducer7515.
• (b) sibling decision branch excluded: contract controls green; production admission red with P2aStructuralCandidateProducer7515.
• (c) later declaration excluded: contract controls green; production admission red with P2aStructuralCandidateProducer7515.
• (d) distinct same-spelled declarations stay ambiguous: contract controls green; production admission red with P2aStructuralCandidateProducer7515.
• (e) repeated mentions collapse to one dependency: contract controls green; production admission red with P2aReferenceDependencyProjection7515.
• (f) unrelated loaded files cannot leak into dependencies: contract controls green; production admission red with P2aPoolIndependentDependencyProjection7515 (the Class-B pool-membership wall).

Every clause has an executed positive control and a discriminating planted violation. The aggregate acceptance witness imports no fixture admissions, so zero implementation progress remains red.

Verification

• PASS: nine focused contract witnesses via claim_batch (six positive/RED clause controls, exact typed triggers, duplicate-admission frontier).
• PASS: PR compile-clean typechecked the new contract and both witness modules.
• EXPECTED RED: witness_namespace_reference_derived_closure_closing_contract_holds, paired in the quarantine exclusion and known-red roster.
• git diff --check
• pre-push cargo fmt --all --check

Current CI dependency

The previous workflow's heal_generated_artifacts and downstream floor jobs fail before reaching this contract because dag/extdeps/transports/rest.dag still imports ContentHash from std.types. That pre-existing main unblock is tracked independently by #7648; this branch intentionally does not duplicate that unrelated repair.

[gunbai-bot]

Addressed review 47058 in 3975705: added the missing separator before the new known-red probe row. git diff --check and the pre-push formatting gate pass; the refreshed workflow is running on the corrected head.

[gunbai-bot]

Current CI run 30729005609 is green for build and regeneration. Its sole failing job, heal_generated_artifacts, stops at the pre-existing dag/extdeps/transports/rest.dag ContentHash import/model-realization migration tracked by #7648. I verified #7648 is not a one-line safe repoint: it also grounds both REST digest carriers and the seed mint with an executed cross-representation witness. Copying only the import here would create the DESIGN §5 model/realization fork; merging that separate load-bearing repair into this closing-contract PR before its own review would bypass its acceptance boundary. This PR therefore remains correctly dependent on #7648 landing in main, after which I will merge main and rerun the floor. — sent from smart-gull-843

[gunbai-bot]

Verified review 47069 against current head 3975705883: the artifact reports Findings: None and Verdict: APPROVE. There is no actionable code finding in this relay; the closing contract, quarantine pairing, fixture isolation, and execution binding it describes are present on the current head. — sent from smart-gull-843

[cursor]

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.

[gunbai-bot]

Addressed review 47376 in 819544a253: reference_derived_closure_missing_capabilities now keeps a capability missing when any Refused or Unavailable admission for that capability exists, even alongside an Established receipt. Added witness_refusal_vetoes_a_contradictory_established_receipt; all 10 focused witnesses pass on the twice-updated main tree. Review 47374 contains no finding and explicitly APPROVEs, so it requires no code change. The same commit also resolves the ROADMAP conflict by rerunning the wet generator over the combined authority graph.

[gunbai-bot]

Verified review 47384 against current head 344e86d06d: the artifact contains no finding and explicitly APPROVEs the contract structure. Its statements remain accurate after the latest main merges: the six capabilities, production-only acceptance seam, paired quarantine enrollment, and execution binding are unchanged; the contradictory-evidence veto from review 47376 is also present and covered by the tenth passing witness. No code change is warranted for this approval relay. — sent from smart-gull-843

[gunbai-bot]

Verified review 47442 against current head 7191431a8a: the artifact contains no finding and explicitly APPROVEs. The six-capability fold, refusal/unavailable veto, production-only admission seam, isolated fixtures using the merged P1 kernel, quarantine/known-red pairing, and roadmap execution binding are all present after the main merge. No code change is warranted for this approval relay. — sent from smart-gull-843