Skip to content

W2.6 — Cross-target python.dag leaf-model verification (PR #3938 §11.4 Wave 2). Mirror the rust.dag R1 pattern landed in #3972 (mergeCommit e2a33511ee) for python target. Deliverables: (1) python.dag R1 fixture (Phase-1 minimal Python source: 'def r1_test() -> int: return 0' or equivalent typed form - #4022

Merged
briansrls merged 3 commits into
mainfrom
session/warm-tern-791
May 30, 2026
Merged

W2.6 — Cross-target python.dag leaf-model verification (PR #3938 §11.4 Wave 2). Mirror the rust.dag R1 pattern landed in #3972 (mergeCommit e2a33511ee) for python target. Deliverables: (1) python.dag R1 fixture (Phase-1 minimal Python source: 'def r1_test() -> int: return 0' or equivalent typed form#4022
briansrls merged 3 commits into
mainfrom
session/warm-tern-791

Conversation

@briansrls

@briansrls briansrls commented May 30, 2026

Copy link
Copy Markdown
Contributor

Auto-opened by session-dashboard for session warm-tern-791.
Pushing to session/warm-tern-791 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

  • Title describes the change (not the session id or branch).
  • PR body summarises what and why (replace the TODO below).
  • Tests run: name the command (e.g. npm test, cargo test) and the result.
  • If this closes a work item, the body contains a Closes #N directive.
  • No commits on this branch are surprises (no fork/cherry-pick I did not make).
  • No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

  • TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

@briansrls
briansrls marked this pull request as ready for review May 30, 2026 20:30
@briansrls @cursoragent
fix(ci): cargo fmt + SG-0 pairing for python R1 boundary ratchet
2b56352 
Apply rustfmt to integration module ordering and boundary test formatting.
Add sg0-pr-body-append.4022.txt for net +1 on v4_leaf_model_python_r1_test.rs.

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls
briansrls merged commit 7ffe53d into main May 30, 2026
10 checks passed
briansrls added a commit that referenced this pull request May 30, 2026
@briansrls
merge: sync session/warm-tern-791 with main after #4022 squash merge
22c711f
@briansrls briansrls mentioned this pull request May 30, 2026
Closed
6 tasks
briansrls added a commit that referenced this pull request May 30, 2026
@briansrls @cursoragent
docs(planning): Wave 2 maintenance burn-down — post-#4021 landings
4f7c875 
Maturation tracker refresh: #4014 SG-7, #4022 W2.6 python R1, #4015
rung gate, #4023 ship-disposition. Adds Wave 2 landing log + Jun 1
state-at-tag courtesy note. D-REL-1 flavor (iv) framing retained.

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls briansrls mentioned this pull request May 30, 2026
Merged
6 tasks done
briansrls added a commit that referenced this pull request May 30, 2026
@briansrls @cursoragent
docs(planning): Wave 2 maintenance burn-down — post-#4021 landings (#…
48508c6 
…4030)

* WIP: v4-done predicate burn-down — Jun 1 push: update tracker per Wave 2 disp

* docs(planning): Wave 2 maintenance burn-down — post-#4021 landings

Maturation tracker refresh: #4014 SG-7, #4022 W2.6 python R1, #4015
rung gate, #4023 ship-disposition. Adds Wave 2 landing log + Jun 1
state-at-tag courtesy note. D-REL-1 flavor (iv) framing retained.

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request May 30, 2026
@briansrls
fix(planning): address cursor REQUEST_CHANGES on #4043
8a5769c 
Three valid findings:
1. Cross-ref path: v4-done-six-predicate-burn-down → v4-done-predicate-burn-down
   (corrected 3 occurrences; matches actual filename)
2. W2.6 contradiction: dropped "W2.6 python.dag leaf-model spec (proud-pike)"
   from in-flight list; W2.6 is MERGED via #4022 per Wave 2 table
3. MW-D8 disposition: PM doc deferred to sharp-otter-407's #4017 ledger as
   single authoritative source. Reframed headline from "4/5 MET" to
   "3/5 PROVEN per ledger" (C2 stays GAP/SCAFFOLD_PRESENT pending
   falsification receipt of recursion-impossible-by-construction even after
   #4014 impl merged; C4 still GAP gated on C2). Eliminates parallel-ledger
   risk per P2 single-authority.
briansrls added a commit that referenced this pull request May 30, 2026
@briansrls
fix(planning): cursor RC#2 + proud-pike adjudication absorption
062481d 
Cursor RC #2 (line 101 contradiction): tree-health row said
"Authoring W2.3 + W2.6 worksheets" while same doc marks W2.6 merged.

Root cause uncovered by proud-pike state report (msg_b7140f50): "W2.6"
is actually JOINT across three lanes — Runtime/TestClaim shipped its
slice (#4022) but Modeling DFS worksheet + Target Realization carriers
are pending. PM doc was over-simplifying by calling W2.6 "merged."

Reframed W2.6 as W2.6a/b/c:
- W2.6a Runtime slice: ✓ MERGED #4022
- W2.6b DFS worksheet: blocked-on-decision:keen-heron-python-LeafModelClaim-subject-coproduct
- W2.6c TR carriers: gated on W2.6b

Also absorbed proud-pike's W2.3 = ready-for-worker-dispatch (worksheet
landed; held by Compiler Spine until #4014 + W1.5).

Applied blocked-state protocol per operator standard: every Wave 2 row
now has one of {ready-for-worker-dispatch, blocked-on-receipt:X,
blocked-on-decision:X, in flight}. No ETA state remains.
briansrls added a commit that referenced this pull request May 30, 2026
@briansrls @claude
docs(planning): v4 progress snapshot 2026-05-30T22Z — PM visibility d…
5721f63 
…oc (#4043)

* docs(planning): v4 merge wave + next-waves planning (operator engagement requested)

Operator 2026-05-30: "take a doc covering the merges we're making now... and
then, we can discuss the upcoming waves and any changes/decisions we have to
make (in the doc)."

Inventories the ~15-PR backlog clearing now (post operator self-merge
re-authorization). §3 captures substrate baseline post-clear. §4-§6 sketch
three upcoming waves. §7 surfaces 7 operator decisions worth making before
dispatch:

  D1 Wave 1 parallelism (recommended yes; confirm or constrain)
  D2 Wave 1 ordering pressure (priority if any slows down)
  D3 Cross-target widening scope for v4 release
  D4 Phase 2 (T-24 close) trigger
  D5 Manager succession policy (parallel sessions on same role-node?)
  D6 Dashboard-tooling patterns — dispatch any work?
  D7 Operator engagement model through Wave 1

Wave 1 (immediate post-clear, 7 items, all owner-named): SG-7 impl,
Phase 1.4 Upsert<T> substrate, Step 4 R1 first leaf-model verdict,
Phase 1a T-22 interpreter, Phase 2.1 ci.dag types, SG-2 re-dispatch,
R2a/R2b/R3 claim authoring.

Wave 2 (mid-term, gated on Wave 1): SG-1, SG-5/6, Phase 1.5
CiUpsertStep, Phase 1b atom migration, Phase 4 widening, python.dag
verification.

Wave 3 (longer-horizon, decision-loaded): Phase 2 T-24 close, Phase 2.5
affected-set gate, rung 5/6/7/8/9 closures.

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

* docs(planning): cursor #3983 22015 — fix W3.5 narrowing of v4-done

cursor REQUEST_CHANGES: line 134 said rung 7 was "THE v4-done predicate"
— retracted framing from PR #3938 §8 D4. v4-done per TASKS.md:805-817
is six collective predicates, not rung 7 alone.

W3.5 description updated: "Load-bearing for predicate 4 (bit-identical
self-output) — NOT v4-done alone. Per PR #3938 §8 D4: v4-done = all six
predicates collectively..."

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

* WIP: PM May 29

* docs(planning): v4 progress snapshot 2026-05-30T22Z — PM visibility doc

Operator-requested visibility doc. Complements merry-badger-222's
incoming per-predicate burn-down amendment with a wave-level + immediate-
momentum lens.

Headlines:
- 0/6 v4-done predicates PROVEN; 5 YELLOW + 1 GRAY
- ~7,951 rustc errors baseline; SG-2/SG-5 substrate landed; SG-1 imminent
- Wave 1 MW-D8: 4/5 conditions MET (W1.5 ci_selection_receipt_shadow remaining)
- Wave 2: ~85% closed (W2.2 SG-5 + W2.5 + W2.6 ✓; W2.1 SG-1 in flight;
  W2.3/W2.4 worksheet authoring)
- Release: flavor (iv) alpha/WIP — ships AS-IS with honest disclaimers

* fix(planning): address cursor REQUEST_CHANGES on #4043

Three valid findings:
1. Cross-ref path: v4-done-six-predicate-burn-down → v4-done-predicate-burn-down
   (corrected 3 occurrences; matches actual filename)
2. W2.6 contradiction: dropped "W2.6 python.dag leaf-model spec (proud-pike)"
   from in-flight list; W2.6 is MERGED via #4022 per Wave 2 table
3. MW-D8 disposition: PM doc deferred to sharp-otter-407's #4017 ledger as
   single authoritative source. Reframed headline from "4/5 MET" to
   "3/5 PROVEN per ledger" (C2 stays GAP/SCAFFOLD_PRESENT pending
   falsification receipt of recursion-impossible-by-construction even after
   #4014 impl merged; C4 still GAP gated on C2). Eliminates parallel-ledger
   risk per P2 single-authority.

* fix(planning): cursor RC#2 + proud-pike adjudication absorption

Cursor RC #2 (line 101 contradiction): tree-health row said
"Authoring W2.3 + W2.6 worksheets" while same doc marks W2.6 merged.

Root cause uncovered by proud-pike state report (msg_b7140f50): "W2.6"
is actually JOINT across three lanes — Runtime/TestClaim shipped its
slice (#4022) but Modeling DFS worksheet + Target Realization carriers
are pending. PM doc was over-simplifying by calling W2.6 "merged."

Reframed W2.6 as W2.6a/b/c:
- W2.6a Runtime slice: ✓ MERGED #4022
- W2.6b DFS worksheet: blocked-on-decision:keen-heron-python-LeafModelClaim-subject-coproduct
- W2.6c TR carriers: gated on W2.6b

Also absorbed proud-pike's W2.3 = ready-for-worker-dispatch (worksheet
landed; held by Compiler Spine until #4014 + W1.5).

Applied blocked-state protocol per operator standard: every Wave 2 row
now has one of {ready-for-worker-dispatch, blocked-on-receipt:X,
blocked-on-decision:X, in flight}. No ETA state remains.

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 31, 2026
@briansrls @cursoragent
Wc — W3.3 cross-target equivalence on nat_semiring (Rust + Python + G…
494f42e 
…o per Wave F F3 operator-ratified scope). Execute nat_semiring's complete roster on all three target outputs (Rust via #4047 transport, Python via #4022 transport, Go via NEW transport you author following the Rust/Python pattern), (#4081)

* WIP: Wc — W3.3 cross-target equivalence on nat_semiring (Rust + Python + Go p

* WIP: Wc — W3.3 cross-target equivalence on nat_semiring (Rust + Python + Go p

* WIP: Wc — W3.3 cross-target equivalence on nat_semiring (Rust + Python + Go p

* chore: apply cargo fmt for W3.3 harness test

Fixes CI fmt check on PR #4081.

Co-authored-by: Cursor <cursoragent@cursor.com>

* WIP: Wc — W3.3 cross-target equivalence on nat_semiring (Rust + Python + Go p

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls briansrls mentioned this pull request May 31, 2026
Merged
4 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@briansrls