Maintained by Fractal Research Group (frg.earth).
CLI and workspace for Paul Erdos problems.
Browse the atlas, scaffold a dossier, and keep public status, local route state, and verification records separate.
erdos-problems
atlas -> dossier -> pack -> checkpoint -> archive
erdos-problems is a CLI for working with Paul Erdos problems. It bundles problem records, local dossiers, workspace scaffolding, and pack-specific views for the problems that already have more structure in this repo.
A short example from the first minute:
- a bundled external atlas import snapshot for provenance and seeding
- local dossiers and workspace bundles
- separate surfaces for public status, local route state, and verification records
- pack-specific views where this repo already has enough structure to support them
- an ORP-based workflow for claims, checkpoints, and run artifacts
- a paper writer bundle mode for public-safe, citation-safe, agent-friendly drafting
SproutSeeds/erdos-problemsis the canonical public home for this project's atlas, dossiers, packs, and contribution workflow- the npm package is the installable CLI plus the bundled import snapshot, packaged dossiers, and packaged pack assets
- the GitHub repo is the broader public collaboration space for dossiers, pack packets, docs, issues, discussions, PRs, and future deep research bundles
.erdos/is local workspace state created by the CLI; it is not canonical repo trutherdos import showreports whether you are using the bundled import snapshot or a workspace-local refreshed import snapshoterdos import synccurrently refreshes an external atlas import snapshot fromteorth/erdosproblemswithout mutating the canonical local dossier layererdos import sync --write-package-snapshotis the maintainer path for intentionally updating the bundled import snapshot in this repo- repo-only deep-research directories such as
research/,formal/,paper/,imports/, andanalysis/are intentionally kept out of npm by staying outside thepackage.jsonfileslist - repo-only public research can live in this GitHub repo without shipping in the npm tarball; see the contribution guide: https://github.com/SproutSeeds/erdos-problems/blob/main/CONTRIBUTING.md
Install:
npm install -g erdos-problemsBootstrap a seeded problem:
erdos bootstrap problem 857
erdos sunflower frontier 857
erdos sunflower ready 857
erdos workspace show --jsonSeed a new problem into the current workspace:
erdos seed problem 25 --cluster number-theory
erdos problem show 25
erdos checkpoints syncInitialize or resume a paper bundle:
erdos paper init 857
erdos paper show 857Archive a solved problem:
erdos graph-theory status 1008
erdos archive scaffold 1008 --json| Surface | Coverage |
|---|---|
| Bundled external atlas snapshot | 1183 problems |
| Native packaged dossiers | 18 |
| Sunflower pack | 20, 536, 856, 857 |
| Number-theory pack | 1, 2 |
| Graph-theory archive pack | 19, 22, 1008 |
| Most developed pack problems | 20, 857 |
Seeded problems today:
1,2,3,4,5,6,7,18,19,20,21,22,89,536,542,856,857,1008
$ erdos sunflower frontier 857
Erdos Problem #857 sunflower frontier
Active route: anchored_selector_linearization
Active ticket: T10
First ready atom: T10.G3.A2
Checkpoint focus: keep the board packet honest around T10 while preserving the open-problem / active-route / route-breakthrough ladder.$ erdos graph-theory status 1008
Erdos Problem #1008 graph-theory harness
Family role: c4_free_lean_archive
Harness profile: lean_archive_workspace
Archive mode: method_exemplar
Problem solved: yes
First ready atom: G1008.G1.A1 — Freeze the primary Lean-facing archive hook for the `C_4`-free density resulterdos bootstrap problem 857
erdos problem artifacts 857 --json
erdos checkpoints syncWhat this does:
- sets the active workspace problem
- syncs the bundled ORP kit into
.erdos/orp/ - scaffolds the dossier into
.erdos/scaffolds/<id>/ - pulls in pack-specific context where available
- prepares the workspace for the next step
erdos seed problem 25 --cluster number-theoryWhat this does:
- pulls external public metadata into a workspace bundle
- includes live site review and an agent websearch brief by default
- seeds a local dossier into
.erdos/seeded-problems/<id>/ - syncs state, checkpoints, and ORP automatically
erdos pull problem 857
erdos pull literature 857 --include-crossref --include-openalex --jsonUse this when you want a research bundle first and a canonical dossier later.
erdos maintainer review problem 25 --from-pull .erdos/pulls/25
erdos maintainer seed problem 25 --from-pull .erdos/pulls/25 --cluster number-theoryerdos paper init 857
erdos paper show 857What this does:
- creates or resumes a paper bundle for the problem
- writes machine-readable public evidence and section indexes
- scaffolds claim-safe section drafts, a citation ledger, and a privacy review
- defaults to
paper/problems/<id>/when run inside this repo and to.erdos/papers/<id>/elsewhere
The sunflower pack currently covers this quartet:
20: strong / uniform sunflower core857: weak / non-uniform sunflower core536: natural-density LCM analogue856: harmonic-density LCM analogue
Useful commands:
erdos sunflower status 857
erdos sunflower board 857
erdos sunflower frontier 857
erdos sunflower routes 857
erdos sunflower tickets 857
erdos sunflower route 857 anchored_selector_linearization
erdos sunflower atom 857 T10.G3.A2
erdos sunflower compute run 857What is included here:
- public board packets
- route / ticket / atom views
- checkpoint and report packets
- governed local-scout compute posture where a packet exists
The number-theory pack currently includes:
1: open route-oriented starter pack around a distinct-subset-sum lane2: counterexample / archive pack
Useful commands:
erdos number-theory status 1
erdos number-theory frontier 1
erdos number-theory routes 1
erdos number-theory route 1 distinct_subset_sum_lower_bound
erdos number-theory ticket 1 N1
erdos number-theory atom 1 N1.G1.A1The graph-theory archive pack currently includes:
19: decision archive pack22: proof archive pack1008: Lean-facing proof archive pack
Useful commands:
erdos graph-theory status 19
erdos graph-theory frontier 22
erdos graph-theory routes 1008
erdos graph-theory tickets 19
erdos archive scaffold 1008 --jsonDesign rule:
- no fake live frontier for solved or decided problems
- keep the archive usable as a method exemplar
- preserve public status discipline instead of inflating pressure where none exists
If you are using Codex, Claude Code, or another coding agent, the package provides:
- canonical dossier files
- external import provenance when available
- pack-aware context where it exists
.erdos/workspace state- ORP templates and protocol guidance
- checkpoint shelves
- explicit next-step framing
- machine-readable JSON on the main public surfaces
Useful commands for agent workflows:
erdos problem artifacts 857 --json
erdos workspace show --json
erdos pull literature 857 --include-crossref --include-openalex --json
erdos import drift 857 --jsonerdos-problems ships a bundled Open Research Protocol kit:
PROTOCOL.mdAGENT_INTEGRATION.mdtemplates/CLAIM.mdtemplates/VERIFICATION_RECORD.mdtemplates/FAILED_TOPIC.md
The package keeps these layers separate:
- canonical repo truth
- external imported public truth
- workspace bundle truth
- pack-specific route / checkpoint / run truth
erdos problem list --cluster sunflower
erdos problem show 857
erdos problem artifacts 857 --json
erdos cluster list --json
erdos cluster show graph-theory
erdos workspace show --json
erdos checkpoints sync
erdos preflight
erdos sunflower frontier 857
erdos sunflower ready 857
erdos sunflower compute run 857
erdos number-theory route 1 distinct_subset_sum_lower_bound
erdos graph-theory status 1008
erdos pull problem 857
erdos pull literature 857 --include-crossref --include-openalex --json
erdos seed problem 25 --cluster number-theory
erdos maintainer review problem 25 --from-pull .erdos/pulls/25
erdos archive scaffold 1008 --json- canonical repo: https://github.com/SproutSeeds/erdos-problems
- local dossier truth:
problems/<id>/problem.yaml - bundled external import snapshot:
data/upstream/erdosproblems/ - workspace external import snapshot:
.erdos/upstream/erdosproblems/ - external atlas import repo: https://github.com/teorth/erdosproblems
- external public site: https://www.erdosproblems.com/
docs/ERDOS_PROBLEMS_REPO_SPEC.mddocs/ERDOS_PROBLEMS_PROBLEM_SCHEMA.mddocs/ERDOS_SUNFLOWER_CLUSTER_SEED_PLAN.mddocs/RESEARCH_LOOP.mddocs/LAUNCH_KIT.md
If you are preparing a public post, start here:
- docs/LAUNCH_KIT.md
assets/social-card.svgassets/terminal-demo.gif
erdosproblems.com is an external public problem source. erdos-problems imports from public sources when helpful, but keeps its canonical dossiers, packs, workflow, and contribution surface in this repo.
Yes. The package can scaffold a local .erdos/ workspace, expose machine-readable JSON on the main public surfaces, and keep public status, local route state, and verification records separate.
The sunflower pack is currently the most developed. Problems 20 and 857 have the deepest public pack surface. Problems 536 and 856 are included as bridge-oriented sunflower dossiers. The number-theory and graph-theory packs are lighter.
No. The bundled upstream atlas covers open, solved, and decided problems. Open problems can be seeded into active workspaces. Solved or decided problems can be scaffolded in archive mode and used as method exemplars.
A dossier is the local canonical folder for one problem. It usually includes problem.yaml, STATEMENT.md, REFERENCES.md, EVIDENCE.md, and FORMALIZATION.md.
No. You can start with erdos bootstrap problem <id> or erdos seed problem <id>. ORP files are bundled into the workspace for structured claims and checkpoints, and some packs include formalization-specific surfaces, but the first step does not require Lean.
erdos-problems is the canonical npm package name and it is already live on npm. The compact unscoped alias erdosproblems is not publishable because npm rejects it as too similar to erdos-problems.