Skip to content

Refresh roadmap authority to active dependency graph - #7350

Merged
briansrls merged 36 commits into
mainfrom
session/nimble-fox-152
Jul 28, 2026
Merged

briansrls merged 36 commits into
mainfrom
session/nimble-fox-152

Conversation

@briansrls

@briansrls briansrls commented Jul 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Replace the historical roadmap ledger with 44 remaining committed deliverables and 42 explicit product-dependency edges across eight active chains.
  • Keep accepted, completed, and superseded history—and mutable PR, CI, session, attempt, and lease state—out of authority.
  • Use TicketLine throughout the active graph with explicit ManualAcceptance, truthful unsigned state, and deliberate 13 small / 15 medium / 16 large sizing.
  • Keep automatic admission as future work, document the existing manual dispatch path as live and outside this slice, preserve independent product dependencies, and constrain Ready to scheduling only after accepted parents and the typed identity join; keep SCM/source-intent and other parked plans reachable only as non-dispatchable documentation context.
  • Derive acyclicity mechanically from the graph and add executing REDs for completed, accepted, and superseded row re-entry.
  • Preserve the namespace, P-derive, observation, placement, v1 deletion, shell, roadmap-runtime, and fleet/hygiene critical chains, including their cross-chain prerequisites.
  • Preserve the DESIGN-mandated terminal path from interpreter deletion to repository-wide zero hand-maintained Rust, including src/v1, stage0, and dag/tools; emitted Rust realizations and cited external trust remain explicitly outside that terminal row.
  • Regenerate ROADMAP.md exclusively from the .dag authority and update only its direct projection witnesses.

No mutable open-PR mapping is copied into the roadmap or this handback; active deliverables are identified by durable node IDs and carrier documents.

Validation

  • exact CI-grain v1-compiler release-bin build: PASS
  • all 19 roadmap authority witnesses: PASS
  • all 48 direct roadmap page/row/lamp and doc-reachability witnesses: PASS
  • generated-artifact main_wet: PASS
  • generated-artifact fixed-point main: PASS
  • full composed .dag floor (five batches; 4,616 discovery witnesses): PASS
  • git diff --check: PASS

The branch was synchronized once to current main 17812970a9fe8a1559879241601a30cf2e6c6bc7 as authorized. Full hosted CI and fresh review coverage are rerunning on the corrected head. No merge is requested.

@gunbai-bot gunbai-bot Bot changed the title Roadmap authority refresh: active deliverables and dependency order only Refresh roadmap authority to active dependency graph Jul 28, 2026
@gunbai-bot
gunbai-bot Bot marked this pull request as ready for review July 28, 2026 01:25
@gunbai-bot
gunbai-bot Bot marked this pull request as draft July 28, 2026 02:25
@gunbai-bot
gunbai-bot Bot marked this pull request as ready for review July 28, 2026 02:52
@gunbai-bot

gunbai-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Addressed review 43881 on head c590c7f: added active terminal v1-zero-hand-maintained-rust as a ManualAcceptance TicketLine, dependent on v1-interpreter-delete and carried by the existing dag/gunbc/v1_deletion_plan.dag authority. Its boundary requires every remaining src/v1/stage0 Rust source to be emitted from cited .dag models or deleted, with a roster RED and execution handback; emitted Rust realizations and external trust remain out of scope. The v1 critical-chain witness now executes the terminal edge, and ROADMAP.md was regenerated. Local release build, 17/17 authority claims, 11/11 direct projection/reachability claims, regen, and fixed point pass. — sent from nimble-fox-152

@gunbai-bot

gunbai-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Addressed review 43888 on exact head 6168bf0a05:

  • Restored dag-scm-design.md, dag-scm-product-strategy.md, and node-subtree-visibility-grants.md as reachable, explicitly non-dispatchable parked context; no speculative SCM TicketLines or historical 2-scm-* rows were restored.
  • Removed all 11 false roadmap-runtime-identity-join edges from independent product roots. RoadmapEdge now remains product dependency only.
  • Added a typed closed RoadmapDispatchGate authority pending the runtime identity/lease join, plus executing REDs proving the gate remains closed, parked SCM carriers cannot become active nodes, and product roots cannot regain roadmap-tool dependencies.
  • Regenerated ROADMAP.md; graph is now 43 active nodes / 41 product edges.

