erdos-problems 0.1.4 → 0.1.5

package/docs/ERDOS_PROBLEMS_REPO_SPEC.md

@@ -4,120 +4,48 @@ Last updated: 2026-03-25
 
 ## Purpose
 
-This document defines a new public-facing sibling repository:
+This document defines the public-facing `erdos-problems` repository and npm package.
 
-- repo name target: `erdos-problems`
-- npm package target: `erdos-problems`
-- CLI executable target: `erdos`
+Targets:
+- repo name: `erdos-problems`
+- npm package: `erdos-problems`
+- CLI executable: `erdos`
 
-This repo is meant to be the polished atlas and harness for Paul Erdős problems.
+`sunflower-coda` remains the experimental lab.
+`erdos-problems` is the clean public atlas and harness surface.
 
-`sunflower-coda` remains the experimental proving ground.
-
-`erdos-problems` becomes the clean published surface.
-
-## Product Position
-
-`erdos-problems` should be:
+## Product position
 
+`erdos-problems` is:
 - a problem atlas for Paul Erdős problems
-- a research harness with staged workflows for selected problem families
-- CLI-first
-- dossier-first
-- evidence-linked
+- a dossier-first CLI research harness
+- provenance-aware
 - formalization-aware
+- agent-friendly from first install
 
-It should not be:
-
-- a clone of `sunflower-coda`
-- a raw mirror of every internal experiment
+It is not:
+- a raw mirror of `sunflower-coda`
 - a generic research framework
+- a place where local route state silently overwrites public upstream truth
 
-## Core Product Model
+## Core model
 
-The repo should have two layers.
+The repo has three 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:
+All seeded Erdős problems live here with canonical local dossiers.
 
-- public atlas
-- clean CLI surface
-- curated problem dossiers
-- stable research harness for selected families
+### 2. Upstream truth layer
 
-### `ode-to-erdos`
+The package ships a bundled snapshot of `teorth/erdosproblems` and can refresh a workspace-local snapshot.
 
-Role:
+### 3. Harness layer
 
-- narrower theorem-work CLI
-- can either remain a focused sibling or be absorbed as an internal package inside `erdos-problems`
+Selected problem families get deeper pack-specific context.
+The first pack is `sunflower`.
 
-Current recommendation:
-
-- keep `ode-to-erdos` as a focused implementation seed
-- let `erdos-problems` become the broader public shell above it
-
-## Repository Shape
+## Repository shape
 
 ```text
 erdos-problems/
@@ -129,94 +57,76 @@ erdos-problems/
     cli/
     commands/
     atlas/
-    dossiers/
-    packs/
-    reporting/
-    adapters/
+    runtime/
+    upstream/
   problems/
-    20/
-    536/
-    856/
-    857/
+    <id>/
   packs/
     sunflower/
-  schemas/
-  templates/
+      README.md
+      problems/<id>/
+      compute/<id>/
+  data/upstream/erdosproblems/
   docs/
 ```
 
-## Runtime Model
-
-Local runtime folder:
-
-- `.erdos/`
+## Runtime model
 
-Suggested shape:
+Local workspace runtime:
 
 ```text
 .erdos/
-  config.json
   state.json
   current-problem.json
-  problems.json
-  runs/
+  upstream/erdosproblems/
+  scaffolds/<id>/
+  pulls/<id>/
+    artifacts/
+    literature/
   registry/
-  checkpoints/
-  literature/
 ```
 
-## Problem Entry Model
+## Dossier model
 
-Every problem directory should contain:
-
-```text
-problems/<id>/
-  problem.yaml
-  STATEMENT.md
-  REFERENCES.md
-  EVIDENCE.md
-  FORMALIZATION.md
-  CHECKPOINTS/
-```
+Each canonical seeded dossier contains:
+- `problem.yaml`
+- `STATEMENT.md`
+- `REFERENCES.md`
+- `EVIDENCE.md`
+- `FORMALIZATION.md`
 
-Not every problem needs a deep route board immediately.
+## Pull model
 
-But every problem should have:
+`erdos pull problem <id>` creates a root pull bundle with two sub-lanes:
+- `artifacts/`
+- `literature/`
 
-- source URL
-- normalized statement
-- status
-- tags
-- references
-- evidence links
+`erdos pull artifacts <id>` and `erdos pull literature <id>` target those lanes directly.
 
