erdos-problems 0.2.6 → 0.2.8

package/README.md

@@ -98,7 +98,7 @@ Checkpoint focus: keep the board packet honest around T10 while preserving the o
 $ erdos graph-theory status 1008
 Erdos Problem #1008 graph-theory harness
 Family role: c4_free_lean_archive
-Harness profile: lean_archive_cockpit
+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 result
@@ -305,8 +305,32 @@ If you are preparing a public post, start here:
 - `assets/social-card.svg`
 - `assets/terminal-demo.gif`
 
-## Notes
+## FAQ
 
-- `erdos-problems` is the canonical npm package name.
-- the package is already live on npm.
-- the compact unscoped alias `erdosproblems` is not publishable because npm rejects it as too similar to `erdos-problems`.
+### What is the difference between this and erdosproblems.com?
+
+`erdosproblems.com` is a public problem atlas. `erdos-problems` uses that public record, but adds local dossiers, workspace scaffolding, checkpoints, and pack-specific views for the problems that already have more structure here.
+
+### Can I use this with Codex, Claude Code, or another agent?
+
+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.
+
+### Which problems are most developed right now?
+
+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.
+
+### Does it only cover open problems?
+
+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.
+
+### What is a dossier?
+
+A dossier is the local canonical folder for one problem. It usually includes `problem.yaml`, `STATEMENT.md`, `REFERENCES.md`, `EVIDENCE.md`, and `FORMALIZATION.md`.
+
+### Do I need Lean or ORP to start using it?
+
+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.
+
+### Why is the npm package called `erdos-problems` and not `erdosproblems`?
+
+`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`.

package/docs/RESEARCH_LOOP.md

@@ -75,7 +75,7 @@ For sunflower compute lanes, ORP sits above `breakthroughs`:
 - `erdos sunflower board <id>` exposes the packaged atomic or bridge board for the active sunflower problem
 - `erdos sunflower ready <id>` exposes the dependency-satisfied ready queue for the packaged board
 - `erdos sunflower ladder <id>` exposes the first-principles ladder for the packaged board
