VibeMathed

vibemathed.com is a community of mathematicians and enthusiasts tracking, curating and cataloguing the mathematical problems that have been solved, fully or partially, by AI models - from famous conjectures to the long tail of specialist questions and the numbered Erdős problems.

Not a scrape, not a leaderboard. Every entry cites a real, checkable primary source, and results that are unrefereed, partial, or actively disputed are labeled as such rather than left out or overstated. The methodology documents what qualifies and how every label is assigned.

689 published entries across twelve areas of mathematics, 480 of them fully resolved, and eight frontiers, as of 6 September 2026. The stats page carries the live figures.

What an entry carries

• Result (proved / disproved) and status (resolved, partial, variant, candidate under review, retracted)
• A verification ladder from Lean-kernel-checked down to contested
• An AI contribution tier: did the model discover the mathematics, co-develop named steps, or assist a human-led proof
• A significance score, 0-100 against an anchored ladder (Riemann hypothesis = 100), assigned with a published prompt
• Community machinery: submissions with review, field-level edits with a public changelog, discussion threads, votes, flagging, and member profiles - all under pseudonyms only (real names, emails and avatars are never shown)

Frontiers

Not every AI result resolves a question. Some move a number: the exponent of matrix multiplication, the proportion of zeta zeros proved to lie on the critical line, the bound on gaps between consecutive primes. A frontier is one such quantity with a direction and a dated staircase of every best known value, human and AI alike, so a reader can see whether a model actually moved a number people had been pushing for decades. vibemathed.com/frontiers.

Frontiers are curated rather than submitted. The current best is derived from the rows rather than stored, so it cannot go stale when a row is added, retracted or re-dated.

How a submission becomes an entry

Anyone signed in can submit. A curator reads the source - the paper, the repository, the Lean development - and either publishes the entry with its tiers filled in, or holds it with a written reason that lands in the submitter's inbox. While it waits, the queue is public at vibemathed.com/queue: titles and ages only, under a banner saying that nothing there is part of the record yet.

When a claim ships a Lean development, the site can rebuild it instead of trusting a badge. .github/workflows/verify-lean.yml checks out someone else's repository at a pinned ref, installs the toolchain that repository names, builds every module and prints the axioms its theorems really use. That is what the Site-confirmed tier means here. It checks a proof against the statement its author wrote; whether that statement says what the informal problem says is a human's job, and the reviewing checklist says so.

Data

The complete dataset is one request away: vibemathed.com/api/dataset. What the site wrote is CC BY 4.0; quoted material from the papers is not ours to license. See vibemathed.com/data-license.

The database is the source of truth. src/data/problems.json is the seed baseline and disaster-recovery snapshot, refreshed with npm run db:export after catalog changes; npm run db:seed rebuilds a fresh database from it. Community edits are audited in the ProblemActivity table, not in git.

Stack

Next.js (App Router, v16) + TypeScript + Tailwind v4, CockroachDB (serverless, Postgres-compatible) via Prisma, Auth.js (next-auth v5) with Google and GitHub as sign-in providers, Vitest for the unit tests. Deployed on Vercel.

Cache Components (cacheComponents: true) is enabled, so Partial Prerendering is the default: each page ships a prerendered static shell, and the parts that depend on the viewer stream in. That is what keeps every entry page indexable while still showing a live vote tally.

See the root AGENTS.md before making framework-level changes; this Next.js version postdates a lot of training data.

Local development

There is no bundled local database - point DATABASE_URL at any Postgres-compatible database (CockroachDB serverless has a free tier). Copy .env.example to .env (the Prisma CLI reads .env, not .env.local) and fill in the database URL, an AUTH_SECRET (npx auth secret), and a Google OAuth client of your own.

npm install
npm run db:push      # sync schema (no migrations dir)
npm run db:seed      # load problems.json (idempotent)
npm run dev

Open http://localhost:3000.

CockroachDB quirks

• A newly created database on a multi-region cluster can carry crdb_internal_region metadata that breaks prisma db push. Fix once: ALTER DATABASE vibemathed DROP REGION "<region>";
• CockroachDB v26 creates tables with schema_locked = true, which breaks Prisma's multi-step pushes. Unlock any newly added table with ALTER TABLE "<name>" SET (schema_locked = false); if a push fails on it.

Scripts

npm run build needs a reachable DATABASE_URL: the most-visited entry pages are prerendered from the database via generateStaticParams.

Contributing

Catalog contributions - new entries, corrections, challenges to a claim - go through the site rather than through git, because the catalog lives in a database: see vibemathed.com/contributing.

For code, see CONTRIBUTING.md. Pull requests go to main, which is where everything lands first and which deploys to the staging environment. production is the branch vibemathed.com serves, and it moves only by a deliberate promotion: a pull request from main, merged when someone decides to release. Both branches require a green CI run and one approving review; CI runs Prisma schema validation, ESLint, tsc, the Vitest suite and a parse of the seed baseline. docs/branch-flow.md explains why the flow is shaped this way and records how it was migrated.

License

Code is MIT (see LICENSE).

Catalog content is mixed and the distinction matters: the classifications, verification tiers, significance scores, curator notes and the structure of the dataset are VibeMathed's own and are CC BY 4.0. Material quoted from the papers an entry cites - abstracts, passages, figures - belongs to its authors and is not relicensed by appearing here. vibemathed.com/data-license is the canonical statement, and /api/dataset points at it rather than asserting one licence over both.