erdos-problems 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,29 @@
+# erdos-problems
+
+CLI atlas and staged research harness for Paul Erdos problems.
+
+## Current shape
+
+- atlas layer for seeded Erdos problems
+- sunflower cluster as the first deep harness pack
+- initial seeded problems: `20`, `536`, `856`, `857`
+- lightweight `.erdos/` workspace state for active-problem selection
+
+## CLI
+
+```bash
+erdos problem list
+erdos problem list --cluster sunflower
+erdos problem use 857
+erdos problem show
+erdos cluster list
+erdos cluster show sunflower
+erdos workspace show
+erdos dossier show
+```
+
+## Docs
+
+- `docs/ERDOS_PROBLEMS_REPO_SPEC.md`
+- `docs/ERDOS_PROBLEMS_PROBLEM_SCHEMA.md`
+- `docs/ERDOS_SUNFLOWER_CLUSTER_SEED_PLAN.md`

package/bin/erdos

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import '../src/cli/index.js';

package/docs/ERDOS_PROBLEMS_PROBLEM_SCHEMA.md

@@ -0,0 +1,196 @@
+# Erdos Problems Problem Schema
+
+Last updated: 2026-03-25
+
+## Purpose
+
+This schema defines the minimum metadata for each problem entry in `erdos-problems`.
+
+The goal is:
+
+- every Erdős problem has a consistent home
+- open and solved problems use the same shape
+- dossiers can grow without changing the core schema
+
+## Canonical File
+
+Each problem should have:
+
+- `problems/<id>/problem.yaml`
+
+## Required Fields
+
+```yaml
+problem_id: "857"
+title: "Sunflower Conjecture"
+source:
+  site: "erdosproblems.com"
+  url: "https://www.erdosproblems.com/857"
+  external_id: "857"
+status:
+  site_status: "open"
+  repo_status: "active"
+family_tags:
+  - "sunflower"
+  - "extremal-set-theory"
+problem_type:
+  kind: "open_problem"
+statement:
+  short: "Normalized problem statement"
+  normalized_md_path: "STATEMENT.md"
+references_path: "REFERENCES.md"
+evidence_path: "EVIDENCE.md"
+formalization_path: "FORMALIZATION.md"
+```
+
+## Recommended Fields
+
+```yaml
+display_name: "Erdos Problem #857"
+aliases:
+  - "weak sunflower problem"
+related_problems:
+  - "20"
+  - "536"
+  - "856"
+prize:
+  amount_usd: null
+  note: null
+domain_tags:
+  - "combinatorics"
+  - "set-systems"
+cluster: "sunflower"
+repo_links:
+  dossier_dir: "problems/857"
+  checkpoints_dir: "problems/857/CHECKPOINTS"
+  pack: "sunflower"
+formalization:
+  status: "active"
+  lean_modules:
+    - "SunflowerLean/Obstruction.lean"
+    - "SunflowerLean/ObstructionExport.lean"
+research_state:
+  open_problem: true
+  active_route: "anchored_selector_linearization"
+  route_breakthrough: true
+  problem_solved: false
+```
+
+## Status Vocabulary
+
+### `site_status`
+
+Allowed values:
+
+- `open`
+- `solved`
+- `partial`
+- `unknown`
+
+This reflects the public source.
+
+### `repo_status`
+
+Allowed values:
+
+- `cataloged`
+- `active`
+- `archived`
+- `solved_locally`
+- `historical`
+
+This reflects our local posture.
+
+### `research_state`
+
+For deep-harness problems only:
+
+- `open_problem`
+- `active_route`
+- `route_breakthrough`
+- `problem_solved`
+
+This lets us preserve the sunflower ladder without forcing it onto every problem.
+
+## Supporting Files
+
+### `STATEMENT.md`
+
+Contains:
+
+- normalized statement
+- source attribution
+- concise context
+
+### `REFERENCES.md`
+
+Contains:
+
+- literature references
+- source links
+- related problem links
+
+### `EVIDENCE.md`
+
+Contains:
+
+- verified constructions
+- theorem checkpoints
+- computational artifacts
+- failed-path summaries
+
+### `FORMALIZATION.md`
+
+Contains:
+
+- Lean status
+- code paths
+- verification hooks
+- outstanding gaps
+
+## Example: Problem 857
+
+```yaml
+problem_id: "857"
+display_name: "Erdos Problem #857"
+title: "Sunflower Conjecture"
+aliases:
+  - "weak sunflower problem"
+source:
+  site: "erdosproblems.com"
+  url: "https://www.erdosproblems.com/857"
+  external_id: "857"
+status:
+  site_status: "open"
+  repo_status: "active"
+family_tags:
+  - "sunflower"
+  - "extremal-set-theory"
+domain_tags:
+  - "combinatorics"
+  - "set-systems"
+problem_type:
+  kind: "open_problem"
+cluster: "sunflower"
+related_problems:
+  - "20"
+  - "536"
+  - "856"
+statement:
+  short: "Bound the weak sunflower number m(n,k) by C(k)^n."
+  normalized_md_path: "STATEMENT.md"
+references_path: "REFERENCES.md"
+evidence_path: "EVIDENCE.md"
+formalization_path: "FORMALIZATION.md"
+formalization:
+  status: "active"
+  lean_modules:
+    - "SunflowerLean/Obstruction.lean"
+    - "SunflowerLean/ObstructionExport.lean"
+research_state:
+  open_problem: true
+  active_route: "anchored_selector_linearization"
+  route_breakthrough: true
+  problem_solved: false
+```
+

