Repository navigation
roadmap: §0 priority spine — frontload compile wall + complexity (operator, 2026-07-06) - #6343
Merged
Merged
Conversation
…rator, 2026-07-06) Adds section_0 to roadmap_authority.dag (regenerated ROADMAP.md) capturing the operator's current execution ordering, rearranged 2026-07-06 to frontload the compile wall and complexity enforcement: ① compile wall (refreshed to #6239's 100+min; the rust-gate timeout thrash #6339/#6342 recorded as a downstream symptom) ② complexity enforcement whole-codebase — un-shelved from §4 (complexity budget + enforcement-intent gate + intent-linearity + expressibility-frontier gap analysis) ③ affected set live in CI ④ Realization (carrier inhabited; dag↔v2 de-fork) ⑤ dev-UX minimality — un-shelved from §4 (fold-ergonomics + namespace-only resolution) Overlay approach (operator-approved): the two pillars (§1 get-off-v1, §2 compute-fabric) stand as the strategic frame; §0 is the priority ordering over them, each item pointing into the detailed lane (no dual dispatch). §4 preamble notes the un-shelve. Surfaces the two post-reset directions absent from the roadmap: namespace-only resolution and intent-linearity. ROADMAP.md regenerated byte-exact from the edited authority. 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.
Reshuffles the roadmap to reflect the operator's current execution ordering (2026-07-06), rearranged to frontload the compile wall and complexity enforcement. Edits the authority (
dag/gunbc/roadmap_authority.dag);ROADMAP.mdis regenerated byte-exact.What & why
The roadmap was reset 2026-07-01 into two pillars (§1 get-off-v1, §2 compute-fabric) + audit + shelved. Three of the operator's current top-5 priorities were shelved, buried, or absent, and the compile-wall was understated by a generation ("~47min" vs #6239's 100+min). This adds a §0 priority spine (overlay — pillars stay as the strategic frame beneath):
Also surfaces the two post-reset operator-signed directions the roadmap didn't mention: namespace-only resolution and intent-linearity.
Mechanics
Overlay (operator-approved): §0 items point into the detailed §1–§4 lanes rather than duplicating them (no dual dispatch); §4 preamble records the un-shelve.
ROADMAP.mdregenerated from the edited authority and verified byte-exact againstexpected_roadmap_md()(the drift gate's oracle) —gunbc ci/main_wetdon't run locally (compile-wall), so the projection was run directly (--source-root dag, 597ms) and the two hunks applied to the committed file byte-for-byte.Docs/authority-only;
ci-floor is pre-existing-red (compile-wall).🤖 Generated with Claude Code