Skip to content

Board hygiene for merged #940 — arc entry + shipped row #941

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AdaWorldAPI merged 1 commit into from
Aug 12, 2026
Merged

Board hygiene for merged #940 — arc entry + shipped row #941

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .claude/board/LATEST_STATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -855,6 +855,7 @@ Membrane consumers can now pull BOTH halves of a render `classid` BBB-safely fro
| PR | Merged | Title | What it added |
|---|---|---|---|
| *gap note* | — | **#781–#925 are NOT in this table** — carried by the dated sections above + `PR_ARC_INVENTORY.md`. Recorded 2026-08-12 (codex P2 on #930) rather than silently reconstructed; the table had stalled at #780. | — |
| **#940** | 2026-08-12 | W6 lands — vector-sum dipole model VOID by its own anti-vacuity control; stranded stratum empty by CT-F14's filter arithmetic; same-PR sign/units correction round | B0 VOID: single-geo R²=−0.104 (worse than the mean); both controls (permuted P_bow, P_bow rotated 90°) clear the `≤single-geo+0.03` ceiling. B3 stranded (`\|v_storm\|<8 m/s`): n=0 — `displacement_km≥250`/6h implies `\|v_storm\|≥11.57 m/s` for every admitted storm, `E-THE-DISPLACEMENT-FILTER-ATE-THE-STRANDED-STRATUM-1`. Same-PR: codex+CodeRabbit caught a sign-convention bug (`D=-spine(...)`, matching `low_pole_bearing()`'s own flip; verified offline that this leaves R²/B0/B1/B3 unchanged, confirmed on the actual re-run) and a units error (`c_bow` is km⁻¹ not dimensionless; replaced with the dimensionally valid `\|c_bow·P_bow\|` vs `\|D\|` metric — geo≈25%, bow≈9% of `\|D\|`). CT-F17's gate now moot for this model form. |
| **#938** | 2026-08-12 | W5 v2 RUN lands — B2 REVERSES to genuine FAIL, B3's VOID CONFIRMED at full headline scale, both link families now verified | B2: real diffusion resolved (raw rel-L2 vs unsmoothed input = 0.190), operator's own anisotropy = **1.5251 vs the 1.25 bar** (baseline through the clean 3.35σ mask = 1.0046 — the operator alone contributes ~0.52). `domino.rs` gather-design claim REFUTED at this test point. B3: 99.68 % (family A) / 99.56 % (family B) of the QUALIFYING population's control links land on a pure Fibonacci offset (n_qualifying=4 782 017, out of the headline lattice N=7 651 227 — not a 62k sub-sample) — dominated by the two discovered strides 2584=F(18) / 4181=F(19) respectively. Same-PR fixes for 3 more codex findings: family-B histogram was previously uncomputed (now measured + JSON patched); "four orders of magnitude" corrected to ~1.9 (76.9×); B4 downgraded from verdict to explicit descriptive reading (n=19 was dropped without pre-authorization — B4 stays open). |
| **#936** | 2026-08-12 | W5 v1 RUN (B2 PASS / B3 VOID / B4 smooth) — ⊘ SUPERSEDED same day, all three verdicts compromised; v2 CODE fix merged in this PR, v2 RUN/results in flight | Codex found 4 real defects: B3 control subsampled at 250k/band (~74 % self-linked at headline, ratio 0.9996 uninformative); B2's fit floor = input σ (8 iters ≈ inert, "resolved" indistinguishable from "untouched"); bump only 1.72σ from the mask edge (analytic truncation ratio 1.2082 ≈ the measured "1.213 asymptote" — likely the MASK, not the operator); 99.38 % Fibonacci-membership figure was chat-only. Fixed same day, code merged HERE (`106ca605`, verified an ancestor of this PR's merge commit — corrects two overclaims caught by codex P2 on PR #937: the fix was described as "landing in a follow-up PR" when it had already landed, and the histogram artifact as "committed" when only the SCRIPT that produces it had landed — the tracked JSON is still v1's until the v2 run completes): full-band control, V-matched iteration scaling, bump moved to 3.35σ clearance + baseline-through-mask computed, offset histogram now computed by the script. The epiphany's MECHANISM survives (sub-cap 99.38 % measurement was never subsampled) but its "does not exist" phrasing was also softened (codex P2 on #937: 99.38 % ≠ 100 %, one N/one construction ≠ universal proof) — only the headline evidentiary number is retracted; the claim is restated at its actual evidentiary scope, not deleted. |
| **#935** | 2026-08-12 | The validation wave RUNS: T1–T4 + W2s-a executed; `E-A-CONTROL-THAT-CANNOT-LOSE-IS-NO-CONTROL-1` | T2/T3/T4 PASS (68–106× at 200q; tempered 140/140 exact vs golden 124–127/140; 39.0 % naive-rounding collapse). T1 twice-corrected under codex review of its own run: verified-permanent m* = **1.9–2.7× q** (first-crossing 1.0–1.4× was not permanent; q=17: D*(22) back above the ceiling). W2s-a: G1 VOID, G2/G4 FAIL — the CONTROL is degenerate (two translated identical grids are symmetry-uniform, CV ~1e-12; cannot lose any evenness comparison). W5 pre-registered, run in flight at merge. |
Expand Down
45 changes: 45 additions & 0 deletions .claude/board/PR_ARC_INVENTORY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,48 @@
## 2026-08-12 — lance-graph #940 (MERGED) — W6 lands: VOID by its own control, sample-composition lesson, and a same-PR sign/units correction round

