docs(planning): post-#4110 burn-down — #4102 + compute_fabric landing log

[briansrls]

Summary

Per-merge maintenance on docs/planning/v4-done-predicate-burn-down-2026-05-30.md after landings post-#4110 on main at 084005699:

• Tree HEAD → 084005699 (08:56Z)
• feat(leaf-model): R3-internal Symbol emit-coupling exercise (post-SG-1) #4102 R3-internal Symbol emit-coupling (P5 leaf-model path)
• compute_fabric.dag Worksheet A §6 landed (8c01c15c1) — P5 Layer 2 substrate
• docs(planning): post-#4109 burn-down — HEAD refresh + landing log row #4110 landing-log row added

Replaces stale auto-opened draft duplicate of pre-merge #4110 content. 0/6 PROVEN preserved.

Worker attestation

• Title describes the change
• Doc-only; no code/substrate changes in this PR (records prior landings)
• Tests: doc-only — CI only
• No secrets staged

Test plan

• CI green on push

[briansrls]

Verified both dashboard review artifacts against 405f702aa:

@cursor/composer-2.5 #22852 — APPROVE: Confirmed. Docs-only burn-down refresh; 084005699 and 8c01c15c1 resolve on origin/main; dsl/std/compute_fabric.dag present; P5 still Layer 2 OPEN / not GREEN (#4102 row explicit). No fix required.

@claude-opus-4-7 #22853 — APPROVE: Confirmed. HEAD pointer + three landing-log rows only; no code/substrate/invariants. No fix required.

Merge readiness: 2/2 APPROVE (cursor + claude), 0 REQUEST_CHANGES, MERGEABLE, CI green. Stopping per temporary operator-merge policy — not running gh pr merge.

— sent from merry-badger-222

[briansrls]

Review metadata

• Provider / model: openai-pro / gpt-5-5-pro
• Commit: 405f702a · Trigger: manual
• Comparison: main @ 08400569 ... session/merry-badger-222 @ 405f702a
• Conversation: View conversation

---

1. Story of the diff

This PR is a planning-log refresh for docs/planning/v4-done-predicate-burn-down-2026-05-30.md, not an implementation change. It advances the tracker’s stated mainline from post-#4109 to post-#4110, records #4102 as an R3-internal Symbol emit-coupling exercise, and records dsl/std/compute_fabric.dag Worksheet A as landed at 8c01c15c1 while preserving the important status that P5 Layer 2 is still OPEN and Not GREEN. The added landing-log rows at pr-4111.diff.txt:29-31 align with the refreshed HEAD/evidence rows at pr-4111.diff.txt:10 and pr-4111.diff.txt:20-21, so the document is acting as a burn-down ledger rather than changing the plan’s semantics. chatgpt-review-e589ab36-7ae6-42…

chatgpt-review-e589ab36-7ae6-42…

2. Invariant categories

1. LAYER MODEL (substrate vs implementation).

Compliant — the diff references substrate work but does not modify substrate declarations. The key decision is that it logs compute_fabric.dag Worksheet A as landed while keeping “Layer 2 OPEN — structural bridge live” and “Not GREEN,” so it does not claim full substrate closure from a partial landing at pr-4111.diff.txt:20.

1. INVARIANTS.md + modeling-discipline.md.

Compliant — progress-is-dissolution / fail-closed status is preserved: the tracker records new evidence but explicitly retains the open bridge state and a near-term re-check rather than silently converting the lane to green. The “Blocking receipt” remains deletion of scripts/v4-testclaim-corpus-gate.sh, and the changed evidence line continues to say “Not GREEN” at pr-4111.diff.txt:17 and pr-4111.diff.txt:20.

1. CODING.md.

N/A — no Rust implementation or helper code is changed; the diff is a Markdown planning-log update.

1. TESTING.md.

Compliant — no behavior or executable surface changes are introduced, so no new tests are required. The doc update keeps test-related work framed as pending structural receipt work: modeled T-22 eval, structured TestClaimRun verdicts in CI, and deletion of the shell bridge remain the blocking receipt at pr-4111.diff.txt:17.

1. LOCKED DESIGN DECISIONS.

Compliant — the diff does not alter a locked design document or relax the Pure Bootstrap / 0-floor direction. It only logs that one substrate worksheet landed and that the relevant layer remains open, which is compatible with the uploaded Pure Bootstrap authority’s “data / generated” direction and not a semantic departure.

1. TRACKED vs UNTRACKED DEBT.

Compliant — the live scaffold/debt remains tracked: “Layer 2 OPEN — structural bridge live” is bounded by the existing blocking receipt and the 2026-06-01 re-check at pr-4111.diff.txt:17, pr-4111.diff.txt:20, and pr-4111.diff.txt:23. The PR adds no new TODO, scaffold, or temporary representation.

2.5. Top-down PM intent review

Compliant — this PR does not dilute the PM-level intent. It is careful not to turn Worksheet A into a completion claim: the new text says compute_fabric.dag Worksheet A landed, but the same row still says Layer 2 is open and not green at pr-4111.diff.txt:20; the new landing-log rows likewise mark #4102 as “not GREEN” and the compute fabric row as a Layer 2 substrate landing, not as bridge deletion or release readiness at pr-4111.diff.txt:30-31. That should cause a worker to understand the correct next state: evidence improved, but the structural bridge replacement remains unfinished. chatgpt-review-e589ab36-7ae6-42…

3. Verdict

APPROVE — This is a narrow tracker refresh that records newly landed work without overclaiming closure. I did not find a diff-cited invariant violation or PM-intent dilution that should block merge.

[briansrls]

@openai-pro/gpt-5-5-pro (#22854 artifact + posted api-review comment): Verified against 405f702aa. Dashboard stdout #22854 is reviewer startup log only; substantive verdict is the posted APPROVE api-review comment (sha 405f702a) — narrow tracker refresh, compute_fabric.dag Worksheet A logged without overclaiming P5 Layer 2 closure (still OPEN / not GREEN at :152-153, #4102 row explicit). No invariant or PM-intent dilution. No fix required.

Merge readiness (re-eval): ≥2 distinct APPROVE (claude + cursor dashboard; openai-pro manual APPROVE additive), 0 REQUEST_CHANGES, MERGEABLE/CLEAN, CI green. Stopping per temporary operator-merge policy — not running gh pr merge.

— sent from merry-badger-222