Method

How a result earns its place.

Nothing that matters rests on one implementation, one model or one reader. This page says what happens before a result is released, what each step can catch, and what none of them can.

The stackin the order a result meets it

  1. A question

    We choose it: usually a named open problem, or a sharper form of one. Before work starts we write down what would show the expected answer wrong.

  2. Exploration

    Many model instances, from more than one developer, work on the problem in long sessions, in parallel, building on and challenging each other’s results. We set the direction and decide which lines to pursue and which to drop.

  3. A blind check that tries to refute

    Before a result is kept, a model that has not seen its proof, usually from a different developer, first tries to refute the statement, then audits the proof line by line.

    Catchesfalse statements, gaps, and statements stronger than their proofs.

  4. Exact computation on independent engines

    Finite claims, constants and certificates are computed with exact arithmetic where possible, on at least two independently written engines. The programs, their recorded outputs and checksum manifests ship with the paper.

    Catchesnumerical and transcription errors, unless every engine shares them.

  5. Whole-paper audits

    Each paper goes through rounds of adversarial audit by readers that have not seen it, alone and together with its companion papers, with literature searches for priority and credit. Fix rounds follow each audit, and a fresh audit follows each fix round.

    Catcheserrors between sections, misplaced credit, and claims the paper does not prove.

  6. Lean, where it matters most

    We are formalizing the main theorems in the Lean 4 proof assistant with Mathlib, paper by paper, and every formal proof is checked to use only the standard axioms. Each paper says exactly what is formalized so far.

    Catchesany gap in the formalized part.

  7. Release

    A public repository with the source, the checks and their recorded outputs; a DOI for every version; a statement of what was checked and what was not.

  8. Corrections

    Errors found after release are corrected in a new version and listed below, with what was wrong and what changed.

What the checks cannot catch

  • An error every method shares. In August 2026 two engines agreed on a step in our I3322 work because both had been written from the same transcription; a later exact audit found the error, and the claims were withdrawn publicly the day after release. An engine that copies another’s transcription now counts as the same engine. The record
  • What Lean does not formalize. A formal proof covers its own statement and nothing else, and a formal statement can differ from the intended one. Statement fidelity is audited separately.
  • Work we have not found. Literature searches miss work that is new, unindexed or posted elsewhere. When concurrent work comes to light after a release, we add a note.
  • Our own blind spots. Every check described here is internal, and none of it is journal peer review. One paper on this site, an earlier single-author paper, has been published in a journal; no joint paper has been through journal review yet.

Correctionsall thirty-three, newest first

Any change that fixes something a released version got wrong: a mathematical error, a claim stronger than its proof, wrong or missing credit, a wrong citation, or faulty packaging of the checks. A new version that only adds results is a release, not a correction.

    • ReleaseFinitely presented infinite p-groups for every prime v1.0.1 10.5281/zenodo.23791059Correction. Credit: a “Note added” in the introduction cites Kenta Kitamura’s independent, concurrent work (manuscript 13 October 2026, Lean 16 October 2026), which also proves the every-prime result; in the paper’s words, “the extension to every prime listed above is shared with it.”
    • ReleaseThe price of keeping time v1.1.1 10.5281/zenodo.23790746Correction. Version 1.1.0 said, in the batch-law appendix, that a minimizing Y need not exist. The infimum is attained (Rockafellar, Convex Analysis, Theorem 28.2). No result depended on the sentence.
    • CorrectionThe four thermodynamics papers of 11 OctoberCorrection. The four thermodynamics papers of 11 October cited Thompson et al. with a DOI that did not resolve. Version 1.0.2 of each paper gives the correct DOI, 10.1103/dryx-l5rt.
    • ReleaseThe I3322 quantum value is attained spatially but not in finite dimension v4.1.0 10.5281/zenodo.22698978Correction. Proof correction to version 4.0.0. The lower bound had identified paired components without justification; it now uses a weighted flow over all retained edges. The limiting-weld justification, an endpoint-gap constant, the spatial amplitude notation, the mixed-state argument and two upper-rate constants were also corrected. Concurrent independent work by Pauwels and by Coladangelo is credited. The main statements and the upper coefficient are unchanged.

