Skip to content

ROADMAP §0: un-park the Disposition carrier — fold slice-1 dispatch + post-#5579 wall-reframe - #5611

Merged
briansrls merged 11 commits into
mainfrom
roadmap/fold-dispatch-gaps
Jun 23, 2026
Merged

briansrls merged 11 commits into
mainfrom
roadmap/fold-dispatch-gaps

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Jun 23, 2026 •

Copy link
Copy Markdown
Contributor

Folds the operator's un-park of the Disposition carrier (GO 2026-06-23) into the ROADMAP authority, plus the post-#5579 wall-reframe.

What changed

Dispatch

Slice-1 prove-by-use is dispatched as work-item adhoc-0a633bef-bb9 (fierce-crane-13 under neat-dove-397). The std carrier decl is DESIGN-named load-bearing → it checkpoints back to bright-stag-194 before any row migrates; migration is region-by-region, each region red-on-revert so the lens never goes inert mid-migration.

Verification

  • ROADMAP.md is a generated projection: regenerated, drift gate green (ROADMAP/ci.yml/.gitignore all == their .dag authority).
  • roadmap_authority_witnesses green.

🤖 Generated with Claude Code

briansrls and others added 10 commits June 22, 2026 22:13
…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>
@gunbai-bot gunbai-bot Bot changed the title ROADMAP planning ROADMAP §0: un-park the Disposition carrier — fold slice-1 dispatch + post-#5579 wall-reframe Jun 23, 2026
@gunbai-bot
gunbai-bot Bot marked this pull request as ready for review June 23, 2026 03:43
@briansrls
briansrls merged commit ec12e86 into main Jun 23, 2026
2 checks passed
@briansrls
briansrls deleted the roadmap/fold-dispatch-gaps branch June 23, 2026 04:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant