earlyink
070 watching first flagged11 Oct 2026

Verification becomes the measurable bottleneck, from math proofs to office work

Checking, refereeing and review-load measurement for AI output, paid for by research funders, journals and enterprise CFOs.

Competitive · Peer-reviewed AlphaProof versus OpenAI proof dump

Written for: Investor or analyst

Next step

Thesis: the scarce resource in AI-assisted work is now checking, and a verification category will form around it. Confirming signal: a funder, journal or lab pays a third party to verify AI results at volume. Already building: DeepMind's peer-review-first approach, the formal-proof community around Tao, and the survey teams at Workday, Google and MIT.

Why now

New since the watchlist entry: the two labs have now shown the two paths, reviewed first versus dumped and verified later, and the community punished the second. Terence Tao's 'Math 2.0' frames the shift. Outside math, NYT reporting on surveys from Workday, Google and MIT names a human 'verification tax' as the reason AI productivity gains stall. Epoch and Anthropic find that agents overstate their results. A study of semantic query engines finds 0.07% to 10.2% of rows change output at temperature 0. Supply of AI output is running well ahead of the capacity to check it.

What became possible

DeepMind's AlphaProof Nexus solved dozens of open problems, including nine Erdős problems, and passed peer review in Science. OpenAI released 372 results at about three hours of compute per proof and faced a boycott for skipping review.

Three ways in

  1. Referee triage for AI-generated results

    Formal checking where possible, then routes what remains to paid human referees, with a public status for each claim.

    Customer
    Science funders, journals and the labs themselves
    Model
    Per-result verification fees plus funder grants
  2. Verification load meter

    Measures the hours staff spend reviewing AI output, by workflow, so AI ROI is reported net of review time.

    Customer
    Enterprise CFOs and transformation offices
    Model
    Per-seat SaaS
  3. Run-to-run variance certification

    Repeats AI judgments many times and reports how stable they are before teams rely on them.

    Customer
    Data teams running LLM-in-the-database workflows
    Model
    Usage-based testing

Competition

Competitive

So the opening is to be the independent auditor rather than another prover. That means a trusted third party that does not generate proofs (so it has no conflict of interest when the labs publish results), checks that formal statements actually match the paper's claims (the known weak point, since Lean only verifies the theorem as stated), and fits into editorial systems with standard gap reports. The main risks are that the prover labs add certification themselves or partner directly with journals, that open-source document-level autoformalization from EPFL and LeanAide makes the pipeline a commodity, and that most research math still can't be formalized cheaply because Mathlib's coverage is limited. A realistic start is narrow: certifying AI labs' own headline claims and serving specific combinatorics or number theory journals, before trying to sell broad triage to publishers.

Full competition notes (12 competitors)

