#929 hygiene + open-review sweep of #920–#930 (3 frozen figures corrected, append-only audit replaced) + report §10 + weather-w-probes-v1 (MIXED) - #930
Conversation
Post-merge board hygiene per the Mandatory Board-Hygiene Rule. #929 was a mixed PR (2 probes + report sections + epiphany), so its entry records the non-hygiene half: * CT-F16: the steering rescue failed both pre-registered bars; the level sweep is monotone toward the SURFACE (best 850 hPa). The ladder survives as a measurement; its operational reading is dead. * F16c's rotated control scored 0.684 = CT-F14's headline -- the sign test could not distinguish the real referent from a wrong one at n=19. Rule banked: a control's score is the floor any rate-headline must clear. * The circular resultant resolves the same 19 rows at p=0.0050, estimates the offset (-30.2 deg) instead of penalizing it, and separates the rotated control by 100.3 deg. Post-hoc, instrument demo, not a promotion -- but sign-consistency numbers are retired as verdict-grade instruments across the arc. All 13 figures in the entry verified against the committed JSONs BEFORE landing (13/13 exact -- the #927 self-verification, now standard practice). Append-only audit: zero removed lines across both board files (pure prepend). THIS PR IS PURE HYGIENE -- no type, plan, deliverable, epiphany or code. Per the termination clause it generates no further obligations; the chain stops here. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
|
Warning Review limit reached
Next review available in: 33 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_19cced9d-14e4-47b8-8ebc-7e45ff521857) |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4b80db503e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - **CT-F16 `[G]`:** the steering-level moderator FAILED both pre-registered bars on CT-F14's own 19 storms (0.579 vs 0.70; residual +28.4 % wider; level sweep monotone toward the surface, best 850 hPa). §9.2's "single most promising fix" is superseded in place. The height ladder survives as a measurement; its operational reading died. | ||
| - **The instrument calibration `[G]`:** a 90°-rotated control scored **0.684 = CT-F14's headline**. At n=19 the sign test separates from a wrong answer only at 14/19. **Rule: attach a deliberately-wrong referent to any rate-headline; its score is the floor.** | ||
| - **The replacement instrument:** circular resultant (R̄, μ, Rayleigh) resolves the same rows at **p=0.0050** (sign test: 0.0835), estimates the offset (**−30.2°±36.5°**) instead of penalizing it, and makes the rotated control visible (μ shifted 100.3° at identical R̄). Post-hoc — instrument demo, NOT a promotion. **Sign-consistency numbers are no longer verdict-grade anywhere in this arc.** |
There was a problem hiding this comment.
The committed result does not show an identical R̄ for the surface referent and rotated control: comet_tail_resultant_instrument.json records 0.516448 for surface and 0.342633 for the control. The identical-R̄ comparison is between steering and its 90° rotation, whose μ values differ by 90°, whereas the stated 100.3° separation compares the control with surface. This sentence conflates those two comparisons and leaves the permanent board ledger with a false experimental result.
Useful? React with 👍 / 👎.
| @@ -1,3 +1,13 @@ | |||
| ## 2026-08-12 — lance-graph #929 (MERGED) — steering rescue dead; sign test retired as primary instrument | |||
|
|
|||
| ### Current Contract Inventory — no new types (2 probes + report §5.12/§5.13 + 1 epiphany) | |||
There was a problem hiding this comment.
For this post-merge hygiene commit, CLAUDE.md:330-334 requires updating both the LATEST_STATE.md shipped-PR table and PR_ARC_INVENTORY.md. This change adds only a Current Contract Inventory section; the actual “Recently Shipped PRs” table at lines 840-844 remains topped by #780 and contains no #929 row, so the commit leaves the required merged-PR index stale.
Useful? React with 👍 / 👎.
…h, fixed in all three homes Codex P2 on #930: "identical R-bar with mu shifted 100.3 deg" fused two different comparisons. Identical R-bar belongs to steering<->rotated (0.343 = 0.343, mu shifted exactly 90 -- rotation preserves concentration by construction); the 100.3 deg separation belongs to surface<->rotated, where R-bar is NOT identical (0.516 vs 0.343). The composite was false in all three homes: LATEST_STATE, the #929 arc entry, report SS5.13. Stated correctly the finding is STRONGER -- the control separates from surface in BOTH channels. Unmerged board entries composed in place (append-only rule's unmerged-PR allowance); the merged report gets a dated correction note. Lesson banked: the 13/13 figure verification checked every NUMBER and still missed this -- a relation between two individually correct numbers can be false. Verify comparative claims AS claims: every "identical/same/larger" must name both operands, and the check must evaluate the relation. Also codex P2 #2: the LATEST_STATE shipped-PR table had stalled at #780. Added #926-#929 rows plus an explicit gap-note row for #781-#925 (carried by PR_ARC_INVENTORY) -- honest gap, not silent reconstruction of ~150 rows. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
…r briefs with stranded rescue Operator ask: "auf product lead level dokumentation erweitern und die followup testreihen für sonnet agents runterbrechen zum token sparen … und stranded rescue." - COMET_TAIL_REPORT.md §10 — the product-lead program: 10.1 measurement standard (circular resultant primary, control scores are floors, comparative RELATIONS verified as claims), 10.2 dipole vector-sum model incl. the STRANDED regime (v_rel = v_storm − v_env covers cut-off lows natively), 10.3 corridor α physics, 10.4 queue-and-bow anchors, 10.5 sunflower/facet/spiral-ADI substrate with [H] flags, 10.6 roadmap, 10.7 worker model + stranded rescue. - .claude/plans/weather-w-probes-v1.md — §0 verbatim-paste worker preamble (iron rules, fetch()/t-guard/wrap_deg/circular() code, controls-FIRST with VOID rule, checkpoint-per-storm + resume-skip + exec-runs heartbeat = the stranded-rescue protocol); full briefs W5 / W2s-a / W6; outlines W2s-b / W7; audit-gated CT-F17 spec; execution order + token budget. - Board hygiene per the new-plan rule: INTEGRATION_PLANS.md prepend + STATUS_BOARD.md rows D-W5 / D-W2sA / D-W6 / D-W2sB / D-W7 / D-CT-F17 (all Queued; F17 gated on W6 + mandatory independent adversarial audit). Exploratory tier ACTIVE; verdict tier gated. No probe was run in this commit. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
…ng, and the append-only audit could not fail Operator: "930 has comments / check also previous 5 / if you want go back another 5." All 68 review comments on #920-#930 enumerated and checked against the TREE, not the merge. Depth is non-uniform and said so: #922-#930 finding-by-finding; #920 (27) and #921 (5) spot-checked on P1/governance only (both clean), ~30 older findings there left explicitly UNVERIFIED. Clean: #922/#924/#925/#929 zero comments; all 27 of #926's findings fixed in the tree (equal-budget grid_pts + regenerated E2 JSON, seam-wrapping subgrid_min, find_center->None, F7d 35->40, CT_F12 NO-VERDICT, persisted storm metadata, np.roll longitude, __file__-relative write, net-decay E6, the 93-97%->90.9-94.3% headline); #923's plan-status P2 resolved. Three open, all frozen in append-only ledgers, all corrected in NEW entries: 1. "+92.76 Pa moves R2 in the 5th decimal" is refuted by the report's own carve table 15 lines above it: carve A's +92.76 Pa moved R2 0.9212->0.9129 (0.0083, THIRD decimal); carve D's +1.59 Pa moved it 2.4e-06 (SIXTH). The var() BUG was blind at every magnitude; the STATISTIC is near-blind only in the single-digit-Pa regime -- which is exactly where "lossless" was claimed. 2. "10 probe scripts with committed JSON" undercounts: 15 .py added, 11 with a committed .json. 3. "+13/-0, +10/-0, +0/-0": measured +13/-0, +17/-0, and EPIPHANIES absent from the net diff -- it was +1/-1 at 0f9e6bc (the in-place edit), zeroed by the revert. The +0/-0 was a revert artefact, not evidence of purity. And the audit METHOD is replaced: zero-deletions proves ADDITIVE, not PREPEND. The suffix check (new.endswith(old)) proves it. Both halves measured before banking: a constructed end-append scores zero-del=True/suffix=False; a true prepend True/True. It also fires on THIS PR (LATEST_STATE suffix=False at +15/-0) -- correctly, since #930 inserts table rows mid-file and composes an unmerged entry in place. A False is a demand for justification, not a verdict. Same defect shape as #930's relation error, twice in three days: two individually-true numbers asserted of one pair when each belongs to a different one. A figure-by-figure check cannot catch it; the relation must be evaluated as a claim. Already standing in report SS10.1 and the worker preamble of weather-w-probes-v1 (both verified present, not assumed). Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
#930 merged as MIXED (started as #929 hygiene, grew into the #920-#930 open-review sweep + report SS10 + weather-w-probes-v1 worker briefs, per its own twice-corrected title/body). Arc entry + LATEST_STATE shipped-PR row added. The #928/#929 shipped-table rows are left untouched (superseded by the sweep entry's correction table, not edited in place -- append-only). Suffix-checked before commit: PR_ARC_INVENTORY suffix=True (pure append); LATEST_STATE suffix=False (a table-row mid-file insert, the justified case the sweep entry itself named). Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
The previous commit's message claimed "STATUS_BOARD rows D-W2sA + D-GVT-T1 updated" -- only D-W2sA had actually been edited; D-GVT-T1 still carried the first-crossing 1.0-1.4x range that codex P1 falsified. Caught by verifying the commit message's own claims against the tree immediately after pushing (the #930-arc lesson: prose and patch are written in the same breath and only the patch is checked by anything). Row now carries the verified-permanent 1.9-2.7x figure with both codex fixes named. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
Why this exists — and why the title keeps growing
This PR started as pure hygiene for merged #929 and its first body said "the chain stops here." That stopped being true twice, so the description is corrected rather than left to a reviewer (#927's lesson). It is now MIXED and owes its own arc entry on merge.
1. Codex P2s on this PR — both fixed (
25ab52b6)2. Open-review sweep of #920–#930 (
15f2e32f)All 68 review comments enumerated and checked against the tree, not the merge. Depth is non-uniform and stated as such: #922–#930 finding-by-finding; #920 (27) and #921 (5) spot-checked on P1/governance only — both clean (
p1_noise_floor.pycarries an explicitSUPERSEDED by p1_ci_vs_floor.pyheader fixing the decoded-error framing and the 255-vs-256 bucket-edge bug; merged #917's entry has exactly one commit in its whole history, so it was never mutated) — leaving ~30 older findings there UNVERIFIED, recorded as such.Clean: #922 / #924 / #925 / #929 have zero review comments. All 27 of #926's findings are fixed in the tree — verified individually:
grid_ptsreturns exactlynwith the E2 JSON regenerated at 64/64/64 · 256/256/256 · 1024/1024/1024;subgrid_minwraps longitude;find_centerreturnsNoneon an empty mask; F7d tests>= 40.0;CT_F12emitsNO-VERDICT-INSUFFICIENT-N; storm metadata persisted;d_dxusesnp.roll;go_territorywrites__file__-relative; E6 requires a net decline; the 93–97 % headline superseded. #923's plan-status P2 resolved.Three were genuinely open, all frozen in append-only ledgers, all corrected in NEW entries:
.pyadded, 11 with a committed.json0f9e6bcd(the in-place edit), zeroed by the revertThe R² one matters beyond the digits: the sentence fused carve A's magnitude with carve D's insensitivity. The true statement is sharper — the
var()BUG was blind at every magnitude (that is what hid +92.76 Pa), while the STATISTIC is near-blind only in the single-digit-Pa regime, which is exactly where "lossless" was claimed on four-decimal agreement. The banked doctrine (RMSE + mean bias in Pa beside every R²) is unchanged.And the audit method itself is replaced. #928 banked "zero removed lines proves a pure prepend" as reusable. It does not — zero deletions proves additive, not prepend. The property is proved by the suffix check (
git show origin/main:Fmust be a suffix ofgit show HEAD:F). Both halves measured before banking, per the falsifiability rule: a constructed end-append scoreszero-del=True, suffix=False— caught only by the new test; a true prepend scoresTrue/True. It also fires on this PR (LATEST_STATEsuffix=Falseat+15/−0) — correctly, because #930 inserts shipped-PR rows mid-file and composes an unmerged entry in place (the PR-878 allowance). AFalseis a demand for justification, not a verdict; the old test could not even ask.3. Report §10 + worker briefs (
755a3c96)COMET_TAIL_REPORT.md§10 — measurement standard (circular resultant primary; a control's score is the floor; relations verified as claims), the dipole vector-sum model incl. the stranded-storm regime (v_rel = v_storm − v_envcovers cut-off lows natively), corridor α physics, queue-and-bow anchors, sunflower/facet/spiral-ADI substrate, roadmap, worker model..claude/plans/weather-w-probes-v1.md— Sonnet worker briefs with a verbatim-paste §0 preamble (iron rules, controls-FIRST with VOID rule, stranded rescue: per-storm checkpointing to<name>.partial.jsonl+ resume-skip +exec-runs/heartbeat). Full specs W5 / W2s-a / W6; gated W2s-b / W7; CT-F17 gated on W6 and a mandatory independent adversarial spec audit.What the #929 entries record (unchanged)
[G]— the steering rescue failed both pre-registered bars (0.579 vs 0.70; residual +28.4 % wider; sweep monotone toward the surface, best 850 hPa).[G]— a 90°-rotated control scored 0.684 = CT-F14's headline. A control's score is the floor any rate-headline must clear.Queued (operator go-ahead pending)
Wave 1 (parallel): W5 spiral-ADI anisotropy · W2s-a golden-vs-grid pairing on the real cos-lat metric · W6 two-component (geo + bow) deconvolution incl. stranded stratification. Gated: W2s-b, W7, CT-F17 (fresh 1959–1979 sample; V-test p<0.05 ∧ R̄≥0.35; audit mandatory) · C-register climatological calibration.
🤖 Generated with Claude Code
https://claude.ai/code/session_01CcpLeEC3XK8Eye53GKBVvi
Generated by Claude Code