The thirty-three entries are the corrections named in our release notes, changelogs and commit messages, and the credit, precision and citation fixes found when every patch release from August to October 2026 was reread against the version before it.

A confirmed error is fixed in the next version of the paper and listed here. Earlier versions stay archived under their own DOIs.

Labels

Every result carries four labels: verification, Lean, peer review and novelty. Novelty is stated as one of these values: new; new, with named precedent; new, with named precedents in form; new, with named prior work; concurrent with named independent work; new proof of a known result; extends named prior work; unifies named prior results; synthesis of prior work (credited). The last is for a paper whose contribution, in its own words, is to bring earlier results together and present them, with each credited; we use it only when the paper describes itself so. We make no claim of priority without a dated citation, and the credit on the site matches the credit in the paper.

The process above is how the joint papers are made. Nidhal Mghirbi’s earlier single-author papers predate it: their verification label says “the author’s own checks” and names the reproducibility package where there is one, and nothing on this site implies our blind-audit process for them. A peer-review label other than “not yet” requires a journal’s own record of publication; a Zenodo resource type is not enough.

Labels are dated. When a paper changes, its label is checked again.

Our toolsexact certification, by Nidhal Mghirbi

Three tools turn a numerical search into a statement checked in exact arithmetic. Each is released with its paper or as a package on Zenodo; their checks are the author’s own, and none is peer reviewed yet.

  1. ACSP: proof-carrying affine symbolic search

    A calculus for bounded, finite-depth searches in one integer parameter with rational affine registers. Exact valuation classes, congruence preimages, affine cuts and exact updates give partitions into progressions with locally checkable witnesses, so that acceptance rests on a local certificate contract rather than on rerunning the search; the verifier’s cost follows the proof representation, not the population it represents.

    Paper: Proof-carrying affine search with valuation guards and compressed progression certificates (Zenodo, 14 September 2026). Package: ACSP Symbolic Search Package, version 3.0.0.

  2. Certified moment completion and structured noncommutative SDP post-optimization

    Turns a verified Gram matrix into a reusable optimization state. A completion theorem attaches a certificate for the full problem to intermediate dual states without assuming numerical optimality, and the remaining gap splits into an optimization part and a consistency part. Its Bell benchmark is I3322, where a new dual witness turns a numerical suggestion into an exact statement.

    Paper: Certified Moment Completion and Structured Noncommutative Semidefinite Postoptimization (Zenodo, 14 September 2026).

  3. Exact semidefinite post-optimization

    The reproducibility compendium for the paper above. Its acceptance paths use exact integer and rational arithmetic; in its own words, numerical optimization “discovers candidates; it is not a condition of theorem acceptance.”

    Package: Exact Semidefinite Postoptimization: a reproducibility compendium (Zenodo, 14 September 2026). The exact I3322 bounds follow the same rule.

AI disclosure

Our joint papers are the work of their authors together with AI models from more than one developer. The authors take responsibility for every claim.

The authors set the direction throughout: they choose the questions, decide which lines to pursue and which to drop, and judge and select the results. The models do most of the exploration, derivation, computation and drafting. Models are not listed as authors.

Every paper first released on or after 12 October 2026 includes a section titled “How this work was done” that describes the process for that paper and says what is checked by machine and what is proved only in the text. Reports of the independent checks are available from the authors. For Nidhal Mghirbi’s earlier single-author papers, each paper’s own text is the record of how it was done.

Licence

The text of this site is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0): you may share and adapt it for any purpose, with credit to finite.works and a link to the page. Each paper, its source and its code carry the licence stated in its repository, and the PDFs hosted here are the released files under their papers’ licences. The Libertinus typefaces are used under the SIL Open Font License 1.1.