-## Harness Model
+## Maintainer model
 
-The first harness pack should be:
+`erdos maintainer seed problem <id>` promotes a pulled bundle into a canonical local dossier.
 
-- `packs/sunflower/`
+This is the disciplined bridge from:
+- public upstream/site truth
+- to local canonical dossier truth
 
-That pack should preserve:
+## Sunflower pack model
 
-- open problem
-- active route
-- route breakthrough
-- problem solved
+The sunflower pack now explicitly covers the quartet:
+- `20`: strong sunflower core
+- `857`: weak sunflower core
+- `536`: natural-density LCM analogue
+- `856`: harmonic-density LCM analogue
 
-And also:
+Pack assets may include:
+- pack README context
+- per-problem context files
+- compute packets for deep problems
 
-- tickets
-- gates
-- atoms
-- ready queue
-- compute lane awareness
-- generated checkpoints
-- literature mapping
-
-## CLI Shape
-
-### Atlas commands
+## CLI shape
 
+Atlas:
 ```bash
 erdos problem list
 erdos problem show 857
@@ -225,70 +135,43 @@ erdos cluster list
 erdos cluster show sunflower
 ```
 
-### Dossier commands
-
+Workspace and artifacts:
 ```bash
-erdos dossier show 857
-erdos dossier build 857
-erdos checkpoints sync 857
-erdos report build 857
+erdos workspace show
+erdos problem artifacts 857 --json
+erdos scaffold problem 857
+erdos bootstrap problem 857
 ```
 
-### Sunflower harness commands
-
+Pull and maintainer flow:
 ```bash
-erdos sunflower setup 857
-erdos sunflower warnings 857
-erdos sunflower pass 857
-erdos sunflower frontier 857
-erdos sunflower status 857
+erdos pull problem 1
+erdos pull artifacts 857
+erdos pull literature 857 --include-site
+erdos maintainer seed problem 1 --from-pull .erdos/pulls/1 --cluster number-theory
 ```
 
-`erdos sunflower status` should be the public-shell place where route state and
-compute posture meet:
-
-- active route
-- breakthrough state
-- packaged compute lane
-- next compute action
-- whether paid approval is required
-
-## 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
+Sunflower pack:
+```bash
+erdos sunflower status 20
+erdos sunflower status 536
+erdos sunflower status 857 --json
+```
 
-- deepen route-level automation for sunflower family
-- expand to other Erdős clusters carefully
+## Canonical truth split
 
-## First Public Promise
+Public upstream truth:
+- `teorth/erdosproblems`
+- `data/problems.yaml`
+- `erdosproblems.com`
 
-The first public promise should be:
+Local atlas truth:
+- `problems/<id>/problem.yaml`
+- dossier markdown files beside it
 
