Target: CSS, unrestricted connectivity, maximum check weight 8. Starting from an existing sparse stabilizer code, remove one independent X generator to increase k by one, then search both logical sectors for the resulting distance loss. The parent is the board's [[96,22,6]] 2BGA code on SmallGroup(48,11), reconstructed there from the Lin–Pryadko database. This submission concerns the derivative; it makes no claim to the parent's construction or literature novelty.
144 single-row-deletion trials across 36 parent entries. The first 48 trials used 12 parents with n=20–30; the next 96 used 24 parents with n=50–120. Parents were selected from the stored-claim Pareto frontier with check weight at most 8 and claimed distance 4–6. Each side was first reduced to an independent subset of its original rows. Each parent received two X-row and two Z-row deletions, with k recomputed exactly. These are trial counts, not a claim that every resulting stabilizer group is inequivalent.
Screening used the repository submission builder with 200 randomized trials per side. All trial documents and their witnesses were saved, and all 144 passed the trusted structural/witness verifier with refutation disabled. Only three cases with a bound at least 3 remained provisionally nondominated; these received 8,000 fresh trials per side and the full candidate gate. One [[54,21,3]] case was an exact duplicate of the existing entry; a second matched its parameters. The selected [[96,23,6]] derivative improves k over its parent and has a previously unoccupied parameter triple in this checkout.
For this candidate, the 200-trial screen used seed 20261035 for X and 20261036 for Z and found weight-6 logicals on both sides. The 8,000-trial confirmation used seeds 20361035 and 20361036 and again found 6 on both sides. The lowest stored witness from each side was retained across these runs. A further independent 100,000 trials per side at seeds 20461035 (X) and 20461036 (Z) again returned weight 6 on both sides, taking about 231 seconds. The submitted witnesses remain the saved weight-6 confirmation witnesses.
The trusted candidate gate passed at seed 111883778: structure and witnesses accepted; no lighter logical in 6,340 RIS trials; no exact fingerprint or WL signature duplicate; board advancement in unrestricted weight-8, with gains on k and n relative to dominated peers and no distance-only gain flag. This comparison is relative to checkout 0ad745c011ce7393c921a39cf35fe760090222c4, not the entire literature.
Both d_X <= 6 and d_Z <= 6 are upper bounds. No lower-bound proof or exact certificate is claimed for this code. Circuit-level distance and logical error rates have not been measured.
The first 48 trials yielded bounds of 1 (19 trials), 2 (23), or 3 (6). The larger 96-trial screen yielded 1 (32), 2 (38), 3 (16), 4 (9), or 6 (1). Deleting an independent stabilizer raises k but usually creates short logicals; retaining the parent's claimed distance was rare in this pilot. The result does not establish that any other deletion or construction family is exhausted.
Author: @nihoniumqc. GPT-6 through Codex; Python 3.12.2, NumPy 2.2.6, SciPy 1.14.1, and the repository's GF(2), submission, surrogate, and trusted verification modules. CPU only. The 144 screening trials took approximately 46 seconds in total, excluding confirmation and verification.
Use the parent from github.com/unitaryfoundation/qldpc-challenge at 0ad745c011ce7393c921a39cf35fe760090222c4, codes/96-22-6.json. Its construction and literature attribution are documented in notes/96-22-6.md. Convert each support list to a binary matrix with 96 columns. For each matrix H, compute the pivot-column list p from the repository's GF(2) RREF of H transpose, and retain H[p,:] in that order. This selects original sparse rows; it does not replace the checks by potentially dense RREF rows. Remove row 17 (zero-based) from the resulting X basis and keep the Z basis. The resulting ranks are 36 and 37, hence k=96-36-37=23. CSS commutation is preserved by taking subsets; all retained rows have weight at most 8. Package with the repository submission builder at the seeds and trial counts above, keeping the lower-weight saved witness on each side. The submitted JSON contains both full support matrices and the final witnesses, so the code can also be verified directly without rerunning the search.