Repository navigation
disposition-carrier plan: total-migration scope (_contracts coproducts + DeclarationRef→NodeRef grounding) - #5754
Merged
Merged
Conversation
gunbai-bot
Bot
changed the title
…hority #5745 hand-added the `→ [host-effect orchestration plan]` pointer to the generated ROADMAP.md without modeling it in roadmap_authority.dag, so the generated_artifact_drift_gate failed fleet-wide (emit(.dag) lacked the line the committed .md carried) — main has been RED since that merge. An earlier auto-committed regen on this branch "resolved" the drift by deleting the line, which would in turn orphan docs/plans/host-effect-orchestration.md. Fix the authority, not the projection: add the pointer as a section_prose element immediately before the Host-operation band group (its text reads "G1–G3 below are its consumers", which now directly follow it), then regen ROADMAP.md from the .dag. emit(.dag) == committed .md → drift gate green and the host-effect plan doc keeps a modeled inbound link. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…merge The merge with main brought #5762's structure (Host-operation band label as a section_prose, host-effect pointer below it, empty group label). Conflict was resolved to main's side; regenerate ROADMAP.md from the .dag so emit == committed and the generated_artifact_drift_gate stays green. Co-Authored-By: Claude Opus 4.8 (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.
Works the total migration into the
disposition-carrierplan tracker (operator directive: "i need a total migration/cleaned up"). The plan already covered thedata:Stringfleet + theNodeRef-bind intent; two gaps are now captured. Authority isdsl/gunbc/plans/disposition_carrier.dag;docs/plans/disposition-carrier.mdis its regenerated projection (drift gate green).§6 — total migration surface. All five disposition regions in one table, ordered by what the substrate can enumerate now. Names the 20
_contractsCoproductWireContracts (0/20 tagged, across docker/github×6/llm×2/systemd) as the recommended next ratchet region — buildable today viaenumerate_coproduct_decls(), no gunbc#5364 dependency. Answers the operator's "is tagging coproducts in_contractsrequired?" → not enforced yet; that is the #1SubstrateMandatoryTagend-state, reached region-by-region, not by flag-day.§7 — symbolic binds. Records the carrier drift: landed
bind: DeclarationRef(stringly{module_path, decl_name, field}) vs §1'sbind: NodeRefintent. Why it shipped stringly (field-granular resolution gated on gunbc#5364). The enforcement gap the operator flagged ("a lens to enforce that?") — no lens resolves a DeclarationRef today. Two-step grounding: (1) ungated resolution lens now over enumerated coproduct decls (RED on a dangling decl_name; the discriminating consumer that makes the_contractsmigration non-inert); (2)DeclarationRef→ resolvedNodeRef, unresolvable-is-unwritable, once #5364 lands.§1 carrier note + §5 sequencing updated to point at both.
Coordination: the
disposition-carrierplan +std/disposition.dagcarrier are the active slice-1 of neat-dove-397 / fierce-crane-13 (DESIGN-load-bearing, checkpoint to bright-stag-194). This PR edits only the tracker doc (not the carrier), so the owning lane reviews the added scope rather than getting a silent conflict. Notified.Verification:
gunbc compile --source-root dsl= 0 diagnostics;run_generated_artifact_drift_gate= ExitSuccess.🤖 Generated with Claude Code