-> `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.
+Local harness truth:
+- research state
+- checkpoints
+- pack context
+- compute packets
+- workspace pull/scaffold artifacts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "erdos-problems",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "CLI atlas and staged research harness for Paul Erdos problems.",
   "type": "module",
   "bin": {

package/packs/sunflower/README.md

@@ -2,12 +2,14 @@
 
 The first deep harness pack in `erdos-problems`.
 
-Current seed cluster:
+Sunflower core quartet:
 - `20`
 - `536`
 - `856`
 - `857`
 
-Deep-harness problems now:
-- `20`
-- `857`
+Profiles:
+- `20`: deep harness, strong / uniform core
+- `857`: deep harness, weak / non-uniform core
+- `536`: dossier bridge, natural-density LCM analogue
+- `856`: dossier bridge, harmonic-density LCM analogue

package/packs/sunflower/problems/20/CONTEXT.md

@@ -0,0 +1,9 @@
+# Problem 20 Sunflower Context
+
+Role in family:
+- strong / uniform sunflower core
+- deep-harness sibling to the weak sunflower program on 857
+
+Bootstrap focus:
+- start from the uniform k=3 lane
+- keep explicit bridges back to 857 whenever a route or method transfers cleanly

package/packs/sunflower/problems/20/context.yaml

@@ -0,0 +1,18 @@
+problem_id: "20"
+family_role: strong_sunflower_core
+harness_profile: deep
+default_active_route: uniform_k3_frontier
+bootstrap_focus: Frame the strong or uniform k=3 sunflower lane as the direct sibling frontier to the weak 857 route.
+related_core_problems:
+  - "857"
+  - "536"
+  - "856"
+literature_focus:
+  - strong sunflower problem
+  - k-uniform families
+  - k=3
+  - Erdos-Rado sunflower
+artifact_focus:
+  - uniform-family reductions
+  - k=3 active route notes
+  - bridge notes to 857

package/packs/sunflower/problems/536/CONTEXT.md

@@ -0,0 +1,9 @@
+# Problem 536 Sunflower Context
+
+Role in family:
+- natural-density LCM analogue inside the sunflower quartet
+- dossier-first bridge problem rather than a deep theorem harness today
+
+Bootstrap focus:
+- keep the combinatorial relation to 857 explicit
+- collect number-theoretic translations, references, and bridge artifacts

package/packs/sunflower/problems/536/context.yaml

@@ -0,0 +1,17 @@
+problem_id: "536"
+family_role: natural_density_lcm_analogue
+harness_profile: dossier_bridge
+default_active_route: natural_density_lcm_bridge
+bootstrap_focus: Treat 536 as the number-theoretic natural-density analogue that should stay tightly linked to weak sunflower progress.
+related_core_problems:
+  - "857"
+  - "856"
+  - "20"
+literature_focus:
+  - lcm analogue
+  - natural density
+  - weak sunflower transfer
+artifact_focus:
+  - analogue statements
+  - bridge notes to 857
+  - number-theoretic translation artifacts

package/packs/sunflower/problems/856/CONTEXT.md

@@ -0,0 +1,9 @@
+# Problem 856 Sunflower Context
+
+Role in family:
+- harmonic-density LCM analogue inside the sunflower quartet
+- dossier-first bridge problem with direct implications for 857-style exponents
+
+Bootstrap focus:
+- keep the exponent-transfer story explicit
+- collect references and structured bridge artifacts for future deepening

package/packs/sunflower/problems/856/context.yaml

@@ -0,0 +1,17 @@
+problem_id: "856"
+family_role: harmonic_density_lcm_analogue
+harness_profile: dossier_bridge
+default_active_route: harmonic_density_lcm_bridge
+bootstrap_focus: Treat 856 as the harmonic-density LCM analogue whose exponent behavior should stay synchronized with weak sunflower progress.
+related_core_problems:
+  - "857"
+  - "536"
+  - "20"
+literature_focus:
+  - harmonic density
+  - lcm analogue
+  - exponent transfer to 857
+artifact_focus:
+  - analogue statements
+  - density bridge notes
+  - exponent-comparison artifacts

package/packs/sunflower/problems/857/CONTEXT.md

@@ -0,0 +1,9 @@
+# Problem 857 Sunflower Context
+
+Role in family:
+- weak / non-uniform sunflower core
+- current deep-harness flagship problem in the public atlas
+
+Bootstrap focus:
+- preserve the live route framing in the scaffold
+- keep literature, artifact, and compute packets aligned with the active frontier rather than generic sunflower chatter

package/packs/sunflower/problems/857/context.yaml

@@ -0,0 +1,18 @@
+problem_id: "857"
+family_role: weak_sunflower_core
+harness_profile: deep
+default_active_route: anchored_selector_linearization
+bootstrap_focus: Start from the weak sunflower asymptotic route and preserve the active export/compression frontier in the scaffold.
+related_core_problems:
+  - "20"
+  - "536"
+  - "856"
+literature_focus:
+  - weak sunflower problem
+  - m(n,3)
+  - asymptotic routes
+  - container and export methods
+artifact_focus:
+  - active route notes
+  - formal frontier checkpoints
+  - compute lane packets when frozen

package/problems/20/problem.yaml

@@ -20,14 +20,15 @@ prize:
   display: $1000
 related_problems:
   - "857"
+  - "536"
+  - "856"
 family_tags:
   - sunflower
   - uniform-families
 harness:
   depth: deep
 statement:
-  short: Determine the strong sunflower threshold for k-uniform set systems, with
-    the k=3 lane as the immediate active frontier.
+  short: Determine the strong sunflower threshold for k-uniform set systems, with the uniform k=3 lane as the immediate active frontier.
   normalized_md_path: STATEMENT.md
 references_path: REFERENCES.md
 evidence_path: EVIDENCE.md
@@ -36,3 +37,8 @@ formalization:
   status: active
   upstream_state: yes
   upstream_last_update: 2025-08-31
+research_state:
+  open_problem: true
+  active_route: uniform_k3_frontier
+  route_breakthrough: false
+  problem_solved: false

package/problems/536/problem.yaml

@@ -12,7 +12,7 @@ upstream:
 status:
   site_status: open
   site_badge: OPEN
-  repo_status: cataloged
+  repo_status: active
   upstream_status: open
   upstream_last_update: 2025-08-31
 cluster: sunflower
@@ -20,14 +20,15 @@ prize:
   display: no
 related_problems:
   - "857"
+  - "856"
+  - "20"
 family_tags:
   - sunflower-analogue
   - number-theory
 harness:
   depth: dossier
 statement:
-  short: Number-theoretic analogue of the sunflower problem framed through least
-    common multiples.
+  short: Number-theoretic analogue of the sunflower problem framed through least common multiples and natural-density structure.
   normalized_md_path: STATEMENT.md
 references_path: REFERENCES.md
 evidence_path: EVIDENCE.md
@@ -36,3 +37,8 @@ formalization:
   status: planned
   upstream_state: yes
   upstream_last_update: 2025-11-12
+research_state:
+  open_problem: true
+  active_route: natural_density_lcm_bridge
+  route_breakthrough: false
+  problem_solved: false

package/problems/856/problem.yaml

@@ -12,7 +12,7 @@ upstream:
 status:
   site_status: open
   site_badge: OPEN
-  repo_status: cataloged
+  repo_status: active
   upstream_status: open
   upstream_last_update: 2025-08-31
 cluster: sunflower
@@ -20,14 +20,15 @@ prize:
   display: no
 related_problems:
   - "857"
+  - "536"
+  - "20"
 family_tags:
   - sunflower-analogue
   - number-theory
 harness:
   depth: dossier
 statement:
-  short: A harmonic or density-shaped LCM analogue whose exponents are explicitly
-    linked to progress on the weak sunflower problem.
+  short: A harmonic or density-shaped LCM analogue whose exponent behavior is explicitly linked to progress on the weak sunflower problem.
   normalized_md_path: STATEMENT.md
 references_path: REFERENCES.md
 evidence_path: EVIDENCE.md
@@ -36,3 +37,8 @@ formalization:
   status: planned
   upstream_state: no
   upstream_last_update: 2025-08-31
+research_state:
+  open_problem: true
+  active_route: harmonic_density_lcm_bridge
+  route_breakthrough: false
+  problem_solved: false

package/src/cli/index.js

@@ -1,6 +1,7 @@
 import { runBootstrapCommand } from '../commands/bootstrap.js';
 import { runClusterCommand } from '../commands/cluster.js';
 import { runDossierCommand } from '../commands/dossier.js';
+import { runMaintainerCommand } from '../commands/maintainer.js';
 import { runProblemCommand } from '../commands/problem.js';
 import { runPullCommand } from '../commands/pull.js';
 import { runScaffoldCommand } from '../commands/scaffold.js';
@@ -28,6 +29,9 @@ function printUsage() {
   console.log('  erdos scaffold problem <id> [--dest <path>]');
   console.log('  erdos bootstrap problem <id> [--dest <path>] [--sync-upstream]');
   console.log('  erdos pull problem <id> [--dest <path>] [--include-site] [--refresh-upstream]');
+  console.log('  erdos pull artifacts <id> [--dest <path>] [--refresh-upstream]');
+  console.log('  erdos pull literature <id> [--dest <path>] [--include-site] [--refresh-upstream]');
+  console.log('  erdos maintainer seed problem <id> [--from-pull <path>] [--dest-root <path>] [--cluster <name>]');
 }
 
 const args = process.argv.slice(2);
@@ -55,6 +59,8 @@ if (!command || command === 'help' || command === '--help') {
   exitCode = await runBootstrapCommand(rest);
 } else if (command === 'pull') {
   exitCode = await runPullCommand(rest);
+} else if (command === 'maintainer') {
+  exitCode = runMaintainerCommand(rest);
 } else {
   console.error(`Unknown command: ${command}`);
   printUsage();