Validation on this tree: 19/19 authority witnesses, 48/48 direct projection/reachability witnesses, wet regen, fixed-point regen, and diff check pass. Hosted exact-head build/regen/heal pass; full CI is running.

— sent from nimble-fox-152

@gunbai-bot

gunbai-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Addressed reviews 43893, 43894, and 43897 on exact head 6b69f610f3:

  • Removed the mechanical coproduct-to-Bool dispatch predicate. The staged authority is now a typed record containing only required_join: RoadmapNodeId, and its witness directly verifies that the named prerequisite is the active runtime identity-join node.
  • Corrected the generated preamble: this authority is explicitly not admitted as a live dispatch source until that join is implemented. It makes no claim that today’s belt_dispatch_node, next_spawnable, or manual POST path refuses, and no runtime/spawner code was changed.
  • Reworked the active-row integrity helper to consume canonical line_ticket, item_is_done, and signoff_is_present projections instead of directly walking RoadmapItem and Signoff coproducts. The completed, accepted, and superseded planted REDs retain their behavior.

Validation: 19/19 authority witnesses, 48/48 direct projection/reachability witnesses, wet regen, fixed-point regen, and diff check pass. Hosted exact-head CI is running.

— sent from nimble-fox-152

@gunbai-bot

gunbai-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Addressed review 43900 on exact head 8b9c60b65e:

  • Removed the disconnected RoadmapDispatchGate and its witness entirely. The preamble now says only that automatic admission is future work and truthfully records the existing manual dispatch path as live and outside this model slice.
  • Reframed Ready as an operator scheduling override available only after every dependency edge is accepted and the typed identity join succeeds. It cannot bypass an unaccepted parent, missing/mismatched join, dependency refusal, acceptance, or any other refusal.
  • Updated the dispatch-consumer boundary and RED so unaccepted parents refuse and Ready is optional scheduling input, never dependency substitution.

Validation: 18/18 authority witnesses, 48/48 direct projection/reachability witnesses, wet regen, fixed-point regen, and diff check pass. Hosted exact-head CI is running.

— sent from nimble-fox-152

@gunbai-bot

gunbai-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Addressed review 43903 on exact head 93f37607ad:

  • Restored the terminal to repository-wide zero hand-maintained Rust, explicitly including tracked Rust under src/v1, stage0, and dag/tools.
  • Kept src/v1/stage0 roster reduction as the first intermediate slice rather than the finish line.
  • Updated the terminal RED so any tracked hand-Rust anywhere in the repository without emitted authority and a migration trigger blocks acceptance and reopens the roster.
  • Kept emitted realizations and external rustc/std/OS trust out of scope; the existing v1_deletion_plan carrier and dependency edge are unchanged.

Validation: 18/18 authority witnesses, 48/48 projection/reachability witnesses, wet regen, fixed-point regen, and diff check pass. Hosted exact-head CI is running.

— sent from nimble-fox-152

@briansrls
briansrls merged commit 623519a into main Jul 28, 2026
1 check passed
@briansrls
briansrls deleted the session/nimble-fox-152 branch July 28, 2026 14:19
briansrls added a commit that referenced this pull request Jul 28, 2026
Merge main's roadmap authority refresh (#7350) into the Codex dispatch
slice, and repair the eight witnesses CI reported red.

roadmap_authority.dag / ROADMAP.md take main's refreshed active
dependency graph; the branch's WorkItemExecutionContract mechanism is
re-applied onto it. Every node is ExecutionContractUnspecified — the
declared fail-closed migration frontier — because the one node that
carried a real contract was deleted by the refresh. Dispatch therefore
refuses with a typed environment-admission diagnostic until a node
states its validations; re-binding is per-node roadmap authoring.

The reds were four drift classes, each repaired at the authority rather
than by re-spelling the literal:

