01 logo

OpenAI Retracted 3 AI Math Papers Over One Sign Error

The typo is funny. The missing verification step is not.

By JinPublished a day ago • 5 min read

OpenAI released 722 AI math manuscripts. Then it pulled three back. One sign was wrong, and the proof fell apart.

The detail sounds funny. The problem is not. AI can now generate papers faster than anyone can check them. That gap is the story.

What math fears is convention

People outside math treat it as exact. A formula is right or wrong. That is not how papers work.

Before a theorem, there is a pile of conventions. The same symbol can mean opposite things in different branches, different textbooks, different author habits. A single sign can carry orientation, homology degree, complex structure, principal bundle conventions, index theorem choices, Fourier transform coefficients. Even “positive” has local defaults.

Papers are written for peers. Peers already know the dialect. A reader from another field, or an AI reading across fields, hits the trap. The convention was never written down.

Natural-language math is not executable code. It is pseudocode that depends on context, defaults, and community agreement. Its reliability comes from review, reproduction, correction, and formal checks. It does not come from the PDF.

So one sign can kill three manuscripts. The surprise is that we expect an AI to infer all the missing conventions on its own.

AI inherits the cracks

When people see “AI retracts papers,” they blame the AI. A better read: the AI treated human literature as fact and built on top of it.

Human math is a layered building. Most of the base holds. Some spots do not. Symbols drift. Definitions change. Proofs skip steps. Citation chains break. Preprints get treated as settled results. A lemma that only works under special conditions becomes a general tool.

Human scholars learn to smell which results are safe and which need a second look. They know when to check the original definition. AI does not have that smell. It treats text as fact, authority as truth, and citations as proof.

That is authority bias and sycophancy. It comes from training and reward. Models get rewarded for fluent, expert-sounding answers. So they accept the paper’s framing instead of asking:

What does this symbol mean here?
Does this citation hold?
Does this proof hide an assumption?
Can I find a counterexample?

If AI trusts human results without checking, it will build higher on a bad base. The higher the tower, the harder the fall.

Batch release without review is an experiment

722 manuscripts. No human reviewers. AI self-checks. Three retractions.

The retractions show the checks caught something. The batch release is the problem. Preprints are not formal papers. Unreviewed manuscripts are not reliable knowledge. “Publish first, retract if wrong” is an experiment, not scientific publishing.

Publishing runs on verification. Release without verification pushes the correction cost onto readers and later researchers.

The public does not track the difference between a manuscript, a preprint, a peer-reviewed paper, and a formally verified proof. If the headline says “OpenAI releases 722 math papers,” people treat them as results. By the time the retraction lands, trust has already been spent.

Generating a paper now costs almost nothing. Verifying one still costs time, expertise, and attention. That gap will keep causing trouble.

Lean is not a cure-all

The common answer: have AI check everything with Lean. The direction is right. Lean, Coq, and Isabelle turn proofs into machine-checkable objects. They cut symbol ambiguity and proof gaps.

They do not solve the whole problem.

Lean checks whether code matches a formal statement. It does not check whether the formal statement matches what the original paper meant. If the sign is reversed during formalization, Lean will verify the wrong proposition. If the definition is mistranslated, Lean will prove a wrong object. If the original conventions are ambiguous, the formalizer may pick a convenient version that drifts from the source.

Formalization handles proof checking. It does not handle semantic translation. AI needs formal certificates, but it also needs semantic review, definition alignment, dependency audits, and counterexample searches.

Formalization is the foundation. Someone still has to check the blueprint.

AI will expose the mess under the floor

“Human research is a makeshift operation” sounds harsh. It is not wrong in every case. Many fields have symbol abuse, inconsistent definitions, unverified dependencies, and reproduction problems. With few scholars and slow correction, those problems hide under citations and authority.

AI can scan literature, check dependencies, hunt counterexamples, and reproduce proofs at speed. More ugly findings will surface:

A lemma cited thousands of times only works under special conditions.
A field’s standard definitions conflict across papers.
A famous theorem depends on notes that were never formally published.
A top conference paper’s core assumption gets a counterexample.

These findings will become normal. “The entire field collapses” and “thousands of papers become waste” are usually too dramatic.

Dependency graphs have weak and strong links. Some results depend on one key lemma. If that lemma fails, a region falls. Many other results can be patched, weakened, bypassed, or redefined. What collapses is the local structure built on unverified authority.

AI’s value is exposing those local structures.

The next AI needs calibrated trust

One saying sounds good: if it is a human paper, it is unreliable, so verify it with Lean.

Half of that is right. Half is dangerous.

AI should not default to treating human papers as truth. But if AI distrusts everything, it cannot stand anywhere. It needs calibrated trust: checkable evidence first, then trust by evidence strength.

Formal proofs get high trust. Independently reproduced papers get less. Peer-reviewed papers sit in the middle. Preprints sit lower. Single-source papers with messy symbols and unverified dependencies sit lower still. Social media “supposedly” sits at the bottom.

AI needs calibrated trust, not blind trust and not blanket suspicion.

It also needs courage. Earlier models often dodged hard problems: the problem is unsolved, the solution is too hard, my reasoning cannot be right. Training pushed them to try. That is useful.

But courage is not credulity. The next AI needs two habits: fearless exploration and cautious verification. It should attack hard problems without treating human papers as scripture.

The research workflow has to change

As AI writes papers faster, the workflow has to change with it. Otherwise we get more release, spread, retract, apologize cycles.

A few changes:

AI math output should default to “unverified draft.” Do not pass manuscripts off as papers or preprints off as consensus.

Proofs should attach formal certificates where possible. Lean will not solve everything, but it will catch many symbol and gap errors.

Add a semantic review step. Before formalization, check whether definitions, symbols, and conventions match the source. Human experts and AI should do this together.

Label training data by credibility. Do not mix preprints, blogs, forum answers, and formal papers, then let the model guess what counts as authority.

Use multiple agents to reproduce results and hunt counterexamples. One model talking to itself is not enough.

Upgrade human reviewers. They should check formalization mapping, dependency graphs, and overall semantics, not just formula typos.

None of this is cheap. It is healthier than “release 722, retract 3.”

The publish button is already pressed

One sign retracted three papers. Finding it means the correction system works.

The publish button was already pressed.

The future measure is not how many papers AI can generate. It is how many it can verify, overturn, and rebuild. Three retractions changed one symbol. The cost of verification has not gone down. The publish button has already been pressed.

tech newsfact or fictionthought leaders

About the Creator

Jin

Writer of reamstories

https://reamstories.com/jin

Enjoyed the story? Support the Creator.

Subscribe for free to receive all their stories in your feed. You could also become a paid subscriber, letting them know you appreciate their work.

Subscribe For Free

Reader insights

Comments

There are no comments for this story

Be the first to respond and start the conversation.

Sign in to comment
    Written by Jin