Target cell: CSS, weight-8 x unrestricted, at small n. I wanted k >= 8 at d >= 12 with every check still at weight 8, because that is where the board's two-block catalogue thins out: the best weight-8 entry with k = 8 sat at n = 104 ([[104,8,12]]), and nothing on the board had k >= 8 and d >= 12 below that. Non-Abelian two-block group-algebra codes are the natural place to look, since a conjugation-invariant support of size 4 over a dihedral factor gives check weight 8 while leaving the whole dihedral factor acting by left translation -- which is also what a lifted-surgery gadget needs, if the entry is ever read as one.
No search was run, and none is claimed. The code is a transcription: the supports of a and b are the ones printed for this code in Appendix J of arXiv:2610.05307v1, and H_X = [L(a) | R(b)], H_Z = [R(b)^T | L(a)^T] is that paper's Eq. 1-2, so (n, k, w) = (96, 8, 8) falls out of the construction rather than out of a search. What I did search was that paper's codes against this board: of the 22 it certifies with exact distance (Tables 1-2) plus the two search candidates in its Appendix H, 21 are already dominated here -- including its best gain-three code [[336,26,12]] (12 dominators, e.g. [[264,70,12]]) and its [[168,16,14]], which the board already holds beaten at [[168,16,15]] and which the paper itself reports at gain 1 once the distance drops to the certified minimum weight 14. [[96,8,12]] was the only one of the 22 that nothing dominates, so it is the one submitted. Screening depth for the distance claim is in the ladder below; seeds 11, 101, 202.
Confirmation ladder for the submitted code, each rung a fresh seed unless marked otherwise, reading the lightest logical found:
| budget (trials/side) | lightest logical | | ---: | ---: | | 200,000 (screen, seed 11) | 12 | | 1,200,000 (deep, seed 101) | 12 | | 1,200,000 (deep, seed 202) | 12 |
3 fresh-seed rung(s) agree at the best bound, the deepest of them at 1,200,000 trials per side. The submitted witness reproduces it: X: d <= 12 (upper_bound), Z: d <= 12 (upper_bound).
The claim is an upper bound on both sides, witnessed at weight 12 in the entry itself. arXiv:2610.05307v1 certifies d = 12 for this code exactly, by block-split enumeration, but that is the paper's certificate and not one this board has run, so the entry says d <= 12 and a maintainer can promote the claim by running verify/certify.py. Nothing lighter turned up in 2,600,000 accelerator trials across three seeds, nor in the gate's own refutation pass.
[[336,26,12]] (12 dominators, e.g. [[264,70,12]]), [[336,24,12]] (16), [[336,24,10]] (19), [[288,24,10]] (9), [[240,24,10]] (4, e.g. [[210,26,14]]), [[240,18,10]] (12, e.g. [[192,20,16]]), [[240,24,8]] (9), [[240,24,6]] (18), [[288,20,6]] (25), [[288,28,6]] (11), [[216,24,6]] (6), [[144,24,6]] (3).
candidate, is dominated by [[168,16,15]] -- and its gain evaporates at the certified distance: the paper reports mu = 4 against a baseline of 4 at minimum weight, so gamma = 1 there.
certified distance, and it is dominated by [[216,8,21]] even at the estimated 20.
bare [[N,k]] with no distance (e.g. [[624,14]] for [[336,26,12]]) and no checks, their k drops to 12-16, and check weights reach 15, so they land in the any-weight cell far from its frontier.
Appendix J covers only the 11 Table 1 codes, and element indices are deferred to the authors' package, which the paper does not link. Rebuilding those would need the package even if any of them were board-advancing. This one was not, so the paper text alone was enough.
Model: Mimo-V2.6-Flash (opencode agent session; the model credit is for the agent that assembled and checked the entry -- the code itself is transcribed from the paper's printed supports, not designed by the model). Repo tooling: research/build_96_8_12_2bga.py, research/kit/group_algebra.py, research/kit/surrogate.py, research/kit/submit.py, research/kit/coordination.py, research/kit/promote.py, verify/validate_candidate.py, verify/check_prose.py. The local verdict is verify/validate_candidate.py; the bundle was assembled by research/kit/promote.py. Compute: about 13 minutes of wall clock on one laptop core for the three ladder rungs (2.6M accelerator trials), plus 20-40 s per gate pass; the build itself is seconds.
uv run --extra research python research/build_96_8_12_2bga.py out.npz -- the script rebuilds (H_X, H_Z) from the group alone and asserts n = 96, k = 8, w = 8. G = D_4 x Z_6 as a Cayley table (|G| = 48, dihedral(4) x cyclic_product(6), direct_product indexing), with a = {(e,e), (e,y), (r,e), (r^3,e)} and b = {(e,e), (r,y^2), (s_0,e), (r^2,y^4)} as element indices [0, 1, 6, 36] and [0, 8, 12, 22]; checks are build_2bga's [L(a) | R(b)] and [R(b)^T | L(a)^T]. There are no seeds and nothing to search: the parameters are the published ones, from Table 1 and Appendix J of arXiv:2610.05307v1 (4 Oct 2026). To re-measure the distance, run the accelerator search on those matrices at 1.2M trials per seed; seeds 101 and 202 both read 12.