package/docs/ERDOS_PROBLEMS_REPO_SPEC.md

@@ -0,0 +1,284 @@
+# Erdos Problems Repo Spec
+
+Last updated: 2026-03-25
+
+## Purpose
+
+This document defines a new public-facing sibling repository:
+
+- repo name target: `erdos-problems`
+- npm package target: `erdos-problems`
+- CLI executable target: `erdos`
+
+This repo is meant to be the polished atlas and harness for Paul Erdős problems.
+
+`sunflower-coda` remains the experimental proving ground.
+
+`erdos-problems` becomes the clean published surface.
+
+## Product Position
+
+`erdos-problems` should be:
+
+- a problem atlas for Paul Erdős problems
+- a research harness with staged workflows for selected problem families
+- CLI-first
+- dossier-first
+- evidence-linked
+- formalization-aware
+
+It should not be:
+
+- a clone of `sunflower-coda`
+- a raw mirror of every internal experiment
+- a generic research framework
+
+## Core Product Model
+
+The repo should have two layers.
+
+### 1. Atlas layer
+
+All Erdős problems live here, including:
+
+- open problems
+- solved problems
+- prize information
+- source links
+- tags
+- references
+- dossier links
+- formalization status
+
+Every problem gets a documented home.
+
+### 2. Harness layer
+
+Selected problem families get deeper staged research machinery.
+
+The first deep harness should be:
+
+- `sunflower`
+
+Later families can be added only if they earn it.
+
+## Naming Recommendation
+
+Recommended repo and package name:
+
+- `erdos-problems`
+
+Reason:
+
+- broader than “conjectures”
+- matches the actual scope better
+- includes solved entries naturally
+- leaves room for atlas + dossiers + harnesses
+
+As of 2026-03-25, the following npm names appeared open when checked:
+
+- `erdos-problems`
+- `erdos-conjectures`
+- `erdos-conjecture`
+
+Recommended binary name:
+
+- `erdos`
+
+## Relationship To Existing Repos
+
+### `sunflower-coda`
+
+Role:
+
+- experimental lab
+- theorem-engine proving ground
+- route-design incubator
+- UI/app experimentation
+
+### `erdos-problems`
+
+Role:
+
+- public atlas
+- clean CLI surface
+- curated problem dossiers
+- stable research harness for selected families
+
+### `ode-to-erdos`
+
+Role:
+
+- narrower theorem-work CLI
+- can either remain a focused sibling or be absorbed as an internal package inside `erdos-problems`
+
+Current recommendation:
+
+- keep `ode-to-erdos` as a focused implementation seed
+- let `erdos-problems` become the broader public shell above it
+
+## Repository Shape
+
+```text
+erdos-problems/
+  package.json
+  README.md
+  bin/
+    erdos
+  src/
+    cli/
+    commands/
+    atlas/
+    dossiers/
+    packs/
+    reporting/
+    adapters/
+  problems/
+    20/
+    536/
+    856/
+    857/
+  packs/
+    sunflower/
+  schemas/
+  templates/
+  docs/
+```
+
+## Runtime Model
+
+Local runtime folder:
+
+- `.erdos/`
+
+Suggested shape:
+
+```text
+.erdos/
+  config.json
+  state.json
+  current-problem.json
+  problems.json
+  runs/
+  registry/
+  checkpoints/
+  literature/
+```
+
+## Problem Entry Model
+
+Every problem directory should contain:
+
+```text
+problems/<id>/
+  problem.yaml
+  STATEMENT.md
+  REFERENCES.md
+  EVIDENCE.md
+  FORMALIZATION.md
+  CHECKPOINTS/
+```
+
+Not every problem needs a deep route board immediately.
+
+But every problem should have:
+
+- source URL
+- normalized statement
+- status
+- tags
+- references
+- evidence links
+
+## Harness Model
+
+The first harness pack should be:
+
+- `packs/sunflower/`
+
+That pack should preserve:
+
+- open problem
+- active route
+- route breakthrough
+- problem solved
+
+And also:
+
+- tickets
+- gates
+- atoms
+- ready queue
+- generated checkpoints
+- literature mapping
+
+## CLI Shape
+
+### Atlas commands
+
+```bash
+erdos problem list
+erdos problem show 857
+erdos problem use 857
+erdos cluster list
+erdos cluster show sunflower
+```
+
+### Dossier commands
+
+```bash
+erdos dossier show 857
+erdos dossier build 857
+erdos checkpoints sync 857
+erdos report build 857
+```
+
+### Sunflower harness commands
+
+```bash
+erdos sunflower setup 857
+erdos sunflower warnings 857
+erdos sunflower pass 857
+erdos sunflower frontier 857
+```
+
+## Content Policy
+
+The repo should not blindly mirror `erdosproblems.com` text.
+
+Safer default:
+
+- source URL
+- citation
+- normalized summary of the problem
+- our own dossier and evidence materials
+
+This keeps the repo publishable and reduces licensing ambiguity.
+
+## Launch Strategy
+
+### Phase 1
+
+- create repo
+- scaffold CLI
+- add core schema
+- seed sunflower cluster
+- ship atlas-only read commands
+
+### Phase 2
+
+- add dossier generation
+- add checkpoint shelf
+- add sunflower harness commands
+
+### Phase 3
+
+- deepen route-level automation for sunflower family
+- expand to other Erdős clusters carefully
+
+## First Public Promise
+
+The first public promise should be:
+
+> `erdos-problems` is a CLI atlas and staged research harness for Paul Erdős problems, with the sunflower family as the first deeply integrated pack.
+

package/docs/ERDOS_SUNFLOWER_CLUSTER_SEED_PLAN.md

@@ -0,0 +1,140 @@
+# Erdos Sunflower Cluster Seed Plan
+
+Last updated: 2026-03-25
+
+## Purpose
+
+This document defines the first seed cluster for the future `erdos-problems` repo.
+
+The seed cluster is:
+
+- `sunflower`
+
+## Seed Problems
+
+### `857`
+
+- source: `https://www.erdosproblems.com/857`
+- role: weak sunflower core problem
+- repo posture: primary deep-harness problem
+
+### `20`
+
+- source: `https://www.erdosproblems.com/20`
+- role: strong / uniform sunflower problem
+- repo posture: deep-harness sibling problem
+
+### `536`
+
+- source: `https://www.erdosproblems.com/536`
+- role: related LCM analogue
+- repo posture: dossier-first, later harness candidate
+
+### `856`
+
+- source: `https://www.erdosproblems.com/856`
+- role: related harmonic/log-density LCM analogue
+- repo posture: dossier-first, later harness candidate
+
+## Why These Four
+
+They form the clearest explicit sunflower-related cluster around `857`.
+
+`857` states directly that it is related to:
+
+- `536`
+- `856`
+
+and says:
+
+- `20` is the strong sunflower problem
+
+So this is a real cluster, not an arbitrary grouping.
+
+## Initial Repo Policy
+
+### Deep harness now
+
+- `857`
+- `20`
+
+### Dossier-first now
+
+- `536`
+- `856`
+
+This keeps the system honest.
+
+We should not pretend every related problem already deserves a full ticket/gate/atom board.
+
+## Initial Directory Targets
+
+```text
+problems/
+  20/
+  536/
+  856/
+  857/
+
+packs/
+  sunflower/
+```
+
+## Initial Deliverables Per Problem
+
+### For all four
+
+- `problem.yaml`
+- `STATEMENT.md`
+- `REFERENCES.md`
+- `EVIDENCE.md`
+- `FORMALIZATION.md`
+
+### For `857` and `20`
+
+Also include:
+
+- route state
+- checkpoints
+- active frontier summary
+- CLI harness wiring
+
+### For `536` and `856`
+
+Also include:
+
+- relation to sunflower cluster
+- notes on why the analogy matters
+- literature and dependency mapping
+
+## CLI Goals For Seed Phase
+
+```bash
+erdos problem list
+erdos problem show 857
+erdos cluster show sunflower
+erdos dossier build 857
+erdos sunflower frontier 857
+erdos sunflower frontier 20
+```
+
+## Immediate Build Order
+
+1. scaffold `erdos-problems`
+2. add schema + templates
+3. seed problem entries for `20`, `536`, `856`, `857`
+4. wire atlas commands
+5. wire sunflower pack commands for `857`
+6. wire sunflower pack commands for `20`
+
+## Honest Frontier
+
+The first public deep-harness promise should be:
+
+- `857` as the main weak-sunflower frontier
+- `20` as the strong-sunflower sibling frontier
+
+The first public atlas promise should be:
+
+- all seeded problems have documented statements, references, evidence, and formalization notes
+

package/package.json

@@ -0,0 +1,30 @@
+{
+  "name": "erdos-problems",
+  "version": "0.1.0",
+  "description": "CLI atlas and staged research harness for Paul Erdos problems.",
+  "type": "module",
+  "bin": {
+    "erdos": "bin/erdos"
+  },
+  "files": [
+    "README.md",
+    "LICENSE",
+    "bin",
+    "docs",
+    "packs",
+    "problems",
+    "src"
+  ],
+  "scripts": {
+    "test": "node --test",
+    "start": "node src/cli/index.js"
+  },
+  "keywords": [
+    "erdos",
+    "combinatorics",
+    "open-problems",
+    "research",
+    "sunflower"
+  ],
+  "license": "MIT"
+}

package/packs/sunflower/README.md

@@ -0,0 +1,13 @@
+# Sunflower Pack
+
+The first deep harness pack in `erdos-problems`.
+
+Current seed cluster:
+- `20`
+- `536`
+- `856`
+- `857`
+
+Deep-harness problems now:
+- `20`
+- `857`

package/problems/20/EVIDENCE.md

@@ -0,0 +1,3 @@
+# Problem 20 Evidence
+
+Current dossier placeholder for strong sunflower work.