AkashicINQUIRY017 · 20 Nov 2026 · v1.0.0

Has AI Proved the Riemann Hypothesis?

A Proof Claim, Its First Checks and the Work Still Ahead

Claimed proof · Verification pending in the inspected record

About 5 min main article · Full review below

The Question

Brian Greene has shared an extraordinary possibility: a proof of the Riemann Hypothesis developed with AI. What would establish that the problem has been solved, and what has actually been checked?

Current answer: there is an inspectable proof claim. In the verification record examined for this edition, the complete solution build and proof replay were still in progress. AkashicNET has not verified the Riemann Hypothesis.

From a Post to the Primary Claim

A note on mathematician Levent Alpöge’s website reports finding a proof while working with Claude. It also claims a generalised result and describes a further extension as an expectation. The release points readers to Lean source rather than a conventional explanatory paper. This is a substantive, checkable release, while the correctness of the argument remains a separate question. [S01] [S02]

The attribution matters. The primary announcement inspected is the note on Alpöge’s website. This review did not establish a current formal corporate announcement by Anthropic. It also cannot independently apportion the mathematical work between the human collaborator and the model.

What the Mathematics Asks

Prime numbers have an average distribution, with fluctuations around it. The Riemann Hypothesis concerns those fluctuations through the zeros of the analytically continued zeta function. It says the non-trivial zeros all have real part ½. Checking many zeros numerically cannot settle a statement about every non-trivial zero. [S12]

The released entry point declares a theorem with Mathlib’s RiemannHypothesis type. We read the target and the corresponding definition at the dependency’s pinned commit. The displayed generalised statements concern Dirichlet L-functions. That scope should travel with the claim; it should not silently become every possible generalisation of RH. These are source inspections, awaiting executed comparison of the complete proof environment. [S03] [S04]

What the Green Checks Establish

The verification project has successful CI jobs for two preliminary tasks: matching the submission to the published archive and compiling/exporting an independently stated challenge against Mathlib. We inspected the workflow, job steps and both logs. Neither job compiles the proposed solution’s Main module. [S05] [S07]

There is a useful trap here. The challenge file contains sorry placeholders because it states the questions that the solution must answer. The official checking procedure explicitly permits this. Their presence in that file is not evidence that the submitted solution is incomplete. The solution’s own proof dependencies must be checked separately. [S08] [S09]

The verifier’s notes still report the full solution build in progress. Reports of a source-wide text scan and resource requirements are attributed to that project; AkashicNET did not rerun the full scan or build. A truncated API tree was excluded from our source-count conclusions. [S06]

What Would Make the Claim Stronger?

A useful review keeps three proof checks distinct: the formal statement must express the intended mathematics, the proof must use only the permitted assumptions and the complete proof terms must be accepted by the checking kernels. Comparator is designed to compare a separately stated challenge with the submitted solution, including their definitions and axiom dependencies. A configuration file shows how a check is intended to run; its completed output supplies the result. [S08] [S09]

Here, the configured permitted assumptions are Lean’s standard propext, Quot.sound and Classical.choice. The author’s phrase about having no assumptions should therefore be read as a claim of no additional mathematical assumptions, awaiting the actual audit. A clean text search cannot replace that audit. [S07]

Mathematical understanding is another task. A faithful, successfully checked formal proof can establish a theorem even before people have a short explanation of its ideas. Conversely, an elegant explanation cannot stand in for a valid argument. Tao’s dated note directs readers towards ongoing verification and digestion, rather than giving a completed proof verdict. [S10]

Keep the Earlier Result in Its Own Frame

Anthropic’s August research post described an improvement in a lower bound for the fraction of zeta zeros satisfying RH. It explicitly said that work had not proved the hypothesis. Today’s released proof claim is a different event. Earlier related progress is relevant context, while each new argument needs its own checks. [S11]

The Millennium Prize has a separate process. Clay requires a qualifying publication, at least two years after that publication and general acceptance in the mathematics community before it considers a proposed solution. A proof announcement does not complete those conditions. Clay’s current problem page still says Unsolved; that label should not be used as a substitute for reviewing the new submission. [S12] [S13]

Wonder, Understanding and Responsibility

If the argument survives the required checks, the mathematical consequence would be profound. The result would concern the theorem actually proved, with its definitions and scope. Further claims about physics, encryption or consciousness would still require their own arguments and evidence.

For AkashicNET, the practical lesson is already useful: trace the headline to an inspectable object, check what each success signal measures and make uncertainty easy to find. Respect for the work includes careful credit, patient scrutiny and a willingness to correct the record.