- **Added.** `comet_tail_w6.py`/`.json` — full detail already recorded in
the RUN entry below (unmerged-PR content composed in place per the
PR-878 allowance, since it was written and pushed before this PR
existed). This entry records only the merge + what changed AFTER
that entry was first drafted.
- **Locked — a same-PR sign/units correction round, caught by codex +
CodeRabbit before merge.** Two real findings, both fixed and
verified: (1) `spine()`'s raw coefficient points toward the storm's
HIGH side (increasing residual), not the low pole `P_geo`/`P_bow`
are built to point toward — `D = -spine(...)` now, matching
`low_pole_bearing()`'s own `(ph + pi) % (2*pi)` convention. Verified
offline BEFORE committing: negating the fit target flips
`c_geo`/`c_bow`'s signs exactly and leaves R² (hence every B0/B1
verdict) and B3's residual-bearing resultant completely unchanged —
confirmed bit-identical on the actual re-run. (2) `D`/`P_geo` are
[Pa/km], `P_bow` is [Pa], so `c_geo` is dimensionless but `c_bow`
carries km⁻¹ — the original "`c_bow`≈0, no measurable weight" claim
inferred absence of correlation from a raw, not-comparable
coefficient magnitude. Fixed with a dimensionally valid metric,
`|c_bow·P_bow|` vs `|D|`, both in Pa/km: geo contribution ≈25 % of
`|D|`, bow contribution ≈9 % — modest, not "no weight." Two
Comment on lines +22 to +23

@coderabbitai coderabbitai Bot Aug 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Preserve the statistical qualifier for the contribution metric.

Both summaries omit that the source RUN entry reports mean contribution percentages.

  • .claude/board/PR_ARC_INVENTORY.md#L22-L23: add mean or on average before the 25% and 9% figures.
  • .claude/board/LATEST_STATE.md#L858-L858: apply the same qualifier or state the exact aggregation used.
📍 Affects 2 files
  • .claude/board/PR_ARC_INVENTORY.md#L22-L23 (this comment)
  • .claude/board/LATEST_STATE.md#L858-L858
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.claude/board/PR_ARC_INVENTORY.md around lines 22 - 23, Preserve the
mean-statistical qualifier for both contribution summaries: update
.claude/board/PR_ARC_INVENTORY.md lines 22-23 to identify the 25% geo and 9% bow
figures as mean or average values, and update .claude/board/LATEST_STATE.md line
858 with the same qualifier or the exact aggregation used.

additional CodeRabbit robustness findings also fixed: per-storm
fetch/compute steps now wrapped in try/except with an `ERROR
t0=...` tag-file record before re-raising (§0's "record it and
stop" rule was previously unenforced by code); `load_completed()`
now runs before the tag file's `START` line, not after.
- **Locked — the headline finding survives both corrections
unchanged, and that was verified, not assumed.** B0 VOID, the
vector-sum model as specified is disconfirmed on this sample, the
stranded stratum is empty by CT-F14's own filter arithmetic — none
of these depend on sign or units. What changed is only the
supporting narrative around `c_geo`/`c_bow`'s reported values,
corrected everywhere it had propagated (`weather-w-probes-v1.md`,
`EPIPHANIES.md`, this file's RUN entry) with dated correction
blocks, prior text kept for the record.
- **Confidence.** High — every corrected number re-derived from the
actual re-run's committed JSON, with the sign-flip's R²-invariance
property verified by a standalone offline test before the fix was
even committed.

**Status:** MERGED (`adab8739`). Branch `claude/jirak-math-theorems-harvest-rfii13`
→ `main`. Probe + docs — zero product code.

## 2026-08-12 — the W6 dipole-deconvolution RUN lands — VOID by its own anti-vacuity control, plus a reusable sample-composition lesson (PR pending)

- **Added.** `comet_tail_w6.py`/`.json` — the report §10.2 vector-sum
Expand Down