Repository navigation
docs(close/receipt): v0.1.0 v4 ship-disposition supplement (flavor (iv) — alpha/WIP, no gates) - #4023
Merged
briansrls merged 6 commits intoMay 30, 2026
Conversation
…07-v0-1-0-v4-ship-disposition
…ator flavor (iv)
PM coordination 2026-05-30 with snappy-bee-513 + operator flavor (iv) pick
("alpha v4, no Jun 1 gating, just honest WIP labeling, same for v3").
Per-surface table covers every src/v4/ subtree + src/v3/ bootstrap, each
labeled ship_disposition: ALPHA_WIP (new vocabulary value for the public-tier
axis, orthogonal to the internal closure-axis from PR #3949). engineering_state
tracks maturity per surface using the existing six values.
Public-tier model:
- 'supported' = Rust + TypeScript subset (snappy-bee D-REL-3a/3b authority)
- 'alpha/WIP — not on support contract' = everything else in src/v3/ and src/v4/
Reference HEAD: post-#4017. Cites concrete engineering_state per row including
~7.9k rustc errors on v4 compiler, SG-7 in flight (#4014), R1+R2a/R2b/R3-external
executable receipts (#3972 + #4000), install.dag substrate-shipped exemplar.
§3 explicitly disclaims gating Jun 1, amending RELEASE_v0.1.0.md / TASKS.md,
dispatching workers, or introducing a fail-closed bar. §4 informational
maturation cadence preserves anti-shelfware deadlines from PR #3949 §4
post-tag.
NOT a parallel ledger; PR #4017 and PR #4013 stay as the live maturation
trackers.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
changed the title
briansrls
marked this pull request as ready for review
May 30, 2026 20:27
…+ Go (operator D-REL-3b 2026-05-30) snappy-bee-513 flagged that the supplement caught a 30-second-stale framing: v0.1.0 'supported' is Rust + Python + Go per operator D-REL-3b 2026-05-30, NOT Rust + TypeScript. TypeScript moves to v4 early-support / alpha-only. Fixes: - §1 supported-tier row now names Rust + Python + Go. - §2.3 'supported' references updated; TypeScript (with ecmascript.dag) now explicitly listed as alpha/WIP, not on supported tier. - §2.4 cross-link out clarifies snappy-bee's D-REL-3b authority cites the Rust + Python + Go matrix. Structure unchanged otherwise; per-surface table values stable. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Review metadata
1. Story of the diffThis PR adds a new release supplement, 2. Invariant categories
chatgpt-review-01838c91-d006-43… This is a semantic docs bug: readers can reasonably interpret it as “alpha code is allowed to violate fail-closed,” when the intended release posture appears to be “alpha may currently fail / be unsupported, but failures remain honest and non-fabricating.” Rewrite to something like: “no compile-clean guarantee and no support/regression contract; internal fail-closed discipline remains applicable where the compiler reaches a diagnostic boundary.”
2.5. Top-down PM intent reviewFinding. The highest-level release intent in the PR brief and diff is “alpha/WIP, honest labeling, no arbitrary gates,” not “alpha code may ignore core compiler invariants.” The diff correctly says chatgpt-review-aa3b54d4-99ce-49… As PM, I would reject that wording because it dilutes a must-have invariant into an optional release-support property. The PM-safe version is: alpha/WIP has no advertised compile-clean/support/regression guarantee; current errors are disclosed; fail-closed remains the internal correctness posture for any implemented diagnostic boundary. 3. VerdictREQUEST_CHANGES. The release-disposition structure is otherwise coherent, but the “no fail-closed bar” language crosses from public support policy into invariant dilution. Narrow that wording to “no compile-clean/support/regression guarantee” while preserving fail-closed as internal discipline, and this should be approvable. |
…fixes) (1) Cursor: 'EXECUTABLE_RECEIPT_PRESENT' is not in PR #3949 §1 ratified engineering_state enum. Replaced wherever it appeared (5 sites) with 'PARTIAL_GATE_PRESENT', which is the ratified value that fits when per-claim runners fire but full-corpus / fixture coverage hasn't widened. Keeps the two-axis vocabulary orthogonal and avoids single-authority violation. (2) Cursor: RoundTripClaim eval is no longer 'Deferred in 05_eval.dag'. Verified on origin/main: run_test_claim wires RoundTripClaim to live eval at src/v4/compiler/05_eval.dag:1895-1907 via run_test_claim_round_trip_verdict_runtime + eval_round_trip_claim_input_for_verdict. Updated row to PARTIAL_GATE_PRESENT and rewrote engineering_state cell to cite the live eval; residual maturation is T-38 corpus-runner wiring plus fixture-coverage widening (not eval-arm deferral). (3) Openai-pro: §1 + §3 'no fail-closed bar' wording overreached — was waiving a project invariant (every diagnostic path either fully succeeds or emits typed diagnostic, no fabricated output), not just the public support contract. Rewrote both lines to scope the waiver to compile-clean / support / regression guarantees, and to explicitly preserve the internal fail-closed invariant for implemented diagnostic boundaries in alpha code. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
6 tasks
6 tasks done
5 tasks done
briansrls
added a commit
that referenced
this pull request
May 30, 2026
…cation transcript (zero-overclaim) (#4032) * docs(close/receipt): #4023 follow-on — §1.5 run-status discipline (zero-overclaim) Per operator directive 2026-05-30 (via snappy-bee-513): "i do NOT want ANY overclaim". Adds §1.5 to v0.1.0-v4-ship-disposition.md as the canonical Close/Receipt-lane statement of emit-vs-run discipline. Cross-doc consistency: PR #3991 (D-REL-1) and PR #4025 (SUPPORTED.md) hyperlink here rather than restate. §1.5 contents: - Rule: PROVEN requires demonstrated run-status (passing CI gate, e2e transcript, or executable receipt that validates output); emit success alone is never sufficient. - Why: supported-tier emit lenses routinely produce output that satisfies the emitter but fails python -m py_compile / go build / cargo check / rustc; calling those surfaces PROVEN would be the most user-visible class of overclaim. - Per-target run-validation table (Rust / Python / Go / TS / LeafModelClaim runner / RoundTripClaim) with explicit pass conditions and the fallback (GAP / EXECUTION_NOT_WIRED) when only emit succeeds. - Audit cadence: downstream PROVEN claims subject to retroactive downgrade by this lane if they cite emit-only evidence. - §1.5 self-audit of this supplement's §2 rows: leaf-model rows cite the three CI gates that actually fire on main (ci.yml:243/246/249); no §2 row claims PROVEN. merry-bear-248's verification (cited in PM brief as Python/Go weather-hero emit-OK/run-fail evidence) not yet on main as a tracked file; principle stated abstractly so the citation lands when that artifact is available. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * WIP: Close/Receipt Manager — authority over close predicates, two-axis dispos * docs(close/receipt): #4032 — link §1.5 to landed weather-verification transcript Adds the concrete-evidence-anchor sentence to §1.5 pointing at docs/release/v0.1.0-weather-verification-2026-05-30.md (landed in this same PR). Closes the abstract→concrete loop snappy-bee-513 requested: SUPPORTED.md / D-REL-3b / README per-target claims can now cite a hard file path as the run-status receipt. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 30, 2026
…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
…05-30: v0.1.0 supported = Rust + Python + Go; TypeScript = v4-alpha-only): author docs/SUPPORTED.md as the user-facing support-contract doc for v0.1.0. Location docs/SUPPORTED.md (root of docs/) survives §2 publish-snapshot strip l (#4025) * WIP: Release Jun1 SUPPORTED.md authoring (operator D-REL-3b answered 2026-05- * docs(SUPPORTED): per-target confidence and honesty amendments Incorporate Compiler Spine v2 emit health (HIGH/MEDIUM/MEDIUM-LOW), known-open-bugs table, compile-verified weather hero status, and §2 v4 Rust/TypeScript alpha one-liners per release scope amendment. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(SUPPORTED): anchor weather receipt on public command block Drop cite of scripts/_internal/check-clean-checkout-build.sh from the normative contract; the inline compile + cargo check block is the auditable public receipt. Avoid pointing readers at paths stripped from the publish snapshot. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(SUPPORTED): demonstrated v2 capabilities + weather emit honesty Operator amendments: Go stays in §1 (MEDIUM-LOW); add complexity.dag and interpreter demos with test evidence; document weather Python/Go swap as not yet e2e clean while Compiler Spine emit fixes are in flight. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(SUPPORTED): operator verbatim Py/Go disclaimers, zero overclaim Apply exact per-target disclaimer text; downgrade Python/Go to LIMITED; weather hero notes invalid Py/Go swap; cross-ref PR #3991 and #4023. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(SUPPORTED): refine Py/Go disclaimers per Compiler Spine Replace prior disclaimer text with match-as-expression vs TCO temp-decl (Python) and module/:= scope (Go) failure classes; note v0.1.0 disclaimer commitment and v0.1.1 relaxation ETA. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(SUPPORTED): qualify --dry-run as parsed but not wired in v0.1.0 Remove --dry-run from the §1 CLI support table; document that main.rs does not pass cli.dry_run into handle_run (always dry_run: false). Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.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
Per PM coordination 2026-05-30 with
snappy-bee-513(PR #3991 author) under operator flavor (iv) policy: "we can release an alpha v4 assuming its compilable — and just note the errors/wherever we are — its probably better to release it as a WIP instead of arbitrarily gating it (same with v3)".One new file:
docs/release/v0.1.0-v4-ship-disposition.md.Public-tier model (§1):
supported= Rust + TypeScript subset (snappy-bee D-REL-3a/3b authority).alpha/WIP — not on support contract= everything else insrc/v3/andsrc/v4/.Per-surface table (§2) covers every
src/v4/subtree +src/v3/bootstrap. Every v4 surface is labeledship_disposition: ALPHA_WIP(new public-tier value, orthogonal to the internal closure-axis from PR #3949).engineering_statetracks maturity per row using the existing six values — including~7.9k rustc errorson v4 compiler, SG-7ci.dagrecursion in flight (#4014), R1/R2a/R2b/R3-external executable receipts (#3972 + #4000), andinstall.dagsubstrate-shipped + projection-deferred as the canonical exemplar.Cross-link: snappy-bee owns whether PR #3991 D-REL-1 links this supplement; this PR opens the supplement as a separate artifact per the cross-link coordination shape we agreed.
Does NOT: gate Jun 1, amend
RELEASE_v0.1.0.md, amendTASKS.md, dispatch workers, introduce a fail-closed bar, parallel-ledger any TASKS.md content. PR #4017 (MW-D8 ledger, just merged) and PR #4013 (v4-done burn-down) stay live as post-tag maturation trackers, not pre-tag gates (§4).Test plan
.dag, or Rust seed touched — docs-only.