I'd call this space competitive rather than crowded, and the two ideas are in different shape. Generic referee triage for publishers is already largely taken. MDPI runs AI integrity screening on every submission, Springer Nature has Geppetto, Proofig handles images, platform vendors like Silverchair sell gatekeeper AI, and Google and OpenAI give authors free correctness checkers. A startup selling AI-origin detection plus triage would be up against incumbent tools and the publishers' own in-house teams, and AI detection itself has well-known accuracy problems. None of the publisher tools I found judge novelty, though. Formal proof certification is less settled. Math Inc, Harmonic and Axiom have the strongest autoformalization technology, but they present themselves as proof generators and research labs. I found no product that takes a submitted manuscript and returns a neutral pass, fail or gap certificate that a journal or funder can rely on. The AXLE example, where Axiom's engine checked proofs written by other labs' systems, hints at that role, but none of them sell it as a service. So the opening is to be the independent auditor rather than another prover. That means a trusted third party that does not generate proofs (so it has no conflict of interest when the labs publish results), checks that formal statements actually match the paper's claims (the known weak point, since Lean only verifies the theorem as stated), and fits into editorial systems with standard gap reports. The main risks are that the prover labs add certification themselves or partner directly with journals, that open-source document-level autoformalization from EPFL and LeanAide makes the pipeline a commodity, and that most research math still can't be formalized cheaply because Mathlib's coverage is limited. A realistic start is narrow: certifying AI labs' own headline claims and serving specific combinatorics or number theory journals, before trying to sell broad triage to publishers.

  • Math Inc (Gauss / OpenGauss)

    Venture-backed autoformalization agent. It formalized the strong Prime Number Theorem in Lean in about three weeks and helped with the sphere packing formalization. Scientific American reports it can flag and fix minor errors in papers. It is the closest match to the proof certification idea, though I found no per-manuscript certification product or journal deal.

  • Harmonic (Aristotle)

    Lean-based prover that reached gold-medal-equivalent performance on IMO 2025. It turns natural-language problems into formal statements and proofs, which puts it in a position to offer verification of claimed proofs.

  • Axiom Math (AxiomProver, AXLE)

    AxiomProver autoformalizes and proves research results. In one paper, its AXLE Lean engine served as an independent checker for proofs that Aristotle and OpenGauss generated, which is close to the neutral certifier role.

  • EPFL Document-Level Autoformalization (Renaissance Philanthropy)

    Funded academic project building open-source tools that formalize whole mathematical documents, which could commoditize the core pipeline.

  • LeanAide

    Open, philanthropy-funded no-code environment that combines AI with Lean for autoformalization.

  • Google Paper Assistant Tool (PAT)

    Gemini-based checker for errors in papers. It was piloted on more than 4,700 submissions at STOC and ICML and is positioned for authors to use before submitting. This is a big-company move into informal correctness checking for math and theory conferences.

  • OpenAI Prism Paper Review

    Checks whether derivations are correct, whether units are consistent, and whether claims follow from the method. Positioned as a pre-submission rigor check.

  • MDPI Ethicality

    In-house AI integrity screening of every MDPI submission: paper mills, AI-generated text, citation manipulation. This is publisher-side triage already running in production.

  • Springer Nature Geppetto and Proofig

    Tools publishers already use for AI-text detection and image-integrity checks. They are part of large research-integrity operations that screen millions of submissions.

  • Silverchair submission-to-decision tooling

    Vendor of publishing platforms marketing gatekeeper AI that checks whether submissions are complete, compliant and technically sound.

  • YesNoError and Black Spatula Project

    A commercial tool and an open-source project that scan published papers for errors at scale (tens of thousands and about 500 papers respectively). Both use informal LLM checking, not formal proofs.

  • Igor Rivin arXiv error analysis

    Research system that scanned more than 37,000 arXiv math papers for errors and recommended journal tiers, showing that automated triage of math papers is already feasible.

Checked 2026-10-11

Risks

  • Paying buyers for math verification are few and grant-funded
  • The enterprise version is easy to describe and hard to sell as its own line item
  • Labs may build verification into their own products

Strong team fit; buildability is the weak point (5).

tech 6 · pull 6 · space 7 · fit 8 · build 5

Exposed

Companies that could benefit or be threatened. News and context, not investment advice.

Momentum of its main topic

24 developments this week -11 vs last week
21 Sep: 0 developments22 Sep: 0 developments23 Sep: 0 developments24 Sep: 0 developments25 Sep: 0 developments26 Sep: 0 developments27 Sep: 0 developments28 Sep: 0 developments29 Sep: 0 developments30 Sep: 0 developments1 Oct: 0 developments2 Oct: 0 developments3 Oct: 0 developments4 Oct: 0 developments5 Oct: 0 developments6 Oct: 0 developments7 Oct: 0 developments8 Oct: 4 developments9 Oct: 13 developments10 Oct: 3 developments11 Oct: 5 developments12 Oct: 4 developments13 Oct: 6 developments14 Oct: 1 development15 Oct: 4 developments16 Oct: 3 developments17 Oct: 7 developments18 Oct: 1 development19 Oct: 2 developments20 Oct: 6 developments
Stage: Coverage

Sources

  1. Google Deepmind's AlphaProof Nexus solved dozens of open math problems and actually got peer reviewedThe Decoder
  2. AI’s First Full Field-Level DisruptionThe AI Daily Brief
  3. When AI Solves Your Life’s WorkThe AI Daily Brief
  4. Terence Tao: Math 2.0 [pdf]Hacker News
  5. As economic and corporate research shows limited AI efficiency gains, surveys by Workday, Google, MIT, and others detail a human "verification tax" bottleneck (Sarah Kessler/New York Times)Techmeme
  6. AI agents overstate their results and remain far from autonomous research, study findsThe Decoder
  7. Same Query, Different Answer: Run-to-Run Variance in Semantic Query ProcessingarXiv
  8. The gap in shared understanding of LLM capability is wideningHacker News
  9. Is Claude Conscious? Pope Rejects, Model Welfare Movement, OpenAI's Math Backlash, France RiotsAll-In Podcast

Status history

  • 2026-10-11 Added to the watchlist