erdos-problems 0.2.4 → 0.2.6

package/README.md

@@ -1,8 +1,8 @@
 # erdos-problems
 
-> Research cockpit for Paul Erdos problems.
+> CLI and workspace for Paul Erdos problems.
 >
-> Seed a problem. Hand it to an agent. Keep the public truth, local route truth, and verification truth sharply separated.
+> Browse the atlas, scaffold a dossier, and keep public status, local route state, and verification records separate.
 
 [![npm version](https://img.shields.io/npm/v/erdos-problems?color=111111&label=npm)](https://www.npmjs.com/package/erdos-problems)
 [![npm downloads](https://img.shields.io/npm/dm/erdos-problems?color=111111&label=downloads)](https://www.npmjs.com/package/erdos-problems)
@@ -19,21 +19,23 @@ erdos-problems
 atlas -> dossier -> pack -> checkpoint -> archive
 ```
 
-`erdos-problems` is a CLI atlas and staged research harness for Paul Erdos problems.
-It is built for people who want more than a problem list and for agents that need a real starting surface on day one.
+`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.
 
 **Links:** [GitHub](https://github.com/SproutSeeds/erdos-problems) · [npm](https://www.npmjs.com/package/erdos-problems)
 
-## Why It Feels Different
+## Watch It Run
 
-Most open-problem repos stop at metadata.
+A short example from the first minute:
 
-`erdos-problems` goes further:
-- it ships a canonical atlas of Erdős problems
-- it creates agent-ready dossiers and workspace bundles
-- it keeps upstream public status separate from local research state
-- it adds pack-specific cockpits where deeper structure is honest
-- it carries an ORP-governed loop so claims, checkpoints, and runs stay disciplined
+![erdos-problems terminal demo](https://raw.githubusercontent.com/SproutSeeds/erdos-problems/main/assets/terminal-demo.gif)
+
+## What It Includes
+
+- a bundled snapshot of the Erdős problem atlas
+- 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
 
 ## Start In 60 Seconds
 
@@ -43,7 +45,7 @@ Install:
 npm install -g erdos-problems
 ```
 
-Bootstrap a flagship problem:
+Bootstrap a seeded problem:
 
 ```bash
 erdos bootstrap problem 857
@@ -52,7 +54,7 @@ erdos sunflower ready 857
 erdos workspace show --json
 ```
 
-Self-seed an unseeded problem into a fresh workspace:
+Seed a new problem into the current workspace:
 
 ```bash
 erdos seed problem 25 --cluster number-theory
@@ -60,42 +62,28 @@ erdos problem show 25
 erdos checkpoints sync
 ```
 
-Archive a solved problem cleanly:
+Archive a solved problem:
 
 ```bash
 erdos graph-theory status 1008
 erdos archive scaffold 1008 --json
 ```
 
-## What You Get
-
-| Layer | What it does |
-| --- | --- |
-| Atlas | canonical `problems/<id>/problem.yaml` records plus a bundled upstream snapshot |
-| Dossiers | local case files with statement, references, evidence, and formalization paths |
-| Workspaces | `.erdos/` state, checkpoints, ORP kit, pull bundles, runs, and archives |
-| Packs | deeper family-specific cockpits for problem clusters that deserve them |
-| Governance | ORP + `breakthroughs` + public-status review + structured run artifacts |
-
-## Coverage Right Now
+## Current Coverage
 
 | Surface | Coverage |
 | --- | --- |
 | Bundled upstream atlas | `1183` problems |
 | Native packaged dossiers | `18` |
 | Sunflower pack | `20`, `536`, `856`, `857` |
-| Number-theory cockpit | `1`, `2` |
-| Graph-theory archive cockpit | `19`, `22`, `1008` |
-| Deep theorem-facing pack problems | `20`, `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`
 
-## Flavor
-
-The package is meant to feel like a research cockpit, not a bag of files.
-
-Example:
+## Example Output
 
 ```bash
 $ erdos sunflower frontier 857
@@ -131,9 +119,9 @@ What this does:
 - syncs the bundled ORP kit into `.erdos/orp/`
 - scaffolds the dossier into `.erdos/scaffolds/<id>/`
 - pulls in pack-specific context where available
-- makes the workspace immediately usable by an agent
+- prepares the workspace for the next step
 
-### 2. Self-seed a new problem
+### 2. Seed a new problem
 
 ```bash
 erdos seed problem 25 --cluster number-theory
@@ -141,7 +129,7 @@ erdos seed problem 25 --cluster number-theory
 
 What this does:
 - pulls upstream public metadata into a workspace bundle
-- includes live site review and an agent-websearch brief by default
+- 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
 
@@ -165,7 +153,7 @@ erdos maintainer seed problem 25 --from-pull .erdos/pulls/25 --cluster number-th
 
 ### Sunflower Pack
 
-The first deep pack is the sunflower quartet:
+The sunflower pack currently covers this quartet:
 - `20`: strong / uniform sunflower core
 - `857`: weak / non-uniform sunflower core
 - `536`: natural-density LCM analogue
@@ -184,17 +172,17 @@ erdos sunflower atom 857 T10.G3.A2
 erdos sunflower compute run 857
 ```
 
-What makes it special:
-- mirrored public board packets
-- route / ticket / atom cockpit views
+What is included here:
+- public board packets
+- route / ticket / atom views
 - checkpoint and report packets
-- governed local-scout compute posture
+- governed local-scout compute posture where a packet exists
 
-### Number-Theory Starter Cockpit
+### Number-Theory Pack
 
-The first lighter non-sunflower pack is number theory:
-- `1`: open starter cockpit around a distinct-subset-sum route
-- `2`: counterexample/archive cockpit
+The number-theory pack currently includes:
+- `1`: open route-oriented starter pack around a distinct-subset-sum lane
+- `2`: counterexample / archive pack
 
 Useful commands:
 
@@ -207,12 +195,12 @@ erdos number-theory ticket 1 N1
 erdos number-theory atom 1 N1.G1.A1
 ```
 
-### Graph-Theory Archive Cockpit
+### Graph-Theory Archive Pack
 
-The first archive-first pack outside sunflower is graph theory:
-- `19`: decision archive cockpit
-- `22`: proof archive cockpit
-- `1008`: Lean-facing proof archive cockpit
+The graph-theory archive pack currently includes:
+- `19`: decision archive pack
+- `22`: proof archive pack
+- `1008`: Lean-facing proof archive pack
 
 Useful commands:
 
@@ -229,19 +217,19 @@ Design rule:
 - keep the archive usable as a method exemplar
 - preserve public status discipline instead of inflating pressure where none exists
 
-## Built For Agents
+## Using It With Agents
 
-If you are using Codex, Claude Code, or another agent harness, the package gives your agent:
+If you are using Codex, Claude Code, or another coding agent, the package provides:
 - canonical dossier files
 - upstream provenance
-- pack-aware context when available
+- pack-aware context where it exists
 - `.erdos/` workspace state
 - ORP templates and protocol guidance
 - checkpoint shelves
-- explicit next-honest-move framing
-- machine-readable JSON on the important public surfaces
+- explicit next-step framing
+- machine-readable JSON on the main public surfaces
 
-Especially useful commands for agent workflows:
+Useful commands for agent workflows:
 
 ```bash
 erdos problem artifacts 857 --json
@@ -259,14 +247,12 @@ erdos upstream drift 857 --json
 - `templates/VERIFICATION_RECORD.md`
 - `templates/FAILED_TOPIC.md`
 
-The package is opinionated about a clean truth ladder:
+The package keeps these layers separate:
 - upstream public truth
 - local canonical dossier truth
 - workspace bundle truth
 - pack-specific route / checkpoint / run truth
 
-That separation is one of the main product features.
-
 ## Command Gallery
 
 ```bash
@@ -314,12 +300,13 @@ erdos archive scaffold 1008 --json
 
 ## Launch Assets
 
-If you are about to push the public GitHub launch, start here:
+If you are preparing a public post, start here:
 - [docs/LAUNCH_KIT.md](docs/LAUNCH_KIT.md)
 - `assets/social-card.svg`
+- `assets/terminal-demo.gif`
 
 ## Notes
 
 - `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`
+- 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`.

package/assets/social-card.svg

@@ -4,12 +4,12 @@
   <rect x="78" y="78" width="1124" height="484" rx="18" fill="#181818" stroke="#C86A3E" stroke-width="2"/>
 
   <text x="104" y="168" fill="#F3EBDD" font-family="Menlo, Monaco, Consolas, monospace" font-size="28">erdos-problems</text>
-  <text x="104" y="228" fill="#F3EBDD" font-family="Georgia, 'Times New Roman', serif" font-size="68" font-weight="700">Research cockpit</text>
-  <text x="104" y="302" fill="#F3EBDD" font-family="Georgia, 'Times New Roman', serif" font-size="68" font-weight="700">for Paul Erdos problems</text>
+  <text x="104" y="228" fill="#F3EBDD" font-family="Georgia, 'Times New Roman', serif" font-size="64" font-weight="700">CLI and workspace</text>
+  <text x="104" y="300" fill="#F3EBDD" font-family="Georgia, 'Times New Roman', serif" font-size="64" font-weight="700">for Paul Erdos problems</text>
 
-  <text x="104" y="392" fill="#DDB892" font-family="Menlo, Monaco, Consolas, monospace" font-size="28">atlas  ->  dossier  ->  pack  ->  checkpoint  ->  archive</text>
-  <text x="104" y="446" fill="#DDB892" font-family="Menlo, Monaco, Consolas, monospace" font-size="24">seed a problem  |  hand it to an agent  |  keep the truth clean</text>
+  <text x="104" y="388" fill="#DDB892" font-family="Menlo, Monaco, Consolas, monospace" font-size="26">atlas  ->  dossier  ->  pack  ->  checkpoint  ->  archive</text>
+  <text x="104" y="440" fill="#DDB892" font-family="Menlo, Monaco, Consolas, monospace" font-size="22">seed a problem  |  inspect the record  |  keep sources separate</text>
 
-  <rect x="104" y="490" width="350" height="54" rx="12" fill="#C86A3E"/>
-  <text x="134" y="525" fill="#111111" font-family="Menlo, Monaco, Consolas, monospace" font-size="24" font-weight="700">npm install -g erdos-problems</text>
+  <rect x="104" y="476" width="520" height="64" rx="14" fill="#C86A3E"/>
+  <text x="136" y="518" fill="#111111" font-family="Menlo, Monaco, Consolas, monospace" font-size="24" font-weight="700">npm install -g erdos-problems</text>
 </svg>

package/docs/LAUNCH_KIT.md

@@ -3,24 +3,24 @@
 ## Positioning
 
 Short version:
-- `erdos-problems` is a research cockpit for Paul Erdos problems.
+- `erdos-problems` is a CLI and workspace for Paul Erdos problems.
 
 Medium version:
-- `erdos-problems` is a CLI atlas and agent-ready research harness for Paul Erdos problems. It goes beyond a problem list by shipping dossiers, pack-specific cockpits, ORP-governed workspaces, and structured pull/seed flows that let humans and agents start real research immediately.
+- `erdos-problems` is a CLI atlas with local dossiers, workspace scaffolding, and pack-specific views for Paul Erdos problems. It is designed to make the first step concrete without blurring public status, local route state, or verification records.
 
 Long version:
-- `erdos-problems` is built for serious open-problem work. It packages the public Erdős problem atlas, preserves canonical dossier truth, scaffolds agent-ready workspaces, and adds deeper family-specific cockpits where the problem structure is rich enough to justify them. The result is a clean research loop that can move from atlas -> dossier -> route -> checkpoint -> archive without blurring public status, local route pressure, or verification truth.
+- `erdos-problems` packages problem records, local dossiers, seeded workspaces, and pack-specific packets for the parts of the atlas that already have more structure in this repo. The aim is simple: make it easier to move from a problem listing to a working local workspace, while keeping public status, local route state, and verification records separate.
 
 ## Launch Copy
 
 ### One-liner
-- Research cockpit for Paul Erdos problems.
+- CLI and workspace for Paul Erdos problems.
 
 ### Short post
-- I just released `erdos-problems`: a CLI atlas and agent-ready research harness for Paul Erdos problems. It ships canonical dossiers, ORP-governed workspaces, self-seeding flows, and deeper cockpits for the sunflower family. Install with `npm install -g erdos-problems`. GitHub: https://github.com/SproutSeeds/erdos-problems
+- I just released `erdos-problems`, a CLI and workspace for Paul Erdos problems. It bundles problem records, local dossiers, self-seeding workspaces, and pack-specific views for the sunflower family and a few other problems. Install with `npm install -g erdos-problems`. GitHub: https://github.com/SproutSeeds/erdos-problems
 
 ### Longer post
-- I just released `erdos-problems`, a CLI atlas and staged research harness for Paul Erdos problems. The goal is not just to list problems, but to make them operational for real research. The package bundles upstream problem data, creates canonical dossiers, scaffolds ORP-governed workspaces, supports one-step self-seeding for new problems, and already includes deeper family-specific cockpits for sunflower, number theory, and graph-theory archive work. It is designed so a person or agent can install it at night and start honest, structured work immediately.
+- I just released `erdos-problems`, a CLI atlas and workspace for Paul Erdos problems. It bundles problem records, local dossiers, ORP-based workspaces, one-step self-seeding for new problems, and more developed pack views for the sunflower family. It is meant to make the move from a problem listing to a working local workspace simpler and more explicit, especially when you want to use coding agents without losing track of public status or verification boundaries.
 
 ## Demo Flow
 
@@ -47,40 +47,43 @@ erdos archive scaffold 1008 --json
 
 ## What To Emphasize
 
-- It is not just a metadata dump.
-- It is agent-ready out of the box.
-- It preserves truth hygiene.
-- It supports both open and solved problems.
-- It already has a deep sunflower cockpit.
+- It bundles problem records with local dossiers and workspaces.
+- It keeps public status and local research state separate.
+- It works well with coding agents, but it is still usable by hand.
+- It includes more developed sunflower views and lighter starter/archive views elsewhere.
 
 ## GitHub Presentation Notes
 
 Recommended repo tagline:
-- Research cockpit for Paul Erdos problems.
+- CLI and workspace for Paul Erdos problems.
 
 Recommended social preview:
 - editable source: `assets/social-card.svg`
 - upload-ready raster: `assets/social-card.png`
 
+Recommended demo assets:
+- animated terminal demo: `assets/terminal-demo.gif`
+- poster frame: `assets/terminal-demo-poster.png`
+
 Recommended pinned bullets:
 - atlas + dossiers
-- ORP-governed workspaces
+- workspaces + checkpoints
 - self-seeding from public sources
-- sunflower family cockpit
+- sunflower pack
 
 ## npm Presentation Notes
 
 Recommended lead screenshot substitute:
-- use the README's command-output sections
-- keep the top fast and cinematic
-- lead with install + immediate payoff
+- use the README command examples and the demo GIF
+- keep the top short and readable
+- lead with install + one concrete next step
 
 ## Suggested Release Checklist
 
 - publish npm package
 - set GitHub social preview image
 - add repo description/tagline
-- pin a short demo GIF or screenshot later if desired
+- pin the terminal demo GIF in the announcement thread or repo launch post
 - post the one-liner + short post copy
 
 ## Live links

package/docs/RESEARCH_LOOP.md

@@ -1,6 +1,6 @@
 # Research Loop
 
-`erdos-problems` now carries the staged research loop that was proven out in the sunflower lab and refined by the `.gpd` flow in `longevity-research`.
+`erdos-problems` includes a staged research loop for selecting problems, syncing workspace state, and recording checkpoints.
 
 ## Runtime layout
 
@@ -56,7 +56,7 @@ erdos checkpoints sync
 
 That flow writes the local dossier into `.erdos/seeded-problems/<id>/`, makes it visible to the atlas inside the current workspace, and immediately syncs the same state/checkpoint machinery used by packaged dossiers.
 
-The seeded dossier now also includes starter-loop artifacts:
+The seeded dossier also includes starter-loop artifacts:
 - `AGENT_START.md`
 - `ROUTES.md`
 - `CHECKPOINT_NOTES.md`
@@ -70,7 +70,7 @@ The ORP kit travels with the workspace too:
 - `templates/VERIFICATION_RECORD.md`
 - `templates/FAILED_TOPIC.md`
 
-For sunflower compute lanes, ORP now sits above `breakthroughs`:
+For sunflower compute lanes, ORP sits above `breakthroughs`:
 - `erdos sunflower status <id>` evaluates the packaged compute lane with `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
@@ -85,12 +85,12 @@ For sunflower compute lanes, ORP now sits above `breakthroughs`:
 - the CLI surfaces the selected rung, dispatch action, and the reason compute is admissible
 - this is compute governance and traceability, not an automatic paid or unbounded compute launch
 
-For number-theory starter-cockpit problems:
+For number-theory starter-pack problems:
 - `erdos number-theory status <id>` exposes the current route/frontier posture
 - `erdos number-theory frontier <id>` compresses the honest next move
 - `erdos number-theory routes <id>` exposes the small route table
 - `erdos number-theory tickets <id>` exposes the current ticket/archive packet
-- this is deliberately lighter than the sunflower pack and should stay honest about that
+- this layer is intentionally lighter than the sunflower pack
 
 For solved problems:
 - `erdos archive show <id>` exposes archival posture
@@ -98,7 +98,7 @@ For solved problems:
 
 ## Status ladder
 
-The public package uses the same ladder we converged on in the lab:
+The public package uses this ladder:
 - open problem
 - active route
 - route breakthrough

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "erdos-problems",
-  "version": "0.2.4",
-  "description": "Research cockpit and agent-ready CLI atlas for Paul Erdos problems.",
+  "version": "0.2.6",
+  "description": "CLI atlas and workspace tools for Paul Erdos problems.",
   "type": "module",
   "bin": {
     "erdos": "bin/erdos"

package/packs/sunflower/README.md

@@ -1,28 +1,28 @@
 # Sunflower Pack
 
-The first deep harness pack in `erdos-problems`.
+The sunflower pack is currently the most developed pack in `erdos-problems`.
 
-Sunflower core quartet:
+Sunflower quartet:
 - `20`
 - `536`
 - `856`
 - `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
+- `20`: more developed pack, strong / uniform core
+- `857`: more developed pack, weak / non-uniform core
+- `536`: bridge-oriented dossier, natural-density LCM analogue
+- `856`: bridge-oriented dossier, harmonic-density LCM analogue
 
-Deep route packets:
+More developed packets:
 - `20` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `FRONTIER_NOTE.md`, `ROUTE_HISTORY.md`, `CHECKPOINT_TEMPLATE.md`, `REPORT_TEMPLATE.md`, `OPS_DETAILS.yaml`
 - `857` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `FRONTIER_NOTE.md`, `ROUTE_HISTORY.md`, `CHECKPOINT_TEMPLATE.md`, `REPORT_TEMPLATE.md`, `OPS_DETAILS.yaml`
 
-Bridge packets:
+Bridge-oriented packets:
 - `536` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `FRONTIER_NOTE.md`, `ROUTE_HISTORY.md`, `CHECKPOINT_TEMPLATE.md`, `REPORT_TEMPLATE.md`, `OPS_DETAILS.yaml`
 - `856` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `FRONTIER_NOTE.md`, `ROUTE_HISTORY.md`, `CHECKPOINT_TEMPLATE.md`, `REPORT_TEMPLATE.md`, `OPS_DETAILS.yaml`
 
-Public cockpit commands:
+Public pack commands:
 - `erdos sunflower status <id>`
 - `erdos sunflower board <id>`
 - `erdos sunflower ready <id>`

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

@@ -2,7 +2,7 @@
 
 Role in family:
 - strong / uniform sunflower core
-- deep-harness sibling to the weak sunflower program on 857
+- more developed sibling to the weak sunflower work on 857
 
 Bootstrap focus:
 - start from the uniform k=3 lane

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

@@ -2,7 +2,7 @@
 
 Role in family:
 - natural-density LCM analogue inside the sunflower quartet
-- dossier-first bridge problem rather than a deep theorem harness today
+- bridge-oriented dossier rather than a more developed theorem pack today
 
 Bootstrap focus:
 - keep the combinatorial relation to 857 explicit

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

@@ -2,7 +2,7 @@
 
 Role in family:
 - harmonic-density LCM analogue inside the sunflower quartet
-- dossier-first bridge problem with direct implications for 857-style exponents
+- bridge-oriented dossier with direct implications for 857-style exponents
 
 Bootstrap focus:
 - keep the exponent-transfer story explicit

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

@@ -2,11 +2,11 @@
 
 Role in family:
 - weak / non-uniform sunflower core
-- current deep-harness flagship problem in the public atlas
+- currently one of the most developed public sunflower records in this repo
 
 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
+- keep literature, artifact, and compute packets aligned with the active frontier rather than generic sunflower notes
 
 Frontier framing:
 - preserve the active export/compression route as the live frontier