- two capability counts went stale when c37e450 added an eighth
  dispatch-platform capability (jq). The join is now stated as a law
  (platform + task) and the preflight roster asserts platform coverage
  structurally beside its base-list ratchet.
- witness_fresh_dispatch_receipt_names_provider asserted a caption
  design main's #7327 deliberately replaced; re-pointed at the contract
  that holds and renamed to match it.
- two emitted-JS scans hardcoded identifiers that were later renamed;
  they now derive from the emitting authority.
- the page witness's blob-wide `!j.ok` negative caught the separately
  modelled POST /cleanup/ route. Replaced with total coverage of
  belt_dispatch_all_status_labels, which a boolean-ok wire contract
  cannot satisfy.

Five new non-fold residue sites are rostered with a shared reason and
dissolution trigger: terminal-state absorption over the provider/worker
observation coproducts, dissolving on a derived terminality projection.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request Jul 28, 2026
dag_compile_clean_gate_passes caught the one RoadmapNode literal outside
the authority module that the merge missed: roadmap_authority_test's
red_fixture builds the record directly, so it needs the field the
#7350 merge added.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request Jul 29, 2026
* model portable dashboard instances and Codex dispatch

* treat dashboard absence checks as probe data

* preflight dashboard instance parent ownership

* model complete dashboard source artifacts

* model dispatch admission and provider progress

* disambiguate generated-artifact observation no-op

* correct dashboard apply cleanup contract

* require exact dashboard source revision

* record exact lab source convergence receipt

* model recursive workflow reconciliation

* bound recursive workflow observation

* record separated lifecycle lab receipts

* project bounded provider event envelopes

* record bounded projection lab receipt

* document recursive workflow advancement plan

* record publication gate dependency receipt

* WIP: 7360 continued

* WIP: 7360 continued

* Resolve #7350 authority refresh and re-arm the drifted witnesses

Merge main's roadmap authority refresh (#7350) into the Codex dispatch
slice, and repair the eight witnesses CI reported red.

roadmap_authority.dag / ROADMAP.md take main's refreshed active
dependency graph; the branch's WorkItemExecutionContract mechanism is
re-applied onto it. Every node is ExecutionContractUnspecified — the
declared fail-closed migration frontier — because the one node that
carried a real contract was deleted by the refresh. Dispatch therefore
refuses with a typed environment-admission diagnostic until a node
states its validations; re-binding is per-node roadmap authoring.

The reds were four drift classes, each repaired at the authority rather
than by re-spelling the literal:

- two capability counts went stale when c37e450 added an eighth
  dispatch-platform capability (jq). The join is now stated as a law
  (platform + task) and the preflight roster asserts platform coverage
  structurally beside its base-list ratchet.
- witness_fresh_dispatch_receipt_names_provider asserted a caption
  design main's #7327 deliberately replaced; re-pointed at the contract
  that holds and renamed to match it.
- two emitted-JS scans hardcoded identifiers that were later renamed;
  they now derive from the emitting authority.
- the page witness's blob-wide `!j.ok` negative caught the separately
  modelled POST /cleanup/ route. Replaced with total coverage of
  belt_dispatch_all_status_labels, which a boolean-ok wire contract
  cannot satisfy.

Five new non-fold residue sites are rostered with a shared reason and
dissolution trigger: terminal-state absorption over the provider/worker
observation coproducts, dissolving on a derived terminality projection.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Carry the execution field into the roadmap authority red fixture

dag_compile_clean_gate_passes caught the one RoadmapNode literal outside
the authority module that the merge missed: roadmap_authority_test's
red_fixture builds the record directly, so it needs the field the
#7350 merge added.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* WIP: 7360 continued

* Route the dispatch read dwell through Milliseconds

review 44135: dag/gunbc/roadmap_component.dag's dispatch_requested_read_dwell_ms
carried its unit in its name while typed as a bare Int, beside the branded
Seconds idiom this PR already uses. Route it through std.types Milliseconds and
force the row's evaluation with a witness that serializes the emitted preamble,
proving the emitted bytes (const gunbcDwellMs = 300;) are unchanged.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* WIP: 7360 continued

---------

Co-authored-by: Brian Searls <briansrls@gunb.ai>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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