Repository navigation
fix(ci-floor): delete white-box/tautological spawn-width witnesses (MAIN-RED) - #6083
Closed
gunbai-bot[bot] wants to merge 24 commits into
Closed
gunbai-bot[bot] wants to merge 24 commits into
gunbai-bot[bot] wants to merge 24 commits into
Conversation
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>
…iew #5969) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…raph (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>
…gen 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>
…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>
…, 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>
…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>
…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>
…oc 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>
…ojection + 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>
Contributor
Author
|
Closing — this PR was accidentally opened against the wrong head branch (session/tidy-deer-560, 0 diff). Reopening against the correct branch with the actual changes. — sent from tidy-deer-560 |
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
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.
Fixes a main-red (fragile spawn-width witness) per operator directive
Directive: white-box/tautological witnesses do not belong in the codebase.
The spawn-width witness cluster has been flip-flopping main red↔green for several PRs (#6059 → #6070 → #6079 → #6073) because it was coupled to the live
execution_corpus_spawn_width(), which shifts whenever any PR adds/removes a corpus witness. The witnesses themselves re-computed the implementation and asserted it equals itself — testing nothing. Deleting the four:witness_floor_spawn_width_zero_budget_falls_backint_min(fallback, exec)clamp intogunbc_ci_floor_spawn_width_for_budget, this assertedfallback == int_min(fallback, exec)≡fallback ≤ exec— a fragile corpus-coupled property, and the current main-red.witness_floor_unreadable_budget_uses_conservative_envelopefor_budgetpath →int_min(…) == int_min(…)tautology.witness_plan_spawn_width_is_floor_width_at_runner_capplan_spawn_widthis a thin wrapper overfor_budget→for_budget(cap) == for_budget(cap)tautology.witness_execution_corpus_spawn_width_at_runner_capexecution_corpus_spawn_width() == 3; breaks on any corpus-size change.Kept: the genuine behavioral witnesses — tight-budget backoff inequality, memory-fit, and headroom checks.
Consistency
v2.lens.unwired_modelremoved in lockstep so the Ban unwired models: floor-enrolled lens (subsumes inert_carrier) — §5 coverage-by-illusion wall #6078 unwired-model lens stays consistent. Net-neutral: verified identical unrostered/stale counts before/after this change.int_minimport retained (still used byfor_budget). Zero orphan references repo-wide.Verified green-by-execution
ci_floor_run_envelope_witnesses,ci_floor_spawn_width_live_budget_witnesses,ci_floor_honest_width_fold_witnessesall PASS.🤖 Generated with Claude Code