-- `erdos sunflower frontier <id>` exposes the compressed cockpit view for the active board
+- `erdos sunflower frontier <id>` exposes the compressed frontier view for the active board
 - `erdos sunflower routes <id>` exposes the public route table for the packaged board
 - `erdos sunflower tickets <id>` exposes the ticket table for the packaged board
 - `erdos sunflower route <id> <route-id>` exposes the deeper public route packet

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "erdos-problems",
-  "version": "0.2.6",
+  "version": "0.2.8",
   "description": "CLI atlas and workspace tools for Paul Erdos problems.",
   "type": "module",
   "bin": {

package/packs/graph-theory/README.md

@@ -1,11 +1,11 @@
 # Graph-Theory Pack
 
-Archive and decision cockpit for graph-theory problems in `erdos-problems`.
+Archive and decision workspace for graph-theory problems in `erdos-problems`.
 
-Current seeded cockpit problems:
-- `19`: decision/archive cockpit around the chromatic-number record
-- `22`: proof archive cockpit around the Ramsey-Turan `K_4` construction record
-- `1008`: Lean-facing proof archive cockpit for the `C_4`-free density problem
+Current seeded pack problems:
+- `19`: decision/archive workspace around the chromatic-number record
+- `22`: proof archive workspace around the Ramsey-Turan `K_4` construction record
+- `1008`: Lean-facing proof archive workspace for the `C_4`-free density problem
 
 Useful commands:
 - `erdos graph-theory status 19`
@@ -14,4 +14,4 @@ Useful commands:
 - `erdos graph-theory tickets 1008`
 
 Design rule:
-- keep this pack honest as an archive/decision cockpit until a real open graph-theory frontier earns deeper gated flow
+- keep this pack honest as an archive/decision workspace until a real open graph-theory frontier earns deeper gated flow

package/packs/graph-theory/problems/1008/CONTEXT.md

@@ -2,7 +2,7 @@
 
 Role in pack:
 - Lean-facing proof archive for the `C_4`-free density problem
-- solved graph-theory cockpit rather than a live open frontier
+- solved graph-theory workspace rather than a live open frontier
 
 Bootstrap focus:
 - preserve the solved status and Lean-facing badge

package/packs/graph-theory/problems/1008/OPS_DETAILS.yaml

@@ -1,5 +1,5 @@
 packet_id: gt1008_ops_details_v1
-summary: Lean-facing proof archive cockpit packet for the `C_4`-free density result.
+summary: Lean-facing proof archive workspace packet for the `C_4`-free density result.
 routes:
   - route_id: c4_free_lean_archive
     title: "`C_4`-Free Lean Proof Archive"

package/packs/graph-theory/problems/1008/ROUTE_HISTORY.md

@@ -1,5 +1,5 @@
 # Problem 1008 Route History
 
-- Initial public pack lift: moved the dossier into a graph-theory Lean archive cockpit.
+- Initial public pack lift: moved the dossier into a graph-theory Lean archive workspace.
 - Current route: `c4_free_lean_archive`.
 - Honest next improvement: freeze the best Lean-facing source hook and checkpoint the archive packet.

package/packs/graph-theory/problems/1008/context.yaml

@@ -1,6 +1,6 @@
 problem_id: "1008"
 family_role: c4_free_lean_archive
-harness_profile: lean_archive_cockpit
+harness_profile: lean_archive_workspace
 default_active_route: c4_free_lean_archive
 bootstrap_focus: Freeze the `C_4`-free density result as a Lean-facing archive packet and keep the solved status synchronized with the public dossier.
 route_story: Problem 1008 is a formalization-flavored proof archive. The public job is to preserve the solved record, the Lean-facing posture, and the core extremal-graph framing without re-opening a closed problem.

package/packs/graph-theory/problems/19/CONTEXT.md

@@ -2,7 +2,7 @@
 
 Role in pack:
 - chromatic-number decision archive
-- graph-theory archive cockpit rather than a live theorem frontier today
+- graph-theory archive workspace rather than a live theorem frontier today
 
 Bootstrap focus:
 - keep the public decision posture explicit

package/packs/graph-theory/problems/19/FRONTIER_NOTE.md

@@ -5,4 +5,4 @@ This is an archive-facing graph-theory packet.
 Current honest posture:
 - preserve the public decision status
 - keep the chromatic-number framing explicit
-- do not re-inflate the dossier into an open-problem cockpit
+- do not re-inflate the dossier into an open-problem workspace

package/packs/graph-theory/problems/19/OPS_DETAILS.yaml

@@ -1,5 +1,5 @@
 packet_id: gt19_ops_details_v1
-summary: Decision/archive cockpit packet for the chromatic-number record.
+summary: Decision/archive workspace packet for the chromatic-number record.
 routes:
   - route_id: chromatic_decision_record
     title: Chromatic Decision Record

package/packs/graph-theory/problems/19/ROUTE_HISTORY.md

@@ -1,5 +1,5 @@
 # Problem 19 Route History
 
-- Initial public pack lift: moved the dossier into a graph-theory decision archive cockpit.
+- Initial public pack lift: moved the dossier into a graph-theory decision archive workspace.
 - Current route: `chromatic_decision_record`.
 - Honest next improvement: freeze the best source explaining the decision posture and checkpoint it.

package/packs/graph-theory/problems/19/context.yaml

@@ -1,9 +1,9 @@
 problem_id: "19"
 family_role: chromatic_number_decision_archive
-harness_profile: decision_archive_cockpit
+harness_profile: decision_archive_workspace
 default_active_route: chromatic_decision_record
 bootstrap_focus: Freeze the exact chromatic-number decision posture, the dossier provenance, and the archive packet without drifting back into open-problem language.
-route_story: Problem 19 is currently best treated as a decision/archive cockpit. The public job is to preserve the decision record and its references cleanly enough that future agents do not mis-handle it as a live open frontier.
+route_story: Problem 19 is currently best treated as a decision/archive workspace. The public job is to preserve the decision record and its references cleanly enough that future agents do not mis-handle it as a live open frontier.
 frontier_label: chromatic_decision_record
 frontier_detail: Keep the decision posture and the primary chromatic-number source trail explicit.
 checkpoint_focus: Synchronize the public decision status, archive packet, and primary references every time this dossier is touched.

package/packs/graph-theory/problems/22/CONTEXT.md

@@ -2,7 +2,7 @@
 
 Role in pack:
 - Ramsey-Turan proof archive
-- solved graph-theory cockpit rather than a live open frontier
+- solved graph-theory workspace rather than a live open frontier
 
 Bootstrap focus:
 - preserve the solved status cleanly

package/packs/graph-theory/problems/22/OPS_DETAILS.yaml

@@ -1,5 +1,5 @@
 packet_id: gt22_ops_details_v1
-summary: Proof archive cockpit packet for the Ramsey-Turan `K_4` record.
+summary: Proof archive workspace packet for the Ramsey-Turan `K_4` record.
 routes:
   - route_id: ramsey_turan_k4_archive
     title: Ramsey-Turan `K_4` Proof Archive

package/packs/graph-theory/problems/22/ROUTE_HISTORY.md

@@ -1,5 +1,5 @@
 # Problem 22 Route History
 
-- Initial public pack lift: moved the dossier into a graph-theory proof archive cockpit.
+- Initial public pack lift: moved the dossier into a graph-theory proof archive workspace.
 - Current route: `ramsey_turan_k4_archive`.
 - Honest next improvement: freeze the best source trail and keep the solved wording maximally clear.

package/packs/graph-theory/problems/22/context.yaml

@@ -1,9 +1,9 @@
 problem_id: "22"
 family_role: ramsey_turan_proof_archive
-harness_profile: proof_archive_cockpit
+harness_profile: proof_archive_workspace
 default_active_route: ramsey_turan_k4_archive
 bootstrap_focus: Freeze the solved Ramsey-Turan `K_4` record as a proof archive and keep its dossier wording aligned with the public solved status.
-route_story: Problem 22 is a proof archive cockpit. The public job is to preserve the solved status, the Ramsey-Turan framing, and the main source trail without pretending there is a live frontier here.
+route_story: Problem 22 is a proof archive workspace. The public job is to preserve the solved status, the Ramsey-Turan framing, and the main source trail without pretending there is a live frontier here.
 frontier_label: ramsey_turan_k4_archive
 frontier_detail: Preserve the affirmative proof posture and the extremal graph framing without blurring it into an open program.
 checkpoint_focus: Keep the proof archive wording, the public solved status, and the main source trail synchronized.
@@ -20,7 +20,7 @@ question_ledger:
   open_questions:
     - Which exact reference should anchor the proof archive packet first?
   active_route_notes:
-    - Treat Problem 22 as a proof archive, not as a live open cockpit.
+    - Treat Problem 22 as a proof archive, not as a live open workspace.
   route_breakthroughs: []
   problem_solved:
     - The public site marks this problem as proved.

package/packs/number-theory/README.md

@@ -1,10 +1,10 @@
 # Number Theory Pack
 
-Light starter cockpit for number-theory problems in `erdos-problems`.
+Light starter workspace for number-theory problems in `erdos-problems`.
 
-Current seeded cockpit problems:
-- `1`: open starter cockpit around a distinct-subset-sum lower-bound route
-- `2`: counterexample/archive cockpit for a disproved covering-systems problem
+Current seeded pack problems:
+- `1`: open starter workspace around a distinct-subset-sum lower-bound route
+- `2`: counterexample/archive workspace for a disproved covering-systems problem
 
 Useful commands:
 - `erdos number-theory status 1`

package/packs/number-theory/problems/1/FRONTIER_NOTE.md

@@ -1,6 +1,6 @@
 # Problem 1 Frontier Note
 
-This is a starter cockpit, not a deep theorem board.
+This is a starter workspace, not a deep theorem board.
 
 The honest live route is the distinct-subset-sum lower-bound route:
 - keep the problem statement exact

package/packs/number-theory/problems/1/OPS_DETAILS.yaml

@@ -1,18 +1,18 @@
 packet_id: nt1_ops_details_v1
-summary: Starter cockpit packet for the distinct-subset-sum lower-bound route.
+summary: Starter workspace packet for the distinct-subset-sum lower-bound route.
 routes:
   - route_id: distinct_subset_sum_lower_bound
     title: Distinct Subset-Sum Lower Bound
     status: active
     summary: Keep the problem centered on the exponential-growth lower-bound route implied by distinct subset sums.
-    why_now: This is the smallest honest route that turns the dossier into a real cockpit.
+    why_now: This is the smallest honest route that turns the dossier into a real workspace.
     next_move: Freeze the first exact reduction and connect it to the canonical references.
 tickets:
   - ticket_id: N1
     title: Freeze the lower-bound route note
     route_id: distinct_subset_sum_lower_bound
     status: active
-    summary: Turn the starter dossier into a stable lower-bound cockpit.
+    summary: Turn the starter dossier into a stable lower-bound workspace.
     current_blocker: The first exact reduction and evidence stack are not yet frozen together.
     next_move: Close `N1.G1.A1`.
 atoms:
@@ -21,5 +21,5 @@ atoms:
     route_id: distinct_subset_sum_lower_bound
     ticket_id: N1
     status: ready
-    summary: This is the smallest honest move that upgrades the dossier into a route-aware cockpit.
+    summary: This is the smallest honest move that upgrades the dossier into a route-aware workspace.
     next_move: Record the first reduction and checkpoint it without overclaiming theorem progress.

package/packs/number-theory/problems/1/ROUTE_HISTORY.md

@@ -1,5 +1,5 @@
 # Problem 1 Route History
 
 - Initial public pack posture: dossier-first seed.
-- Current public pack posture: starter cockpit around the distinct-subset-sum lower-bound route.
+- Current public pack posture: starter workspace around the distinct-subset-sum lower-bound route.
 - Next maturity threshold: freeze the first exact reduction or historical lower-bound checkpoint before adding deeper pack machinery.

package/packs/number-theory/problems/1/context.yaml

@@ -1,9 +1,9 @@
 problem_id: "1"
 family_role: additive_number_theory_seed
-harness_profile: starter_cockpit
+harness_profile: starter_workspace
 default_active_route: distinct_subset_sum_lower_bound
 bootstrap_focus: Freeze the exact problem statement, the local dossier, and the first honest lower-bound route for distinct subset sums.
-route_story: This problem now has a starter cockpit whose job is to keep the lower-bound route explicit without pretending we already have a deep theorem engine.
+route_story: This problem now has a starter workspace whose job is to keep the lower-bound route explicit without pretending we already have a deep theorem engine.
 frontier_label: distinct_subset_sum_lower_bound
 frontier_detail: Keep the problem anchored to the binary-growth lower-bound route and freeze the exact first reduction before widening claims.
 checkpoint_focus: Preserve provenance, the exact lower-bound route, and the open-problem boundary in every checkpoint.

package/packs/number-theory/problems/2/FRONTIER_NOTE.md

@@ -5,4 +5,4 @@ This is not a live open-problem frontier.
 The honest posture is:
 - preserve the disproval cleanly
 - keep the references synchronized
-- package the problem as a counterexample/method archive instead of a live cockpit
+- package the problem as a counterexample/method archive instead of a live workspace

package/packs/number-theory/problems/2/OPS_DETAILS.yaml

@@ -1,5 +1,5 @@
 packet_id: nt2_ops_details_v1
-summary: Archive cockpit packet for the disproved covering-systems problem.
+summary: Archive workspace packet for the disproved covering-systems problem.
 routes:
   - route_id: counterexample_archive
     title: Counterexample Archive

package/packs/number-theory/problems/2/ROUTE_HISTORY.md

@@ -1,5 +1,5 @@
 # Problem 2 Route History
 
 - Initial pack posture: dossier-first seed.
-- Current pack posture: archive cockpit around the counterexample/disproval record.
+- Current pack posture: archive workspace around the counterexample/disproval record.
 - Next maturity threshold: freeze the best archive packet rather than inventing open-frontier pressure.

package/packs/number-theory/problems/2/context.yaml

@@ -1,6 +1,6 @@
 problem_id: "2"
 family_role: covering_systems_counterexample_archive
-harness_profile: archive_cockpit
+harness_profile: archive_workspace
 default_active_route: counterexample_archive
 bootstrap_focus: Freeze the exact disproval record, the dossier provenance, and the counterexample-facing archive packet.
 route_story: This problem is not a live open frontier; the honest public job is to preserve the disproval and keep it usable as a method/counterexample exemplar.
@@ -20,6 +20,6 @@ question_ledger:
   open_questions:
     - Which exact disproval or counterexample references should be frozen first in the archive packet?
   active_route_notes:
-    - Treat this as an archive cockpit, not a live open-problem route.
+    - Treat this as an archive workspace, not a live open-problem route.
   route_breakthroughs: []
   problem_solved: []

package/src/commands/cluster.js

@@ -11,13 +11,13 @@ function printCluster(cluster) {
     console.log('  Strong sunflower sibling: 20');
     console.log('  Related analogues: 536, 856');
   } else if (cluster.name === 'number-theory') {
-    console.log('  Open starter cockpit: 1');
-    console.log('  Counterexample/archive cockpit: 2');
+    console.log('  Open starter workspace: 1');
+    console.log('  Counterexample/archive workspace: 2');
     console.log('  Additional dossier seeds: 3, 4, 5, 6, 7, 18, 542');
   } else if (cluster.name === 'graph-theory') {
-    console.log('  Decision archive cockpit: 19');
-    console.log('  Proof archive cockpit: 22');
-    console.log('  Lean proof archive cockpit: 1008');
+    console.log('  Decision archive workspace: 19');
+    console.log('  Proof archive workspace: 22');
+    console.log('  Lean proof archive workspace: 1008');
   }
 }
 

