Repository navigation
Refresh roadmap authority to active dependency graph - #7350
Conversation
…sion/nimble-fox-152
|
Addressed review 43881 on head c590c7f: added active terminal |
|
Addressed review 43888 on exact head
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 |
|
Addressed reviews 43893, 43894, and 43897 on exact head
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 |
|
Addressed review 43900 on exact head
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 |
|
Addressed review 43903 on exact head
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 |
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>
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>
* 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>
Summary
TicketLinethroughout the active graph with explicitManualAcceptance, truthful unsigned state, and deliberate 13 small / 15 medium / 16 large sizing.ROADMAP.mdexclusively from the.dagauthority 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
v1-compilerrelease-bin build: PASSmain_wet: PASSmain: PASS.dagfloor (five batches; 4,616 discovery witnesses): PASSgit diff --check: PASSThe branch was synchronized once to current main
17812970a9fe8a1559879241601a30cf2e6c6bc7as authorized. Full hosted CI and fresh review coverage are rerunning on the corrected head. No merge is requested.