What Would Change This Answer?

  • A completed, reproducible proof check: inspect the exact source revision, statement comparison, final axiom dependencies and kernel verdicts before upgrading the reported status.
  • A reproducible defect: state the failing theorem or checking step, the tested revision and the proposed repair. A build or resource failure alone does not refute the mathematics.
  • An author correction or new release: preserve the earlier edition and repeat the affected checks.
  • A clearer mathematical account: add an explanation while retaining the distinction between understanding, formal validity and prize acceptance.

Conclusion for this edition: a serious, inspectable claim merits scrutiny. The evidence reviewed here supports publication of this inquiry with its pending status; it does not support announcing a verified solution.

Full AkashicNEXUS Review · Claims, Changes, Tests and All 21 Components

Full AkashicNEXUS Review · After ENHANCE

Maximum-depth manual appraisal. All 21 components considered; 18 applied and three not applicable. The same assistant researched, enhanced and checked this report. No independent report validation or general effectiveness estimate is claimed.

Material Claims

IDClaimJudgementScope / LimitSources
C01A note on Alpöge’s website claims RH and a generalised result developed with Claude.Supported as an attributed claimThis establishes what is being claimed, not that the argument is correct.S02, S10
C02The supplied post establishes a formal corporate announcement by Anthropic.Unresolved / attribution narrowedThe primary announcement inspected is a personal-site note. No current corporate announcement was established by this review.S01, S02, S11
C03The released entry point names Mathlib’s RiemannHypothesis.Supported by source inspectionThe source target matches the standard definition on inspection. Transitive statement identity still needs executed comparison.S03, S04
C04The displayed GRH statements cover Dirichlet L-functions.Supported by statement inspectionDo not extend the result to every L-function or to the expected Extended RH.S03, S07
C05The green CI checks validate the complete proposed proof.Contradicted by the inspected workflowThe two jobs compare the archive and build/export the independent challenge. Neither builds Main.S05, S07
C06Challenge.lean containing sorry shows the submitted proof has a hole.Contradicted as an inferenceThe challenge deliberately records unproved targets. The solution must discharge them separately.S07, S08, S09
C07The solution has passed its axiom audit and independent proof replay.UnresolvedNo completed result was present in the inspected verification record. AkashicNET did not execute these checks.S06, S07
C08The August partial-zero result and today’s proof claim are the same result.Contradicted by date and scopeRetain both events separately. Earlier related progress neither proves nor disproves this submission.S02, S11
C09A proof claim immediately qualifies for the Millennium Prize.Contradicted by the prize rulesPrize eligibility has its own qualifying-publication, elapsed-time and acceptance conditions.S13
C10This material establishes a quantum, spiritual or conscious AI mechanism.UnsupportedThe inspected objects concern a mathematical theorem and proof validation. They do not test subjective experience or metaphysical causation.S02–S08
C11A proof of RH by itself supplies a practical attack on encryption.Unsupported by this materialNo such algorithm or demonstrated attack is part of the inspected theorem targets. Implications require their own argument.S03, S07
C12A second assistant review makes the AkashicNET report independently validated.UnsupportedThis report was researched, revised and checked by the same assistant. Human owner review and independent external review remain separate.S14

ENHANCE: Before and After

IDBeforeAfterReason
E01Corporate shorthand in the starting postA note on Alpöge’s website claims work with ClaudePreserves the verified source and the human collaborator.
E02An unrestricted use of GRHGRH for the Dirichlet L-functions in the released statementsStops a broader theorem being inferred from a narrower target.
E03A green badge treated as proof acceptanceArchive comparison and challenge build/export are the completed checksMatches the summary to the actual jobs and logs.
E04Any occurrence of sorry treated as a failed submissionChallenge placeholders distinguished from the solution’s proof obligationsAvoids a false alarm while keeping the solution axiom audit pending.
E05A truncated API listing used as a complete inventoryIncomplete tree excluded from source-count claimsKeeps incomplete retrieval from becoming a misleading denominator.
E06An impressive claim treated as an established resultClaimed proof; full verification pending in the inspected recordKeeps the published conclusion aligned with available evidence.

TEST and VALIDATOR

IDCheckStatusObserved Result
T01Source attributionCheckedPersonal-site claim retained; a corporate announcement was not established.
T02Theorem and dependency targetChecked · static scopeThe RH target is present; the displayed GRH targets concern Dirichlet L-functions.
T03CI job scopeCheckedArchive comparison and challenge compilation/export succeeded. No Main build is in this workflow.
T04Legitimate challenge placeholdersCheckedExpected placeholders in the question file are not counted as a failed solution proof.
T05Wrong-scope claimsChecked · manualOverextended GRH, conflated dates, immediate prize and unrelated implications rejected or qualified.
T06Full solution compilationNot executed hereThe verifier reports the build in progress. No local build pass is claimed.
T07Final axioms and kernel replayPendingNo final axiom output or full Comparator verdict was available in that record.
T08NEXUS record contractPassed · structural scopeCurrent checker returned valid: true with no structural errors. It does not establish source truth, mathematical validity, identity or independent review.
T09Article and infographic deliveryPassed · static scopeSource anchors, declared image dimensions, claim IDs and module coverage checked. Browser and deployment results are separate delivery checks.

All Components

ComponentEditionScopeOutput
AkashicMESSAGEv0.4.0-beta.1AppliedSplit the post into attributed report, proof claim, implication and publication request; preserved stable claim IDs.
AkashicINQUIRYv0.3.0-beta.1AppliedDISCERN traced primary sources; DEEPEN checked code, CI scope, challenge placeholders and alternatives before synthesis.
AkashicASSESSv0.3.0-beta.1AppliedCompared declaring a solution, withholding all coverage and publishing a bounded inquiry. Chose a dated inquiry with an explicit pending verdict.
AkashicENHANCEv0.2.0-beta.1AppliedSix before/after changes retained, including the authority, GRH-scope and CI corrections. No increase in truth confidence inferred from a longer workflow.
AkashicSPIRITv0.3.0-draft.1Applied · reflective scopeWonder can motivate inquiry and humility can guide attribution. Neither feeling supplies mathematical evidence.
AkashicABSTRACTv0.1.0AppliedSummary preserves collaborator, claimed theorem scope, completed checks and missing proof verdict.
AkashicPRISMNumbered edition unverifiedApplied · manual draft scopeReframed “did AI solve it?” into distinct questions about release, statement identity, proof validity, understanding and credit.
AkashicPYRAMIDNumbered edition unverifiedApplied · layered readingFoundation: source and definitions. Next: executed statement/axiom/kernel checks. Above: expert explanation and wider consequences. Missing steps remain visible.
AkashicONENumbered edition unverifiedNot applicableThe linked private puzzle experiment is not required for this theorem review and was not accessed.
AkashicOMNIv0.5.0Applied · manual v0.5.0All twelve published perspectives considered below; synthesis retains the same unresolved proof status.
AkashicNEURONumbered edition unverifiedNot applicableNo neural, clinical or physiological measurements are present in the reviewed material.
AkashicTRACENumbered edition unverifiedAppliedOriginal post, announcement, two pinned repositories, dependency pin, job IDs, access limits and retrieval timestamps retained.
AkashicTESTNumbered edition unverifiedApplied · bounded checksCorrect and misleading interpretations checked, including the legitimate sorry placeholders. Compilation and replay remain explicitly unexecuted.
AkashicFLOWv0.2.0AppliedSource review, enhancement, checks and the new inquiry are linked. Owner review is a post-run handoff, not an invented publishing gate.
AkashicNEXUSv0.1.0AppliedCoordinated one bounded manual route. All registered components were considered; no claim of autonomous engines or all-permutation execution.
AkashicSTATEv0.1.0-draft.1AppliedContent edition v1.0.0 recorded. Scientific claim unresolved; owner and external reviews pending. No framework maturity ratings promoted.
AkashicFOOTPRINTv0.1.0-alpha.1Applied · measurement limitsNo complete labour, billed-usage, energy or carbon measurements collected. No efficiency or cost saving claimed; local full-proof build not attempted.
AkashicTIERv0.1.0-draft.1Not applicableNo package, entitlement or commercial offer was requested.
AkashicAUDITv0.1.0-draft.3Applied · self-reviewEvery material claim has a source and a scoped judgement. Missing evidence remains unresolved, not false.
AkashicLEDGERv0.1.0-draft.2AppliedStarting report, six refinements, check outcomes and reopening triggers preserved in this dated record.
AkashicVALIDATORv0.1.1-alpha.1Applied · structural profileCurrent component v0.1.1-alpha.1; checker and contract v0.1.2. Structural execution result is added after running it.

Twelve OMNI Perspectives

PerspectiveApplication
AWAKENLet the significance invite attention while keeping the theorem verdict open.
HIERATICRead the language of beauty and revelation as the author’s expression, separately from the formal argument.
HOMESENSE · Phase 8Ask what a person can inspect, explain and rely on when the argument is too large to follow unaided.
ADAPTUse independently stated targets and checkable artifacts to adapt review practice to generated proofs.
REGENERATETreat maintained explanations and reusable checking methods as potential public benefits, not already measured outcomes.
TRANSCENDExplore a change in how mathematics is produced without abandoning criteria for validity.
#METADNotice how a respected name, a green badge or the word Lean can change confidence before the proof is checked.
ACTCSeparate the human’s account of collaboration from evidence assigning causal credit to specific model actions.
MultidimensionalCUT · PastKeep the earlier partial result and longstanding mathematical tools in their own dated source trail.
MultidimensionalCUT · PresentThe actionable objects are the released targets, dependency pins and current verification outputs.
MultidimensionalCUT · FutureA pass, a reproducible flaw or an inconclusive resource limit leads to a different next step.
UMASCDistinguish individual understanding, machine checking and community acceptance as different scales of assessment.

Post-Run Human Review

Review by the curator is pending. The curator is invited to assess accuracy, sources, gaps and presentation. Answers are visible. Independent external review of this appraisal: Pending. External mathematical checking is a different process.

Framework readiness ratings are retained. No complete labour, billed usage, energy or carbon measurements were collected. No savings are claimed.

Run NEXUS-RIEMANN-2026-11-20-001 · v1.0.0 · NEXUS v0.1.0 · OMNI v0.5.0 · Contract and checker v0.1.2.

Source mirror: 7cbf7a0c32fca1badf05931879a37c3f8a2b03b4
Verification revision: 1f2beda145f7b7a9f6f6f6640a60f2e44920b7ba
Mathlib pin: 0df444a360eaa60ab8c11dca51a86af692955474

Sources and Access

  1. S01 · Brian Greene’s Original Post

    Original post read in X. A report of the claim, not proof validation.

  2. S02 · Note on Levent Alpöge’s Website

    Text of the four-page note retrieved. The proof archive itself was not downloaded in this run.

  3. S03 · Released Theorem Statements and Proof Entry Points

    Selected source files read at this fixed mirror commit. Full source identity was not locally checked.

  4. S04 · Mathlib’s Pinned Riemann Hypothesis Definition

    Definition read at the dependency commit declared by the submission.

  5. S05 · Verification CI Run and Its Two Jobs

    Run, job steps and both job logs inspected. Successful archive comparison and Challenge build/export observed.

  6. S06 · Verifier’s Detailed Notes

    Notes read. Full solution build reported in progress. Resource estimates and source-wide scans are the verifier’s reports.

  7. S07 · Independent Challenge and Comparator Configuration

    Challenge.lean, comparator.json, README and checks.yml read. A configured checker is not a completed check.

  8. S08 · Lean: Validating a Proof

    Official documentation inspected, including statement meaning, axioms and Comparator checks.

  9. S09 · Comparator’s Official Documentation

    Documents challenge/solution comparison. The standalone repository points users to the tools integrated into Lean.

  10. S10 · Terence Tao’s Dated Research Note

    Relevant RH discussion read. Expert attention and ongoing digestion do not certify the proof.

  11. S11 · Anthropic’s Earlier Partial Result

    Research post dated 10 August 2026 inspected. Describes progress on a lower bound, not a proof of RH.

  12. S12 · Clay Mathematics Institute: Riemann Hypothesis

    Problem description and the page’s current Unsolved label inspected. The label alone cannot adjudicate a new proof.

  13. S13 · Clay’s Millennium Prize Rules

    Qualifying publication, elapsed time and general acceptance conditions read.

  14. S14 · AkashicNEXUS Public Guidance

    Current application guidance and editions checked against the dated module record and current site source.

  15. S15 · AkashicOMNI: Twelve Perspectives

    Published v0.5.0 perspective list used for the manual appraisal below.

The Inquiry in One Image

Download the Infographic · Full Reading Copy · Run Record

Has AI Proved the Riemann Hypothesis? A dated status diagram shows the claim is public, source matching and the standalone challenge checks have passed in the inspected CI, while the solution build, axiom audit and kernel replay remain pending. The displayed generalised targets concern Dirichlet L-functions.
AkashicNET editorial infographic · Evidence snapshot 20 Nov 2026, 19:40 CET. Schematic status summary. The 29 is a personal design motif.

Read the EXPAND² companion for Inquiry 017