package/src/runtime/archive.js

@@ -23,7 +23,7 @@ export function getArchiveView(problemId) {
     solved: isSolved(problem),
     archiveMode: isSolved(problem) ? 'method_exemplar' : 'inactive',
     nextMove: isSolved(problem)
-      ? 'Extract reusable methods, references, and formalization hooks without treating this as an open-problem cockpit.'
+      ? 'Extract reusable methods, references, and formalization hooks without treating this as an open-problem workspace.'
       : 'This problem is not currently in solved archival mode.',
   };
 }

package/src/runtime/graph-theory.js

@@ -121,7 +121,7 @@ export function buildGraphTheoryStatusSnapshot(problem) {
     title: problem.title,
     cluster: problem.cluster,
     familyRole: context.family_role ?? 'graph_theory_pack',
-    harnessProfile: context.harness_profile ?? 'starter_cockpit',
+    harnessProfile: context.harness_profile ?? 'starter_workspace',
     activeRoute,
     routeBreakthrough,
     problemSolved,

package/src/runtime/number-theory.js

@@ -144,7 +144,7 @@ export function buildNumberTheoryStatusSnapshot(problem) {
     title: problem.title,
     cluster: problem.cluster,
     familyRole: context.family_role ?? 'number_theory_pack',
-    harnessProfile: context.harness_profile ?? 'starter_cockpit',
+    harnessProfile: context.harness_profile ?? 'starter_workspace',
     activeRoute,
     routeBreakthrough,
     problemSolved,