Skip to content

docs(planning): v4-done tracker — P1-P6 :819 snapshot + P5 disambiguation - #3975

Merged
briansrls merged 4 commits into
mainfrom
session/nimble-crane-490-tracker-refresh
May 30, 2026
Merged

briansrls merged 4 commits into
mainfrom
session/nimble-crane-490-tracker-refresh

Conversation

@briansrls

@briansrls briansrls commented May 30, 2026 •

Copy link
Copy Markdown
Contributor

Auto-opened by session-dashboard for nimble-crane-490.

Summary

Refresh docs/planning/v4-done-predicate-tracker-2026-05-30.md after Close/Receipt mapping coordination (#3973): add explicit P1–P6 Close-status snapshot for TASKS.md:819, cross-link the line-anchor mapping doc, and disambiguate predicate P5 (TestClaim suite) from INVARIANTS A3/P5 resolve-posture bridge throughout the tracker.

Test plan

  • Docs-only; no code or substrate changes.
  • Relied on CI fmt / affected after gh pr ready.

Worker attestation

  • Title describes the change (not the session id or branch).
  • PR body summarises what and why.
  • Tests: docs-only — CI.
  • No GitHub issue close directive (dashboard work item node://adhoc-f4a9805f-560).
  • No surprise commits.
  • No secrets / credentials / large binaries.

briansrls and others added 2 commits May 30, 2026 06:23
Cross-link Close/Receipt mapping (#3973). Add six-row Close-status snapshot;
disambiguate predicate P5 (TestClaim) vs INVARIANTS A3/P5 resolve-posture bridge.

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls briansrls changed the title Self-host/Release Manager — authority over T-15, the six v4-done predicates per TASKS.md:801-815 (every-other-task / corpus-compiles / emit-compiles / bit-identical-self-output / TestClaim-suite-passes / hand-Rust-not-editable-authority-proven-by-reproduction), T-36 round-trip, reproduction proof, c docs(planning): v4-done tracker — P1-P6 :819 snapshot + P5 disambiguation May 30, 2026
@briansrls
briansrls marked this pull request as ready for review May 30, 2026 06:24
@briansrls

Copy link
Copy Markdown
Contributor Author

Reviews #21703 / #21704 — verified, no code change

Both dashboard items are APPROVE (not REQUEST_CHANGES).

Review Verdict Verification
cursor #21703 APPROVE P1–P6 snapshot matches :819 at main@678bb8bbd; P5 vs INVARIANTS A3/P5 disambiguation at :40, :89, :253 correct. :249 in snapshot = frozen :819 anchor; :273 in live evidence = current ci.yml invocation — intentional, not a semantic error.
claude #21704 APPROVE Docs-only; disambiguation is genuine improvement; no invariant/code surface.

Merge readiness: 2/2 dashboard approvals; 0 REQUEST_CHANGES; CI green; MERGEABLE. Stopping — operator manual merge per policy.

— sent from nimble-crane-490

briansrls and others added 2 commits May 30, 2026 08:21
Per review #21827: :249 is M1 rust-emit continue-on-error; bridge step
is v2 → v4 bootstrap resolve-posture gate at :266-273.

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

Copy link
Copy Markdown
Contributor Author

Review #21827 (REQUEST_CHANGES) — fixed in 8e9c7c572

Finding: :40 cited ci.yml:249 while bridge step lives at :266-273 (v2 → v4 bootstrap resolve-posture gate).

Fix: Snapshot block now cites .github/workflows/ci.yml:266-273, aligned with evidence at :89 / :253. Added footnote that legacy TASKS.md:819 still says :249 (M1 rust-emit line) — tracker intentionally uses live wiring.

Re-requesting dashboard review on new HEAD.

— sent from nimble-crane-490

@briansrls

Copy link
Copy Markdown
Contributor Author

Dashboard relay — reviews #21869 / #21871 (not blocking)

#21869 (claude-opus-4-7) and #21871 (composer-2.5) on 8e9c7c572 are both APPROVE on current HEAD. The relay labeled #21871 “BLOCKING”; artifact verdict is APPROVE.

Spot-check (prior RC #21827): resolve-posture bridge block at tracker :40 cites .github/workflows/ci.yml:266-273; live step name at :266, script at :273. Evidence rows at :89 / :253 unchanged. Prior :249 cite fixed in 8e9c7c572.

Merge readiness: 2 distinct dashboard approvals (claude + cursor), no active REQUEST_CHANGES on HEAD, mergeable clean, CI passing. Holding for operator manual merge per policy.

— sent from nimble-crane-490

@briansrls

Copy link
Copy Markdown
Contributor Author

Review metadata

  • Provider / model: openai-pro / gpt-5-5-thinking
  • Commit: 8e9c7c57 · Trigger: manual
  • Comparison: main @ 993e9e3d ... session/nimble-crane-490-tracker-refresh @ 8e9c7c57
  • Conversation: View conversation

1. Story of the diff

This PR refreshes the v4-done predicate tracker after related lane landings, replacing the old pinned “Tree HEAD spot-check” prose with a live-main refresh note and a cross-link to the Close/Receipt mapping doc at docs/planning/v4-done-predicate-tracker-2026-05-30.md:6. The substantive change is disambiguation: the doc now separates predicate P5 = TestClaim suite passes from the INVARIANTS A3/P5 resolve-posture bridge, so “P5 bridge” no longer reads like it belongs to the TestClaim predicate itself (:19, :23, :40, :89, :253). It also adds a stale TASKS.md:819 close-status snapshot translated into P1–P6 rows, explicitly stating that this is not a TASKS edit and that Self-host/Release remains authoritative until operator refresh (:27-40). chatgpt-review-582196bc-0838-44…

2. Invariant categories

  1. LAYER MODEL — Compliant. This is implementation/planning documentation only; it does not touch substrate, std/, .dag type carriers, dag.rs, or compiler storage. The tracker explicitly keeps TASKS authority separate by saying the new P1–P6 snapshot is “Not a TASKS.md edit” and remains tracker view only at docs/planning/v4-done-predicate-tracker-2026-05-30.md:29.
  2. INVARIANTS.md + modeling-discipline.md — Compliant. Progress-is-dissolution / tracked bridge discipline is preserved: the resolve-posture bridge is named as OPEN, scoped to scripts/v4-bootstrap-resolve-posture-gate.sh plus .github/workflows/ci.yml:266-273, and has a concrete dissolution trigger: “until script + paired CI step deleted per header” at docs/planning/v4-done-predicate-tracker-2026-05-30.md:40.
  3. CODING.md — N/A. The diff adds no Rust code, functions, helper APIs, error shapes, or comments inside implementation code; CODING.md style checks do not materially apply.
  4. TESTING.md — N/A. Docs-only tracker refresh; no executable behavior, runner path, claim evaluator, or test surface changes. No new tests are required for a planning-table clarification.
  5. LOCKED DESIGN DECISIONS — Compliant. The diff does not weaken the pure-bootstrap / zero-hand-authored authority direction. Predicate P6 remains GAP, and its close receipt still requires rebuild-from-.dag plus frozen seed artifact reproduction and dissolution of interim harnesses at docs/planning/v4-done-predicate-tracker-2026-05-30.md:23.
  6. TRACKED vs UNTRACKED DEBT — Compliant. The added stale TASKS.md:819 snapshot is bounded and labeled: it names its source as legacy main@678bb8bbd, says it is stale, says it is tracker-only, and points to future operator refresh rather than pretending to be live authority (docs/planning/v4-done-predicate-tracker-2026-05-30.md:27-40, :255). The live bridge debt is likewise tracked with files, state, and deletion trigger at :40.

2.5. Top-down PM intent review

Compliant. The highest-level intent is not diluted: the tracker still treats all six v4-done predicates as collectively required, keeps P1 broader than a single rung, keeps P4/P6 tied to self-host/fixed-point/reproduction authority, and clarifies that TestClaim P5 is distinct from the A3/P5 resolve-posture bridge (docs/planning/v4-done-predicate-tracker-2026-05-30.md:19-25, :40, :83-89). A worker following this updated tracker is less likely to dispatch the wrong work because “P5” is now reserved for TestClaim suite status while the resolve-posture bridge is separately named as an INVARIANTS A3/P5 scaffold.

3. Verdict

APPROVE. The PR is a scoped planning-doc clarification that improves authority separation and bridge tracking without changing substrate, code, or test behavior. I found no blocking invariant, PM-intent, or debt-tracking regression.

@briansrls

Copy link
Copy Markdown
Contributor Author

Review #21966 / openai-pro (gpt-5.5-pro) — APPROVE, not blocking

Relay: Dashboard flagged #21966 as “BLOCKING”; artifact parser reports unknown verdict. Authoritative text is the posted api-review comment on 8e9c7c57 (provider openai-pro, model gpt-5-5-thinking): APPROVE — docs-only tracker refresh; P5 vs INVARIANTS A3/P5 disambiguation; stale :819 snapshot bounded; live bridge at ci.yml:266-273.

Spot-check vs current tree (8e9c7c572):

No code change required. Merge criteria on HEAD: ≥2 dashboard APPROVE (claude + cursor on 8e9c7c57), plus openai-pro APPROVE above; no active REQUEST_CHANGES; mergeable clean; CI passing. Holding for operator manual merge.

— sent from nimble-crane-490

@briansrls
briansrls merged commit 9029d2e into main May 30, 2026
7 checks passed
briansrls added a commit that referenced this pull request May 30, 2026
After #3983 baseline: refresh header/next-actions; MW-D8 framing;

Co-authored-by: Cursor <cursoragent@cursor.com>
#3973/#3975 landed refs; idle until predicate evidence moves.
briansrls added a commit that referenced this pull request May 30, 2026
…3984)

* WIP: Self-host/Release Manager — authority over T-15, the six v4-done predica

* docs(planning): tracker P1-P6 :819 snapshot + P5 disambiguation

Cross-link Close/Receipt mapping (#3973). Add six-row Close-status snapshot;
disambiguate predicate P5 (TestClaim) vs INVARIANTS A3/P5 resolve-posture bridge.

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

* fix(docs): resolve-posture bridge cites ci.yml:273 not :249

Per review #21827: :249 is M1 rust-emit continue-on-error; bridge step
is v2 → v4 bootstrap resolve-posture gate at :266-273.

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

* docs(planning): post-merge-wave tracker spot-check (MW-D8 idle)

After #3983 baseline: refresh header/next-actions; MW-D8 framing;

Co-authored-by: Cursor <cursoragent@cursor.com>
#3973/#3975 landed refs; idle until predicate evidence moves.

* fix(docs): re-pin resolve-posture ci.yml anchors post-#3983

Per review #22025: bridge step moved to :293-300; :273 is
phase1/nat_semiring. TestClaim structural bridge :290 → :315-319.

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

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant