Skip to content

records(L145): import #973, s(k^2 - 5) = k for every k >= 7, as T-298 (reported, V0/C1) - #974

Merged
jlevy merged 13 commits into
mainfrom
claude/bold-ritchie-xo28us-l145
Nov 14, 2026
Merged

jlevy merged 13 commits into
mainfrom
claude/bold-ritchie-xo28us-l145

Conversation

@jlevy

@jlevy jlevy commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

What this branch cost

This branch is the import of #973 (lane L145, bead think-2vgx): Mohsen Khalili and Sara
Gharabaghi’s $s(k^2 - 5) = k$ for every $k \ge 7$, taken through triage, retention, a
time-boxed replay and registration as T-298, with the blind stage 4 review (lane L144,
think-h10k) merged and mapped. It took about 3.5 hours of agent wall on a four-core
container and about 2.5 CPU-hours of replay at nice -n 19, two jobs at most, inside the
lane’s box of about 4; the review lane spent about 3.1 more. It does not run the full
replay, priced at about 145 to 180 CPU-hours (up to about 320) and held for the owner on
think-0h7r, nor build the Lean reduction, nor review zmx2’s area-density and
first-order lemmas, which is held on think-kn13.
The senior review’s fixes (lane L147) took about 0.8 hours of agent wall to the push and
under 1 CPU-hour, nearly all of it the edit and records tiers, the touched tests and two
paper-render comparisons.

New Results and Their Significance

Result Claim Rungs Status Significance
T-298 $s(k^2 - 5) = k$ for every integer $k$ from 7 up; scope $n = 44, 59, 76, 95, 116, 139, 164, 191, 220, 251, 284, 319$ ($k = 7$ to $18$) V0/C1 reviewed, a report S4 drafted as a claim: a bound family, as T-064 and T-081 are, that would settle eight open cases ($k = 11$ to $18$), with a new argument, the Tight-Tile Lemma

Results and Dispositions

Work or result What was established Evidence Why it stopped Disposition and follow-up
Triage and retention of #973 The source pinned at its one commit 2c0b1b9, 465 of 466 files retained (MIT, README adds CC BY 4.0); tight_tile/cov.tar.xz (8.7 MB) pinned by digest, over the per-blob ceiling; the board’s digest the issue’s. Daniel’s zeromargin.py 3cb95fb7 at 659ee62, which no packet held, retained Packets moh63-dev-k2m5-family-2026-11-13, evand-square-packing-2026-10-24 Complete retire-success; hosted release of cov.tar.xz owed with think-0h7r
Fast verify.sh Passed on the retained bytes: sanity, locality on four boards, the sweep audit, root 9632 and the coverage, from the source’s records receipts/verify_fast.log Complete retire-success (a diagnostic of the records)
zmx2 at 659ee62 Rebuilt from retained bytes to the 31 October binary; the source’s patch is one line of zmx2.rs, output only receipts/zmx2_build.log, receipts/zmx2_print_all_build.log Complete retire-success
zmx2 sample cert0 and 30 of 55 columns, 6,600 of 12,100 roots, every census and listed box equal to the source’s; 8.8% of the sweep’s recorded CPU receipts/zmx2/, receipts/compare.json.gz, E-khalili-973-replay-sample Time box continue under think-0h7r (the other 25 columns)
Root 9632 Re-run whole: the patched zmx2 dump (6,850 boxes) and qx2_zm.py (83 boxes) equal the source’s byte for byte; check_9632.py on this run’s outputs says ROOT-9632-CLOSED. The dump needs --uncert-cap 100000000, which the release does not record receipts/r9632/ Complete retire-success; a question for the authors
Tight-Tile sample 26 of the 323 jobs, 22 strips and 4 lines across all three depths and both signs, all among the cheapest: every job ALL-OK, every chart line equal to the recorded output’s (the shipped run_tt.py prints a K field the recorded outputs lack, so an earlier version wrote them) receipts/tight/, E-khalili-973-replay-sample Time box continue under think-0h7r
Controls zmx2 refuses both scaled boards at root (15, 36); qx2_zm.py on the scaled root-9632 cover leaves the source’s 87 boxes, 3 meeting zmx2’s, NOT-CLOSED; locality_check.py refuses the mutated $\mu_{12}$ (176 windows); the Tight-Tile checker certifies the real board’s control region in 155 cells and refuses the moved-segment board (443 cells within the 2,000-cell cap, 83 of them at the cap; the counts do not match the paper’s, the review’s F8) receipts/controls/, tests/test_replay_k2m5_family.py Complete retire-success
Stage 4 review (L144, blind) Accepted as reviewed, no blocking defect. Its own exact programs (independently re-implemented after reading the producer’s code; the record does not call them clean-room) decide the mass and family, Lemma 7’s premises, the whole $\theta = 0$ face, the coverage of the 75 tight-tile roots and root 9632’s closure; the Tight-Tile Lemma re-derived and its code read; its replays of the source’s code, registered as E-khalili-973-review-replay-sample, agree with this lane’s wherever both ran, the Tight-Tile job d2.5_s-1_line_1.6_2.5 among them. F1 (major): zmx2’s area-density and first-order lemmas unreviewed here. F2 (major): the Tight-Tile Lemma has one implementation and no full replay. Eight new counts, not nine. It ran at tbd-strong, not the tbd-strong-max tier the runbook asks for docs/project/reviews/review-2026-11-14-khalili-gharabaghi-k2m5-973.md, E-khalili-973-review-partial-checks, E-khalili-973-review-replay-sample, V-khalili-973-review-check Complete retire-success: mapped, T-298 to C1
F1, zmx2’s lemmas Not reviewed think-kn13 A review lane at the strongest tier, about 4 to 8 hours of agent wall, under 1 CPU-hour defer-dependency: the owner’s word; recorded beside C3, not a condition of it
Full replay and Lean build Priced by both lanes: about 145 to 180 CPU-hours on the review’s random-job Tight-Tile factor, up to about 320 if the unsampled large Tight-Tile jobs run at the source’s speed; it reruns the one Tight-Tile implementation, and no bead tracks a second (F2); the Lean build on a host with at least 24 GB think-0h7r Above the lane’s box and the 40 CPU-hour item cap defer-dependency: the owner’s budget

Changes by Purpose

Area Result Principal files or interfaces
Source custody Both packets, with acquisition records, READMEs (the k2m5 one with the review’s summary and nine questions for the authors) and the replay receipts; bibliography keys [Khalili Gharabaghi k2m5 family 2026-11-13] and [evand square-packing 2026-10-24] packing/resources/web/moh63-dev-k2m5-family-2026-11-13/, packing/resources/web/evand-square-packing-2026-10-24/, resources/bibliography.yaml, resources/README.md, frontier/source-coverage.yaml
Replay tooling devtools.replay_k2m5_family: stage the packet (the pinned-only cov.tar.xz held to its digest, allowlisted as a download boundary), build zmx2 and the patched copy, run verify.sh, columns, root 9632, controls and tight-tile jobs under receipts, and compare with the source’s records; a test that holds the receipts packing/devtools/replay_k2m5_family.py, packing/tests/test_replay_k2m5_family.py, packing/devtools/integrity-ceremony.yaml
Stage 4 review The L144 review and its packet, merged; mapped in the document map, as the reports’ external_review, in T-298’s reviews, as a verifier with its independence record and as a partial-checks evidence entry; its §13, which repeated §11, trimmed with a dated note docs/project/reviews/review-2026-11-14-khalili-gharabaghi-k2m5-973.md, packing/resources/web/khalili-gharabaghi-k2m5-973-review-2026-11-14/, docs/project/document-map.yaml
Register and cases T-298 at V0/C1, three report evidence entries and the review’s, verifier records; $n = 116$ to $319$ reported proved at $k$, verified lanes unchanged; $n = 95$ notes the second route; T-081 and T-191 gain a sentence each frontier/results.yaml, frontier/evidence.yaml, frontier/verifiers.yaml, frontier/n-095.md and n-116.md to n-319.md
Requests #973’s entry, with its claim map, beads, validation beads and the draft reply campaign/result-requests.yaml
Pins and views Reported-open corpus counts (233 to 225), the closed form’s raised lanes (153 to 145), curated print credits, the other-projects card, register, inventory, status, verifiers, synopsis, URL registry, research tables, T-007 audit, contributor spans (new spans unresolved for the owner’s identity review); a no-public-change record (the explainer’s register count only) src/sqpack/cli/validate.py, tests/test_validation_cli.py, tests/test_apply_closed_form.py, atlas/known-best/credit-attributions.json, devtools/site_resources.py, frontier/*.md, SYNOPSIS.md, release-records/no-public-change/2026-11-14-bold-ritchie-l145-973-t298.yaml

Review Fix (L146)

Lane L147 (bold-ritchie-l147) applied every B and S item of the senior review L146 and
the notes it asked for, in 4471544e0; then merged main at b526521e4 (#975, the
browser cache keyed on the Ubuntu release, for the two WebKit failures) and re-pinned.

  • B1: the record no longer calls the review’s programs clean-room: T-298’s
    composition, the three report entries’ review notes, the partial-checks entry, the
    request notes, the packet README and the row above say “own exact programs
    (independent, not clean-room)”; §13 of the review gains a dated note on why its own
    word differs from V-khalili-973-review-check’s.
  • B2: all nine case files carry the review, F1 on think-kn13, F2 and the held
    replay. B3: the News draft below, and the S4 box ticked.
  • S1–S8: as given: §13’s F1/F2 split; the controls sentence with F8; 83 of the 443
    refusals at the cap; the tool’s custody change dated (8784343, 72db934, OR-16)
    in the README, the label and the verifier summary; F2 not wholly think-0h7r’s, in
    next_rung and think-2vgx’s notes; the score left as the import lane’s draft; the
    no-public-change record at V0/C1, with compare_paper_renders re-run (still only the
    explainer’s register count); and the receipts-equal-records test.
  • S9: E-khalili-973-replay-sample (this lane’s runs) and
    E-khalili-973-review-replay-sample (the review’s), each replayed-here,
    same-implementation, coverage sample of 459 runs (59 and 18), cited by T-298, the
    request and the nine cases.
  • Notes: N1 (headline in T-081’s words, with k plain so the results page keeps its
    projection under 1,700,000), N2, N3 (145 now follows: the price uses the review’s
    random-job Tight-Tile factor), N4, N5, N6, N7, N8, N9, N10, N11 (the review ran at
    tbd-strong, said wherever the record states its tier), N12 (the cropped sum is
    weight_sum; compare.json.gz rewritten from the same receipts, that key alone
    changed) and N14. N13 needed nothing.

Validation

  • Local, lane L147: at 4471544e0, the edit tier (packing-validate --edit) passed 71 of
    71 steps, its full basedpyright run at 0 errors; on the merged tree, the records tier
    (--records --jobs 3) passed 55 of 55. check_requests (206 issues, every id
    resolves), check_results (298 results), site_urls --check,
    check_release_impact --base origin/main (every candidate has a disposition),
    check_integrity_ceremony, retained_data check on the packet and
    check_added_blobs --base origin/main (2.7 MB thin pack) pass. pytest on
    test_known_best_atlas.py, test_overview.py, test_result_status.py,
    test_apply_closed_form.py, test_validation_cli.py, test_replay_k2m5_family.py
    and test_t007_consumer_audit.py, then the first two again after the headline and
    credit fixes: all pass; test_release.py and test_pages_workflow.py after the merge
    and pin: 68 passed. The results page projects 1,699,269 bytes (298 results plus 20 at
    the 4,587-byte P90 row) against 1,700,000. compare_paper_renders against
    0db247de7: only the explainer’s HTML and Markdown differ, by the register count.
  • Hosted: the run at 0b856c746 is on this pull request.

Documentation and Replanning

  • Documentation review: the packet README states what ran, what did not, the review’s findings, the reconciled price and the authors’ questions; the reader-facing changes are the case records and generated views.
  • Selected next entry: post the reply on s(k² − 5) = k for every k ≥ 7 (family k ≥ 10 by one periodic measure; k = 7, 8, 9 known) #973 from think-2vgx’s Reply draft once this merges (T-298 at V0/C1, the review’s F1 and F2, the held replay and lemma review, and the merged questions); the earlier Acknowledgement draft there is superseded.
  • Deferred candidates: the full replay and Lean build (think-0h7r, owner budget; a pilot of two or three of the largest Tight-Tile jobs would narrow the price); the review of zmx2’s lemmas (think-kn13); a hosted release of tight_tile/cov.tar.xz before receipts compared with it are cited; a second implementation of the Tight-Tile Lemma, which no bead tracks (F2).
  • PR has exactly one S1–S5 label, an editorial rationale and its News/changelog disposition: S4 (the S4 label), T-298’s draft score as a claim, which the stage 4 review did not score in its text; News: the draft under News below, for the changelog step after the merge. intake applied.

News

T-298 is registered at S4, so this pull request drafts its News item before the merge
(result-import.md, “Announce a Significant Result”). The entry is below, to land in
packing/site-changelog.yaml after the merge, dated the merge day and naming this pull
request by its retained merge commit; render_changelog needs the merged delivery row
first.

Khalili and Gharabaghi Report s(k² − 5) = k for Every k ≥ 7 (the merge day). Mohsen
Khalili and Sara Gharabaghi report that $k^2 - 5$ unit squares need a square of side
$k$ for every $k \ge 7$. One periodic family of measures reduces every $k \ge 10$ to a
single finite statement on an $11 \times 11$ board, decided with Evan Daniel’s interval
checkers and a new Tight-Tile Lemma where box subdivision stalls, and a Lean
development carries that statement to every $k \ge 10$. New to the record are eight
open counts, $n = 116$ to $319$ ($k = 11$ to $18$). T-298 is reported at V0/C1: a
stage 4 review here found no blocking defect, and no verified bound moves until the full
replay and the Lean build run.

The entry as YAML
- id: khalili-gharabaghi-k2m5-family-reported
  date: 'YYYY-MM-DD'  # the merge day of #974
  title: Khalili and Gharabaghi Report s(k² − 5) = k for Every k ≥ 7
  significance:
    score: 4
    rationale: >-
      T-298, scored S4 as a claim by the import lane: a bound family, the deficit-5 case
      of Friedman’s conjecture, that would settle eight open counts, n = 116 to 319
      (k = 11 to 18), with a new argument, the Tight-Tile Lemma, as T-064 and T-081 are
      S4 families. The stage 4 review stated no score. Reported at V0/C1: limited by the
      held replay, the held lemma review and the review’s F1 and F2.
  topics: [optimality, lower-bound]
  categories: [records]
  pull_requests: [974]
  issues: [973]
  result_ids: [T-298]
  summary: |-
    Mohsen Khalili and Sara Gharabaghi report that $k^2 - 5$ unit squares need a square
    of side $k$ for every $k \ge 7$. One periodic family of measures reduces every
    $k \ge 10$ to a single finite statement on an $11 \times 11$ board, decided with
    [Evan Daniel](packing/contributors/people/evan-daniel.md)’s interval checkers and a
    new Tight-Tile Lemma where box subdivision stalls. New to the record are eight open
    counts, $n = 116$ to $319$. T-298 is reported at V0/C1.
  details: |-
    - $k = 7$, $8$ and $9$ rest on certificates the record already holds (T-252, T-066
      and T-184), and $s(95) = 10$ is Greff’s T-191. At $n = 116$ to $319$ the reported
      lower bounds move to $k$; the verified ones are unchanged.
    - What ran here, about 2.5 CPU-hours: the source’s fast checks, 30 of the 55 columns
      of Daniel’s `zmx2` sweep, root 9632 with both checkers and 26 of the 326 Tight-Tile
      runs, each equal to the source’s records, and the source’s controls, refused as
      reported. That is a diagnostic, not a replay. The full replay, about 145 to 320
      CPU-hours, and the Lean build are held for the owner.
    - A stage 4 review by a separately prompted Claude agent, at the strong tier rather
      than the strongest the runbook asks for, found no blocking defect and two major
      findings: `zmx2`’s area-density and first-order lemmas, on which most of the
      board’s poses rest, have no review in this record (F1, held), and the Tight-Tile
      Lemma has one implementation and no full replay (F2).
    - The paper says the search, the certificate, the Tight-Tile checker and its proof,
      and the verification runs were produced with Claude (Anthropic) under the authors’
      direction. It builds on Daniel’s linear program, format, checkers and Lean
      reduction. Not peer reviewed.
  artifacts:
    - kind: result
      label: Current T-298 record
      target: https://squaremath.org/result/t-298.html
  references:
    - label: Source, retention and the checks made here
      target: packing/resources/web/moh63-dev-k2m5-family-2026-11-13/README.md
    - label: Stage 4 mathematical review
      target: docs/project/reviews/review-2026-11-14-khalili-gharabaghi-k2m5-973.md

Limits

T-298 is a reviewed report: nothing here replays Valid11 in full or builds the Lean
reduction, so no verified lower bound moves and $n = 116$ to $319$ stay open in their
verified lanes. The two lanes’ samples show that the source’s programs reproduce their
recorded outputs where they ran; zmx2’s area-density and first-order lemmas are unread
by any review here (F1), and the Tight-Tile Lemma rests on one implementation (F2). The stage 4 review ran at tbd-strong, not the tbd-strong-max tier the runbook asks for. This
branch records #973; the reply on the issue follows the merge.

https://claude.ai/code/session_01E8g3iMDhVT21veLdEABoxV


Generated by Claude Code

…as T-298 (V0/C0, S4 drafted)

Stages 1 to 3 of the #973 import (think-2vgx) and a time-boxed replay.

Retention. moh63-dev/k2m5-family at its one commit 2c0b1b9 (2026-11-13T23:50:51Z),
465 of 466 files, MIT (the README adds CC BY 4.0 for text and data); the board
sol_exact_box11.txt is the issue's d259fed5...12099 and every SHA256SUMS_ALL line holds.
tight_tile/cov.tar.xz (8.7 MB) is pinned by digest only, over the per-blob ceiling; a
hosted release is owed with think-0h7r. evand/square-packing at 659ee62: zeromargin.py
3cb95fb7, which qx2_zm.py imports there and no packet held, retained in
evand-square-packing-2026-10-24, the other checker files pinned to earlier copies.

Replay, about 2.5 CPU-hours at nice 19, two jobs, by the new devtools.replay_k2m5_family
(receipts in the packet): the source's fast verify.sh passed on the retained bytes; zmx2
e2bb84e9 rebuilt to the 31 October binary d68a2e35, and the source's print-all patch is one
line of zmx2.rs, output only; cert0 and 30 of the 55 sweep columns (6,600 of 12,100 roots),
every census and listed box equal to the source's; root 9632 whole, the patched dump's 6,850
boxes and qx2_zm.py's 83 the source's byte for byte, ROOT-9632-CLOSED on this run's outputs
(the dump needs --uncert-cap 10^8, which the release does not record); 26 tight-tile jobs
equal line for line (the shipped run_tt.py prints a K field the recorded outputs lack); and
the source's controls refused: zmx2 on both scaled boards, qx2_zm.py on the scaled root-9632
cover, locality_check.py on the mutated mu_12 and the Tight-Tile checker on ctl_rise.txt.

Register. T-298, optimality, scope n = 44, 59, 76, 95, 116, ..., 319 (k = 7 to 18), V0/C0:
every cited entry is a report (family, Valid11 runs, Lean reduction, not built here) and no
review is mapped yet (think-h10k runs blind in lane L144). S4 drafted as a claim, as T-064
and T-081. New counts k = 11 to 18: reported lanes move to k from Hosono's closed form,
verified lanes unchanged; n = 95 is already proved by T-191; T-081 and T-191 gain a
sentence. No verified bound moves. The full replay and Lean build are priced at about 140
CPU-hours here, up to about 320, and held for the owner on think-0h7r.

Also: #973's requests entry; verifier records (V-khalili-tight-tile, V-khalili-k2m5-lean,
V-khalili-k2m5-checks, V-replay-k2m5-family, notes on zmx2, qx2_zm.py, zeromargin.py); the
source's card among the other projects; corpus counts (reported-open 233 to 225); generated
views; new contributor spans left unresolved for the owner's identity review; a
no-public-change record (the explainer's register count 297 to 298 only).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01E8g3iMDhVT21veLdEABoxV
…k2m5_family (OR-16)

The integrity-ceremony gate refused two digest comparisons in the new tool: the staged
packet files and the evand checker files are read from Git, whose custody is
acquire_source --check's, so they are no longer compared. tight_tile/cov.tar.xz, pinned
by digest and read from outside the repository, is still held to the packet manifest's
digest, and the tool is allowlisted with that download boundary.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01E8g3iMDhVT21veLdEABoxV
…= 95's evidence, and the closed form's raised lanes

Hosted CI at 72db934 failed two tests. The curated print credits split the eight
counts whose reported lower lane is now T-298's out of the group Hosono's closed form
held, as T-081's counts were, and n = 95's attached evidence takes the three new
entries; the closed form raises 145 reported lanes, not 153, since T-298 holds a
stronger one at n = 116, 139, 164, 191, 220, 251, 284 and 319. The webkit jobs failed
at browser launch on a runner missing libicu, which this change does not touch.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01E8g3iMDhVT21veLdEABoxV
…cord

Blind stage 4 review of Khalili and Gharabaghi's s(k^2 - 5) = k for every k >= 7
(issue #973, bead think-h10k). This commit freezes the verdicts, the programs and
their small outputs (receipts/freeze.sha256) before the lane reads the record's own
k^2 - 3, k^2 - 4 and k^2 - 5 material; the comparison section follows.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01E8g3iMDhVT21veLdEABoxV
Adds the review's comparison with the record, read after the freeze committed in
2e04440: the base cases T-252, T-066 and T-184 at V3/C3; n = 95 already at T-191;
the eight counts n = 116 to 319 the family newly decides; second routes to T-081 and
T-064 by monotonicity; and the 16 October Greff review, which does not reach zmx2's
area and first-order lemmas (F1 stands). Also the frozen digests and the notes for
the records lane. No program or output changed after the freeze.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01E8g3iMDhVT21veLdEABoxV
…eld on think-kn13

The blind review (docs/project/reviews/review-2026-11-14-khalili-gharabaghi-k2m5-973.md,
merged at f58b34b) accepts the argument with no blocking defect and two major findings
for the record: zmx2's area-density and first-order lemmas, on which the 12,024
general-position roots rest, have no review here (F1), and the Tight-Tile Lemma has one
implementation and no full replay (F2).

Mapped: the document map and the synopsis's; the external_review of T-298's three report
entries; T-298's reviews (adversarial, accepted), so check_results derives C1, as T-081's
claim-chain review gave it; V-khalili-973-review-check with its independence record (not
called clean-room: the lane read the source's checkers in full and did not record freezing
its programs first); E-khalili-973-review-partial-checks for the six parts its exact
programs decide in full (mass and family, Lemma 7's premises, the theta = 0 face, the
coverage of the 75 tight-tile roots, root 9632's closure), cited by the nine cases, with
its coverage record; and n = 95's curated evidence.

Reconciled: the two lanes' replays agree wherever both ran; both found the K field missing
from the Tight-Tile outputs and the ctl_rise counts not reproducing. The price takes the
review's coverage-dump factor (0.75 to 0.79, the source ran them six at a time) over this
lane's: about 145 to 180 CPU-hours, up to about 320 if the unsampled large Tight-Tile jobs
run at the source's speed, with the Lean build on a host with at least 24 GB (think-0h7r).
F1's review is a new held option, think-kn13, an unfinished confirmation on T-298.

The review's section 13 repeated section 11 and ended in a stray token, S-LANE; the
repetition is removed and a dated note says so.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01E8g3iMDhVT21veLdEABoxV
@jlevy jlevy changed the title records(L145): import #973, s(k^2 - 5) = k for every k >= 7, as T-298 (reported, V0/C0) records(L145): import #973, s(k^2 - 5) = k for every k >= 7, as T-298 (reported, V0/C1) Nov 14, 2026
@jlevy jlevy added intake Tracking intake (saving, validation, tabulation, credits) of new results S4 Substantial result or major public project capability labels Nov 14, 2026 — with Claude
… 973)

B1: the record no longer calls the stage 4 review's programs clean-room. T-298's
composition, the three report entries' reviews, E-khalili-973-review-partial-checks,
the request notes and the packet README say "own exact programs (independent, not
clean-room)", matching V-khalili-973-review-check; the review's section 13 gains a
dated records-lane note saying why the review's own word differs.

B2: the nine case files (n = 95 and n = 116 to 319) carry the review, F1 on
think-kn13, F2, and the held replay on think-0h7r.

S1 to S8: section 13 says F2's full replay is think-0h7r's and F1's review
think-kn13's; the claim and the request summary say the controls refused as reported
but the Tight-Tile control's counts do not match (F8); the ctl_rise refusals count 83
at the 2,000-cell cap; the packet README dates the tool's custody change (8784343,
72db934, OR-16); next_rung says think-0h7r reruns the one Tight-Tile implementation
and no bead tracks a second; the S4 score stays the import lane's draft, which the
review did not score; the no-public-change record says V0/C1 and records that
compare_paper_renders, re-run against 0db247d on this tree, still differs from main
only in the explainer's register count; and a test holds every zmx2 and Tight-Tile
receipt to the source's record.

S9: E-khalili-973-replay-sample (the import lane's runs: cert0, 30 of 55 columns,
root 9632's two runs, 26 of 326 Tight-Tile runs) and
E-khalili-973-review-replay-sample (the review's: cert0, 3 columns, root 9632, 3
coverage dumps, 9 Tight-Tile runs; 40 roots noted), replayed-here,
same-implementation, coverage sample of 459 runs; cited by T-298, the request and the
nine cases, n = 95's curated credits and T-298's URL identity.

Notes: N1 headline in T-081's words (plain k, which keeps the results page under its
1,700,000-byte projection: 1,699,269); N2 the lemma review is no condition of C3; N3
the price uses the review's random-job Tight-Tile factor, so 145 follows from the
basis; N4 the import lane's first price marked; N5 close_when names think-kn13 and
the request cites the review's entry; N6, N7 wording; N8 233 CPU-seconds; N9 the
shared Tight-Tile job; N10 k2m5_samples.py, the uncited programs and the unretained
.pyc files; N11 the review ran at tbd-strong, not tbd-strong-max, wherever the record
states its tier; N12 build() reuses a finished build before copying sources, the
cropped cover's sum is weight_sum (compare.json.gz rewritten from the same receipts,
that key alone changed), the QX2_FILES digests are documented as unused at run time,
and K = 4 is marked inferred (F3); N14 the case notes count the 26 Tight-Tile jobs.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01E8g3iMDhVT21veLdEABoxV
@jlevy
jlevy marked this pull request as ready for review November 14, 2026 06:36
@jlevy
jlevy merged commit 9adc3a0 into main Nov 14, 2026
59 checks passed
@qodo-code-review

Copy link
Copy Markdown

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

intake Tracking intake (saving, validation, tabulation, credits) of new results S4 Substantial result or major public project capability

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants