On September 4, 2026 (a few secondary sources say Sept 5), Anthropic announced and released a complete Lean 4 formalization of Fermat's Last Theorem — the last open item on Freek Wiedijk's famous 100-theorems list — built by an internal Claude model working 'largely autonomously' over ~11 days on the prove2.me platform: ~13 million lines of Lean and ~29,500 intermediate theorems (excluding Mathlib), following the Wiles–Taylor–Wiles route via Darmon–Diamond–Taylor. The artifact is public on GitHub and, per Anthropic's technical report, was accepted by Lean's kernel plus an independent second checker (nanoda) with a comparator confirming the statement proved; it reuses Mathlib and Kevin Buzzard's Imperial College FLT work. Expert corroboration is strong but largely first-adjacent: Buzzard himself wrote 'Anthropic has beaten me to it' about his own multi-year formalization effort, Nature covered the release, and Lean's creator Leonardo de Moura amplified it. The AI-contribution claim (~6B output tokens, ~$300k at API rates) remains Anthropic-self-reported, and the case's Oct 2 addition — a spare-time, mostly-Claude Lean mechanization of an unrelated PL paper — is a first, self-reported hobbyist-scale replication of the workflow.
2026-10-03T06:04:14Z
grounded: converges/high — The world has now twice independently arrived where Scott's canon already sits — Anthropic's kernel-checked 13M-line FLT artifact, then a spare-time mostly-Clau
2026-10-03T05:55:55Z
First independent replication of the workflow: a spare-time full Lean mechanization of a different paper ('From Linearity to Borrowing'), done almost entirely by Claude, moves the open question from 'is repository-scale AI formalization replicable outside Anthropic' to 'yes, at least once' — easing uncertainty on transferability even though the Anthropic artifact itself still awaits a build/scope audit. A second replication, a downstream build on the FLT repo, or an independent audit would tip the case toward accelerating.
2026-10-02T21:29:13Z
evidence attached: hn.story.49937874 — Independent spare-time full Lean mechanization done almost entirely by Claude corroborates the case's hypothesis that AI-assisted repository-scale formalization is a credible, replicable workflow.
2026-09-27T05:32:21Z
The episode has shifted from announcement-scrutiny to implications-digestion: the newest attachment is low-traction downstream analysis of what cheap formalization means, not verification of the artifact. Three weeks after the burst there is still no independent build/scope audit, provenance disclosure, or downstream implementation, so the release stands as an expert-corroborated event whose completeness, AI contribution, and workflow transferability remain open.
2026-09-27T05:22:36Z
evidence attached: hn.story.49863578 — Analysis of what cheap AI formalization implies materially contextualizes the open AI-assisted Lean-formalization episode this case anchors.
2026-09-10T20:52:37Z
The staleness check brings no new evidence, so the expert-corroborated release remains distinct from its unsettled completeness, AI-contribution, and reusable-workflow claims. Keep the case open at a slower cadence for an independent build/scope audit or substantive methodology disclosure; silence alone neither disproves the claim nor closes the episode.
2026-09-08T19:41:43Z
The discussion refresh adds no independent verification, concrete defect, or methodological disclosure; it does not change the significance of the expert-corroborated release. Completeness, AI contribution, and transferability to reusable repository-scale workflows remain open, with substantive audit or provenance evidence—not comment churn—the next meaningful trigger.
2026-09-08T00:26:49Z
The newly attached Nature coverage broadens recognition of the release and repeats the 11-day claim, but the supplied headline provides no independent build, scope audit, or AI-provenance validation. This strengthens visibility of an already expert-corroborated artifact, not the evidence that it establishes a reusable repository-scale AI workflow.
2026-09-08T00:22:22Z
evidence attached: hn.story.49604319 — Independent Nature coverage corroborates Anthropic's released Lean formalization artifact and materially strengthens the repository-scale AI-assisted mathematics episode.
2026-09-07T21:29:29Z
Refreshed discussion adds no independent verification, concrete defect, or methodological disclosure beyond the already assessed release and 11-day claim. Expert corroboration supports the release’s importance, while completeness, AI contribution, and transferability to reusable repository-scale workflows remain unsettled.
2026-09-07T03:22:48Z
The newly attached coverage makes an 11-day turnaround claim explicit, sharpening the potential long-horizon agent achievement, but supplies no independent verification of that timeline, artifact completeness, or AI contribution. It points back to the existing announcement rather than establishing a separate release or validated workflow.
2026-09-07T03:22:09Z
evidence attached: hn.story.49593340 — The first-party Anthropic announcement directly supports the open case's formalization claim, though it is not independent corroboration.
2026-09-06T19:27:59Z
The refreshed discussion adds no independent verification, concrete defect, or substantiated account of AI contribution. Expert corroboration of the release remains distinct from validation of completeness and a reusable AI-assisted workflow; build and scope audits or methodological disclosures remain the meaningful reassessment triggers.
2026-09-06T01:25:17Z
The refreshed discussion adds no substantive validation or defect report; expert corroboration of the release remains distinct from establishing completeness, AI contribution, or a reusable repository-scale workflow. Keep the case open for independent build/scope checks or methodological disclosures rather than recurring comment refreshes.
2026-09-05T23:24:28Z
The refreshed discussion adds no independent verification, concrete defect, or substantiated disclosure of AI contribution. Expert corroboration supports the release’s importance, but completeness and reusable AI-workflow claims remain unsettled; further comment refreshes alone do not warrant reassessment.
2026-09-05T22:23:55Z
The refreshed discussion adds no independent verification result, concrete defect, or substantiated disclosure of AI contribution. Expert reaction supports the release’s importance, but completeness and reusable repository-scale workflow claims remain unsettled; further audit questions alone do not change that assessment.
2026-09-05T21:23:53Z
The comment refresh adds no independent verification, concrete defect, or substantiated account of AI contribution. Expert corroboration supports the release’s importance, but completeness and transferability to repository-scale AI workflows remain unsettled; substantive audit results, not recurring discussion refreshes, should drive reassessment.
2026-09-05T20:25:10Z
The comment refresh adds no independent verification, concrete defect, or substantiated disclosure of AI contribution. Expert reaction still supports the release’s importance, but the stronger reusable AI-workflow claim remains unsettled; further comment churn is not a meaningful reassessment trigger.
2026-09-05T19:29:08Z
The refreshed discussion supplies no independent verification, concrete defect, or substantiated account of AI contribution; kernel-integrity concerns remain questions rather than counterevidence. Expert reaction supports the release’s importance, but its completeness and reusable AI-workflow implications remain unsettled, with substantive audit results—not comment churn—the next meaningful trigger.
2026-09-05T18:33:34Z
The comment refresh adds no independent verification result, concrete defect, or substantiated account of AI contribution. Expert reaction supports the release’s importance, but repetitive discussion does not establish completeness or a reusable repository-scale AI workflow; substantive audit evidence, not further comment churn, should drive the next reassessment.
2026-09-05T17:30:32Z
The discussion refresh adds no independent build or scope audit, concrete defect, or substantiated AI-contribution disclosure. Expert corroboration still supports the release’s importance, but repetitive audit questions do not establish—or undermine—its stronger repository-scale AI-workflow claims.
2026-09-05T16:27:30Z
Refreshed comments add no independent build or scope audit, concrete defect, or substantiated AI-contribution disclosure. Expert reaction still supports the release’s importance, but repetitive discussion does not establish its completeness or transferability to reusable repository-scale AI workflows.
2026-09-05T15:33:02Z
The refreshed discussion adds neither independent validation nor a concrete defect; proof-kernel concerns and claims about general model capability remain speculation. Expert reaction supports the release’s importance, but completeness, AI contribution, and transferability to reusable repository-scale workflows still require substantive checks.
2026-09-05T14:24:49Z
The refreshed discussion is repetitive amplification, not an independent verification result, concrete defect, or disclosure of the AI contribution. Expert reaction supports the release’s significance, while completeness and transferability to reusable repository-scale AI workflows remain unsettled.
2026-09-05T13:26:51Z
The refreshed comments remain discussion of auditability and maintainability, not independent verification or evidence of a defect. Expert corroboration supports the release’s importance, while completeness, AI contribution, and transferability to repository-scale agent workflows remain unsettled.
2026-09-05T12:22:57Z
The refreshed discussion adds no independent verification, concrete defect, or substantiated account of AI contribution; it remains amplification of the existing release and audit questions. Expert corroboration supports the artifact’s importance, but does not yet establish completeness or a reusable repository-scale AI workflow.
2026-09-05T10:27:10Z
The refreshed comments add interpretation, not a verification result or concrete defect; expert corroboration of the release remains distinct from validation of completeness and AI contribution. Its implications for reusable repository-scale agent workflows remain open, with no substantive change warranting promotion or hourly review.
2026-09-05T09:24:52Z
Refreshed comments add no independent verification, concrete defect, or substantiated account of AI contribution. Expert reaction supports the release’s significance, but correctness, completeness, and reusable AI-workflow implications remain distinct claims requiring substantive checks.
2026-09-05T08:26:08Z
The refreshed discussion remains amplification and audit questions, with no independent verification result, concrete defect, or substantiated AI-provenance disclosure. Expert corroboration supports the importance of the release, but not yet the stronger claim that it establishes a reusable repository-scale AI formalization workflow.
2026-09-05T07:24:19Z
Refreshed discussion adds no independent build or scope check, concrete defect, or substantiated account of the AI contribution. The expert-corroborated release remains consequential, but the claimed reusable repository-scale AI workflow remains unsettled; repetitive audit questions warrant neither promotion nor demotion.
2026-09-05T06:25:52Z
The refreshed discussion adds neither independent validation nor a concrete defect; kernel-integrity and maintainability questions remain questions, not counterevidence. The expert-corroborated release remains consequential, but its completeness and reusable AI-workflow implications still require build, scope, and provenance checks.
2026-09-05T05:23:43Z
The refreshed discussion remains amplification and audit questions, not an independent verification result or concrete defect. The expert-corroborated release remains consequential, but completeness, AI contribution, and reusable repository-scale workflow claims still await substantive checks; repeated comment refreshes do not warrant hourly review.
2026-09-05T04:26:30Z
The refreshed discussion adds no independent verification or concrete defect: proof-kernel concerns and library-maintainability questions remain unresolved rather than evidence against the release. The expert-corroborated artifact remains consequential, but its completeness, AI contribution, and implications for reusable repository-scale workflows still require substantive checks.
2026-09-05T03:23:10Z
The refreshed discussion supplies neither an independent verification result nor a concrete defect, leaving the expert-corroborated release distinct from its still-unvalidated completeness and AI-workflow claims. Repeated auditability questions do not justify hourly reassessment; the next meaningful delta is a build/scope audit or substantive disclosure of the AI contribution.
2026-09-05T02:22:44Z
The refreshed discussion adds no validation result or concrete defect; kernel-exploit concerns remain questions, not counterevidence. The expert-corroborated release remains consequential, while completeness, AI contribution, and reusable workflow claims still await independent checks.
2026-09-05T01:25:47Z
Discussion remains repetitive rather than evidentiary: questions about kernel integrity and library-quality code neither validate nor undermine the artifact. The expert-corroborated release remains consequential, but establishing a reusable AI-assisted workflow still requires independent build, scope, and provenance checks.
2026-09-05T00:29:46Z
The refreshed discussion adds technical questions about kernel integrity, maintainability, and the specific proof route, but still no independent build, completeness audit, or AI-provenance validation. The case remains an important inspectable release whose strongest repository-scale workflow claim is unsettled.
2026-09-04T23:32:19Z
Refreshed comments add only further discussion of auditability, maintainability, and Lean kernel integrity; they do not independently validate the build, completeness, or AI provenance. The case remains a consequential expert-corroborated release whose strongest workflow claims are unsettled.
2026-09-04T22:30:10Z
Refreshed discussion continues to focus on kernel integrity, auditability, and maintainability rather than supplying an independent build, scope audit, or AI-provenance check. The case’s meaning is unchanged: a consequential expert-corroborated release whose strongest completeness and automation claims remain unsettled.
2026-09-04T21:29:32Z
Kevin Buzzard’s expert reaction independently corroborates that Anthropic released a consequential, apparently full-scale FLT formalization, moving the case beyond announcement-only status. It still does not substitute for an independent build, scope audit, or verification of how much of the 13-million-line artifact was produced autonomously by AI.
2026-09-04T21:22:59Z
evidence attached: hn.story.49570133 — Independent coverage materially corroborates Anthropic's claimed complete Lean formalization of Fermat's Last Theorem.
2026-09-04T21:22:59Z
evidence attached: reddit.post.1w7gf6a — shared external link with case evidence
2026-09-04T20:43:20Z
Fresh discussion is concentrating on proof-kernel integrity and how to audit a 13-million-line artifact, but it adds no independent build, scope, or AI-provenance validation. The release remains consequential and inspectable, yet its strongest repository-scale achievement claims are still uncorroborated.
2026-09-04T19:38:51Z
Discussion broadened and surfaced Kevin Buzzard’s contextual analysis, but no independent build, scope, or provenance check has entered the evidence. The case remains a major inspectable release awaiting validation rather than a corroborated repository-scale AI achievement.
2026-09-04T19:29:16Z
grounded: converges/high — If the claimed complete artifact withstands independent build and scope checks, Anthropic has consequentially demonstrated Scott’s existing position that AI bec
2026-09-04T19:25:29Z
case created — The first-party research announcement and public Lean repository make this a substantial, inspectable claim with active technical discussion.