Repository navigation
ROADMAP planning - #5646
Merged
Merged
ROADMAP planning#5646
Conversation
…ection Fixes roadmap_authority_witnesses RED: witness_b_ordered_interleaving asserts the §0 milestones prose is immediately followed by **Audits (done):**; the dispatch-discipline prose inserted between them broke that adjacency. Moved it to the end of §0 (after the Meta group) — witness-safe, reads as a closing meta-note. Verified by execution: roadmap_authority_witnesses() = true and run_roadmap_gate_body = ExitSuccess (drift green). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Folds the three grounding notes for the 1-budget-tree node (handed up from quick-ant-298 after the #5582 carrier review), homed in a plan doc because the ctrl#1793 comment wall keeps rationale out of the .dag carrier: - Measure-generalization fence (now code-real via std.measure measure_le/add) - QoS class §3 citation (k8s QoS <- cgroup-v2 memory.{min,low,max}) - actuator-dependency: the model DECIDES budgets, an enforcement actuator (admission cap / cgroup memory.max) PREVENTS the OOM — the §5 honesty boundary, also surfaced inline in the node as a terse caveat. docs/plans/budget-tree.md reachable from ROADMAP.md via the node's grounding pointer. roadmap_authority_witnesses() verified true by execution post-regen. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…model #5582 reworked substantially (operator directive + opus-4-7 round 2): grounded in real accounting (extdeps.accounting.budget, anchored, zero-based, generic over Measure<Q,S>), genuinely recursive, and the §5 framing corrected. Fixes a §5 mislabeling this node carried: a Bool conservation check (node_conserves) was wrongly called a "compile-time wall, unwritable by construction." A Bool check is validation, not construction. The corrected three-way (never conflated): admission (admit_all, zero-based) is the CONSTRUCTION path (over-commit unwritable on it); node_conserves is the honest RESIDUE LENS for raw literals; reconcile is the runtime fail-closed HANDLER. Also folds the convergence survey (realization_width + complexity EffortBudget are the same capped-resource->claims concept, §3 convergence candidates) and moves the QoS citation to the extdeps-anchor pattern. Grounding doc rewritten to match. roadmap_authority_witnesses() verified true by execution post-regen. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…-gaps # Conflicts: # docs/plans/budget-tree.md
…#5579 wall-reframe Operator un-parked the Disposition carrier (GO 2026-06-23); slice-1 prove-by-use dispatched as adhoc-0a633bef-bb9 (fierce-crane-13 under neat-dove-397). - roadmap_authority §0: move 0-disposition from Fenced-OUT to In-scope (active); content = slice-1 mechanics + single-authority convergence home. Note the same reframe on 0-skipped-modeling. - disposition-carrier.md: §0a post-#5579 reframe (comment-wall moved marks comments→data:String rows: now Node-visible but prose-opaque; §3-migrate surface grew, strengthening the carrier case) + §2a taxonomy stress-test ruling (N-marks-per-carrier, not N-axes-per-Disposition; binary holds unless one indivisible mark needs two dispositions — hypothesis for slice-1 to falsify). - ROADMAP.md regenerated from the authority (wipes a stale duplicate-paragraph drift). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…drift), owner + emitter-first sequencing Fold the 2026-06-23 #5639 findings into the self-host gap analysis: the seed has measurably diverged from the .dag (~764 regen errors, stale copy-lists, 89 missing Generated-by headers) — the Purity enforcement gap the doc flagged as a risk on 2026-06-21 has now fired silently across green-CI PRs. Adds a Δ block (improved/changed/untouched), assigns the reconciliation cutover (bright-stag, model-first single-authority derive), fixes emitter-first sequencing, and resolves open-Q1 to (a). Co-Authored-By: Claude Opus 4.8 <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.
Auto-opened by session-dashboard for session
bright-stag-194.Pushing to
roadmap/fold-dispatch-gapsadvances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan