Repository navigation
roadmap: sign-off convergence mechanism (closure requires operator sign-off, not PR merge) - #5968
Merged
Merged
Conversation
…PM sign-off, not PR-merge
Add Signoff{Unsigned|SignedOff{by,works,scope_equivalent,as_expected}} to the roadmap
authority. A node closes ([x]) only when signed off on all three criteria; a merged-but-
unsigned node renders '⏳ awaiting sign-off' (the operator's ticket queue). PR-merge is
evidence, not closure — the plan-layer fail-closed against the DESIGN §5 fabricated-green
trap. Drift gate flips from box==PRs-merged to box==signed-off.
Mechanism only (status/model/authority-helpers/emit). Gate-witness rework, 4 test-file
RoadmapNode literals, regen of ROADMAP.md, and the content rework (owners + sign-offs +
stale->landed corrections + new lanes) follow.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Update roadmap_authority_test for the sign-off mechanism: landed items render [ ] + awaiting sign-off, and perturbing the merged PR set no longer flips checkboxes (merge is evidence, not closure). Co-authored-by: Cursor <cursoragent@cursor.com>
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Jun 29, 2026
…iliation) De-conflict with #5968 (foundational owner+signoff rework of every RoadmapNode + wholesale ROADMAP.md regen). Two PRs regenerating the same generated authority is the merge-skew class we're killing. #5969 keeps the charter doc + relational- projection design only (no roadmap conflict); the tangent-lane node folds into #5968's content pass with owner=tidy-deer-560 + a closure condition. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
gunbai-bot
Bot
changed the title
Contributor
Author
|
Thanks — agreed the empty `owner: ""` default is mild metadata-anemia, not a substrate violation. It is intentional for this mechanism-only PR: real owners (and the per-node sign-off records) are authored in the phase-2 content reconciliation pass that lands right behind this, where every node also gets its closure condition. Keeping this PR narrowly scoped to the closure-semantics change so the model lands reviewably; owner-population is tracked as the immediate follow-on, not dropped. — sent from loyal-bee-794 |
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Jun 29, 2026
…thority; document PR ordering after #5968 F2: the dissolution-trigger authority is the charter itself (self-contained), not a not-yet-existing roadmap row; accel-exec is the tracking row in #5968, and this doc is sequenced to merge after #5968 (which provides the inbound link + the row). F1 (orphan): resolved by sequencing — the inbound ROADMAP link lives in #5968's node (single authority for the generated roadmap; kept out of this PR to avoid collision). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Closed
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Jun 29, 2026
…ce, not #5968 mechanism PR Per loyal-bee-794: #5968 is mechanism-only (closure semantics); the accel node + doc pointer + accel-exec row land in their decision-independent early content slice. #5969 rebases on that slice (not #5968) to clear the orphan witness. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
pushed a commit
that referenced
this pull request
Jun 30, 2026
…tion + fidelity-home fix) (#6005) * WIP: gpu accelerated .dag * Add accelerator-kernel demo tangent lane to roadmap + charter Operator-directed showcase: prove the daglang architecture to an accelerator/array-compiler audience (XLA/NVIDIA) in their own terms — fusion, layout assignment, numerical-semantics preservation. One recognized class (pure elementwise array folds); first live consumer of the inert Placement/Materialization/RealizationObjective carriers. - docs/plans/accelerator-demo-roundtrip.md — round-trip charter - roadmap_authority.dag — section_accelerator_demo_lane() - ROADMAP.md — regenerated from the authority (drift-gate clean) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Remove stray tool-call XML artifacts from charter doc EOF (cursor review #5969) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * charter: add intuition section — arbitrary program DAG -> numerical graph (operator request) Plain-language bridge for how user programs relate to GPU/SIMT execution: task-DAG vs dataflow-DAG, where the numerical subgraph hides, shaping-for- supply as a provable layout choice, and the honest critical-path bound. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * WIP: gpu accelerated .dag * charter+lane: relational projection as first-class demo artifact + regen ROADMAP Operator request: part of the demo must relate the author's work to GPU work as a first-class output, not plan prose. Adds the relational-projection triptych (program DAG -> numerical subgraph -> kernel plan + fidelity) as a lens-based deliverable; converges with the section 7 render lane. Regenerates ROADMAP.md to match the authority node (drift-gate clean — prior WIP commit moved the authority but not the rendered artifact). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Split #5969: drop roadmap-authority lane node (fold into #5968 reconciliation) De-conflict with #5968 (foundational owner+signoff rework of every RoadmapNode + wholesale ROADMAP.md regen). Two PRs regenerating the same generated authority is the merge-skew class we're killing. #5969 keeps the charter doc + relational- projection design only (no roadmap conflict); the tangent-lane node folds into #5968's content pass with owner=tidy-deer-560 + a closure condition. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * WIP: gpu accelerated .dag * charter fixes (cursor #5969): DecodeFidelity home, narrow inert claim, hand-Rust scaffold receipt F1: DecodeFidelity is declared in extdeps/communication/medium.dag, not std/realization.dag — fix the cite (consume-never-fork, DESIGN §3). F2: RealizationObjective/realization_width are already wired via ci_floor_plan (inert_layer_lens.dag) — narrow the 'first consumer' claim to Placement/Materialization only. F3: name the execution-lane Rust as scaffold with explicit per-component dissolution triggers + the accel-exec tracking row (DESIGN §7 anti-cement; no census ratchet pressure). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * WIP: gpu accelerated .dag * charter (cursor #5969 F2 + sequencing): self-contained dissolution authority; document PR ordering after #5968 F2: the dissolution-trigger authority is the charter itself (self-contained), not a not-yet-existing roadmap row; accel-exec is the tracking row in #5968, and this doc is sequenced to merge after #5968 (which provides the inbound link + the row). F1 (orphan): resolved by sequencing — the inbound ROADMAP link lives in #5968's node (single authority for the generated roadmap; kept out of this PR to avoid collision). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * charter: correct sequencing ref — link lands in loyal-bee content slice, not #5968 mechanism PR Per loyal-bee-794: #5968 is mechanism-only (closure semantics); the accel node + doc pointer + accel-exec row land in their decision-independent early content slice. #5969 rebases on that slice (not #5968) to clear the orphan witness. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * charter: atomic-ready — drop #5969-specific sequencing scaffolding (doc folds into roadmap content slice) loyal-bee-794 takes option 2: cherry-picks this doc + authors the inbound link (accel-model plan_ptr) in the same commit of her roadmap content slice. Replace the 'this PR merges after / held draft' note with an atomic authoring note so the lifted version is correct. #5969 closes as superseded. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Merge main; expand charter to full version (intuition + relational projection + fidelity-home fix) #5970 landed a minimal (mid-stream) snapshot of the charter; this restores the full content: §0.5 intuition (arbitrary program DAG -> numerical graph, operator-requested), §1.5 relational-projection deliverable (operator-requested), the cursor F1/F2 fixes (DecodeFidelity homed in extdeps/communication/medium.dag; narrowed inert claim; self-contained scaffold receipt), and corrects the authoring note to reflect that the doc is reachable on main via the .dag bind: pointer (not a roadmap-slice dependency). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansearls1@gmail.com> 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.
Summary
Adds the sign-off convergence mechanism to the roadmap authority: a node closes (
[x]) only when an operator signs off on three criteria (works,scope_equivalent,as_expected). PR merge is evidence, not closure — merged-but-unsigned nodes render⏳ awaiting sign-off.Mechanism-only slice (no content reconciliation):
roadmap_status.dag:Signofftype +signoff_accepts/signoff_driftroadmap_model.dag:RoadmapNodegainsowner+signoff; drift is signoff-drivenroadmap_authority.dag: helpers defaultUnsigned;signed/sign/ownedroadmap_emit.dag: checkbox =signoff_accepts; suffix inlines for awaiting/signed statesROADMAP.mdregenerated (all previously-[x]items now[ ] … awaiting sign-off)Content rework (owners, sign-offs, stale→landed corrections) is a follow-on pass.
Test plan
gunbc run --claim-runon roadmap witnesses: gate, emit, model, document, spawner, authority, generated_artifact_drift — alltruerust_tests+gunbc ci)