erdos-problems 0.2.2 → 0.2.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/README.md +208 -384
  2. package/assets/social-card.png +0 -0
  3. package/assets/social-card.svg +15 -0
  4. package/docs/LAUNCH_KIT.md +89 -0
  5. package/package.json +22 -5
package/README.md CHANGED
@@ -1,166 +1,169 @@
1
1
  # erdos-problems
2
2
 
3
- CLI atlas and staged research harness for Paul Erdos problems.
3
+ > Research cockpit for Paul Erdos problems.
4
+ >
5
+ > Seed a problem. Hand it to an agent. Keep the public truth, local route truth, and verification truth sharply separated.
6
+
7
+ [![npm version](https://img.shields.io/npm/v/erdos-problems?color=111111&label=npm)](https://www.npmjs.com/package/erdos-problems)
8
+ [![npm downloads](https://img.shields.io/npm/dm/erdos-problems?color=111111&label=downloads)](https://www.npmjs.com/package/erdos-problems)
9
+ [![GitHub stars](https://img.shields.io/github/stars/SproutSeeds/erdos-problems?style=flat&color=111111&label=stars)](https://github.com/SproutSeeds/erdos-problems/stargazers)
10
+ [![GitHub issues](https://img.shields.io/github/issues/SproutSeeds/erdos-problems?color=111111&label=issues)](https://github.com/SproutSeeds/erdos-problems/issues)
11
+ [![GitHub discussions](https://img.shields.io/github/discussions/SproutSeeds/erdos-problems?color=111111&label=discussions)](https://github.com/SproutSeeds/erdos-problems/discussions)
12
+ [![license](https://img.shields.io/npm/l/erdos-problems?color=111111&label=license)](./LICENSE)
13
+ [![node](https://img.shields.io/node/v/erdos-problems?color=111111&label=node)](https://www.npmjs.com/package/erdos-problems)
14
+
15
+ ![erdos-problems social card](https://raw.githubusercontent.com/SproutSeeds/erdos-problems/main/assets/social-card.png)
16
+
17
+ ```text
18
+ erdos-problems
19
+ atlas -> dossier -> pack -> checkpoint -> archive
20
+ ```
21
+
22
+ `erdos-problems` is a CLI atlas and staged research harness for Paul Erdos problems.
23
+ It is built for people who want more than a problem list and for agents that need a real starting surface on day one.
24
+
25
+ **Links:** [GitHub](https://github.com/SproutSeeds/erdos-problems) · [npm](https://www.npmjs.com/package/erdos-problems)
26
+
27
+ ## Why It Feels Different
4
28
 
5
- ## Install
29
+ Most open-problem repos stop at metadata.
30
+
31
+ `erdos-problems` goes further:
32
+ - it ships a canonical atlas of Erdős problems
33
+ - it creates agent-ready dossiers and workspace bundles
34
+ - it keeps upstream public status separate from local research state
35
+ - it adds pack-specific cockpits where deeper structure is honest
36
+ - it carries an ORP-governed loop so claims, checkpoints, and runs stay disciplined
37
+
38
+ ## Start In 60 Seconds
39
+
40
+ Install:
6
41
 
7
42
  ```bash
8
43
  npm install -g erdos-problems
9
44
  ```
10
45
 
11
- Official package:
12
- - `erdos-problems`
46
+ Bootstrap a flagship problem:
13
47
 
14
- Official binary:
15
- - `erdos`
48
+ ```bash
49
+ erdos bootstrap problem 857
50
+ erdos sunflower frontier 857
51
+ erdos sunflower ready 857
52
+ erdos workspace show --json
53
+ ```
16
54
 
17
- ## Current shape
55
+ Self-seed an unseeded problem into a fresh workspace:
18
56
 
19
- - atlas layer with canonical local `problems/<id>/problem.yaml` records
20
- - bundled upstream snapshot from `teorth/erdosproblems`
21
- - bundled ORP kit with protocol and templates for claim hygiene
22
- - workspace `.erdos/` state for active-problem selection, upstream refreshes, scaffolds, and pull bundles
23
- - sunflower cluster as the first deep harness pack
24
- - quartet-aware sunflower context for `20`, `536`, `856`, and `857`
25
- - number-theory starter cockpit as the first lighter non-sunflower pack
26
- - graph-theory archive cockpit as the first archive/decision pack outside sunflower
27
- - packaged atomic/bridge board packets for the full sunflower quartet
28
- - packaged compute-lane metadata for deep sunflower problems, surfaced directly in the CLI
29
- - seeded atlas now includes open and solved problems beyond sunflower
30
- - unseeded problems can still be pulled into a workspace from the bundled upstream snapshot
57
+ ```bash
58
+ erdos seed problem 25 --cluster number-theory
59
+ erdos problem show 25
60
+ erdos checkpoints sync
61
+ ```
62
+
63
+ Archive a solved problem cleanly:
64
+
65
+ ```bash
66
+ erdos graph-theory status 1008
67
+ erdos archive scaffold 1008 --json
68
+ ```
69
+
70
+ ## What You Get
71
+
72
+ | Layer | What it does |
73
+ | --- | --- |
74
+ | Atlas | canonical `problems/<id>/problem.yaml` records plus a bundled upstream snapshot |
75
+ | Dossiers | local case files with statement, references, evidence, and formalization paths |
76
+ | Workspaces | `.erdos/` state, checkpoints, ORP kit, pull bundles, runs, and archives |
77
+ | Packs | deeper family-specific cockpits for problem clusters that deserve them |
78
+ | Governance | ORP + `breakthroughs` + public-status review + structured run artifacts |
79
+
80
+ ## Coverage Right Now
31
81
 
32
- Seeded problems:
82
+ | Surface | Coverage |
83
+ | --- | --- |
84
+ | Bundled upstream atlas | `1183` problems |
85
+ | Native packaged dossiers | `18` |
86
+ | Sunflower pack | `20`, `536`, `856`, `857` |
87
+ | Number-theory cockpit | `1`, `2` |
88
+ | Graph-theory archive cockpit | `19`, `22`, `1008` |
89
+ | Deep theorem-facing pack problems | `20`, `857` |
90
+
91
+ Seeded problems today:
33
92
  - `1`, `2`, `3`, `4`, `5`, `6`, `7`, `18`, `19`, `20`, `21`, `22`, `89`, `536`, `542`, `856`, `857`, `1008`
34
93
 
35
- Native dossier count:
36
- - `18`
94
+ ## Flavor
37
95
 
38
- Pack coverage:
39
- - sunflower pack: `4`
40
- - number-theory starter cockpit: `2`
41
- - graph-theory archive cockpit: `3`
96
+ The package is meant to feel like a research cockpit, not a bag of files.
42
97
 
43
- ## First-run flow
98
+ Example:
99
+
100
+ ```bash
101
+ $ erdos sunflower frontier 857
102
+ Erdos Problem #857 sunflower frontier
103
+ Active route: anchored_selector_linearization
104
+ Active ticket: T10
105
+ First ready atom: T10.G3.A2
106
+ Checkpoint focus: keep the board packet honest around T10 while preserving the open-problem / active-route / route-breakthrough ladder.
107
+ ```
108
+
109
+ ```bash
110
+ $ erdos graph-theory status 1008
111
+ Erdos Problem #1008 graph-theory harness
112
+ Family role: c4_free_lean_archive
113
+ Harness profile: lean_archive_cockpit
114
+ Archive mode: method_exemplar
115
+ Problem solved: yes
116
+ First ready atom: G1008.G1.A1 — Freeze the primary Lean-facing archive hook for the `C_4`-free density result
117
+ ```
118
+
119
+ ## Core Flows
120
+
121
+ ### 1. Bootstrap a seeded problem
44
122
 
45
123
  ```bash
46
- erdos problem list --cluster sunflower
47
124
  erdos bootstrap problem 857
48
125
  erdos problem artifacts 857 --json
49
- erdos sunflower status 857
50
- erdos sunflower board 857
51
- erdos sunflower frontier 857
52
- erdos sunflower routes 857
53
- erdos sunflower tickets 857
54
- erdos dossier show 857
55
- erdos number-theory status 1
56
- erdos graph-theory status 1008
126
+ erdos checkpoints sync
57
127
  ```
58
128
 
59
- For an unseeded problem, the one-step self-seeding flow is now:
129
+ What this does:
130
+ - sets the active workspace problem
131
+ - syncs the bundled ORP kit into `.erdos/orp/`
132
+ - scaffolds the dossier into `.erdos/scaffolds/<id>/`
133
+ - pulls in pack-specific context where available
134
+ - makes the workspace immediately usable by an agent
135
+
136
+ ### 2. Self-seed a new problem
60
137
 
61
138
  ```bash
62
139
  erdos seed problem 25 --cluster number-theory
63
- erdos problem show 25
64
- erdos workspace show
65
140
  ```
66
141
 
67
- What `bootstrap` does:
68
- - sets the active workspace problem
69
- - syncs the bundled ORP workspace kit into `.erdos/orp/`
70
- - scaffolds the canonical dossier files into `.erdos/scaffolds/<id>/`
71
- - includes the upstream record when a bundled or workspace snapshot is available
72
- - copies pack-specific context and compute packets when the problem has them
73
- - gives an agent a ready-to-read local artifact bundle immediately after install
74
-
75
- What `seed` does:
76
- - creates a pull bundle for any problem in the upstream snapshot
77
- - defaults to a live site snapshot plus a public-search review bundle
78
- - treats a problem as seed-admissible only when the public site says `open`, unless you intentionally pass `--allow-non-open`
79
- - promotes that bundle into `.erdos/seeded-problems/<id>/`
80
- - auto-selects the problem in the workspace
81
- - syncs the bundled ORP workspace kit into `.erdos/orp/`
82
- - syncs the staged research loop state and checkpoint shelf
83
- - makes the new dossier visible to the atlas commands immediately inside that workspace
84
- - writes richer starter artifacts:
85
- - `AGENT_START.md`
86
- - `ROUTES.md`
87
- - `CHECKPOINT_NOTES.md`
88
- - `PUBLIC_STATUS_REVIEW.md`
89
- - `AGENT_WEBSEARCH_BRIEF.md`
90
-
91
- The seeded workspace also now has a clearer runtime shape:
92
- - `.erdos/runs/`
93
- - `.erdos/archives/`
94
- - `.erdos/checkpoints/`
95
- - `.erdos/orp/`
96
-
97
- ## Pull lanes
98
-
99
- For any problem number in the upstream snapshot, you can create a workspace bundle even if the problem is not yet seeded locally:
142
+ What this does:
143
+ - pulls upstream public metadata into a workspace bundle
144
+ - includes live site review and an agent-websearch brief by default
145
+ - seeds a local dossier into `.erdos/seeded-problems/<id>/`
146
+ - syncs state, checkpoints, and ORP automatically
147
+
148
+ ### 3. Pull artifacts without seeding
100
149
 
101
150
  ```bash
102
151
  erdos pull problem 857
103
- erdos pull artifacts 857
104
- erdos pull literature 857
105
- erdos pull literature 857 --json
106
- erdos pull literature 857 --include-crossref --include-openalex
107
- erdos pull problem 999 --include-site --include-public-search
108
- erdos pull problem 999 --refresh-upstream
152
+ erdos pull literature 857 --include-crossref --include-openalex --json
109
153
  ```
110
154
 
111
- What the pull lanes do:
112
- - `erdos pull problem <id>` creates `.erdos/pulls/<id>/` with:
113
- - a root pull manifest
114
- - `artifacts/`
115
- - `literature/`
116
- - `erdos pull artifacts <id>` creates only the artifact lane
117
- - `erdos pull literature <id>` creates only the literature lane
118
- - when a problem is locally seeded, the artifact lane includes the canonical dossier, pack context, and compute packets
119
- - when `--include-site` is used, the literature lane can include a live site snapshot and plain-text extract
120
- - when `--include-public-search` is used, the literature lane also includes:
121
- - `PUBLIC_STATUS_REVIEW.md`
122
- - `PUBLIC_STATUS_REVIEW.json`
123
- - `AGENT_WEBSEARCH_BRIEF.md`
124
- - when `--include-crossref` is used, the literature lane also includes:
125
- - `CROSSREF_RESULTS.json`
126
- - `CROSSREF_RESULTS.md`
127
- - when `--include-openalex` is used, the literature lane also includes:
128
- - `OPENALEX_RESULTS.json`
129
- - `OPENALEX_RESULTS.md`
130
- - when `--json` is used, the pull command emits an agent-friendly machine summary instead of prose
131
-
132
- ## Maintainer seeding
133
-
134
- To turn a pulled bundle into a new canonical dossier in the repo:
155
+ Use this when you want a research bundle first and a canonical dossier later.
156
+
157
+ ### 4. Promote a pulled bundle into a canonical dossier
135
158
 
136
159
  ```bash
137
- erdos maintainer seed problem 25 \
138
- --from-pull .erdos/pulls/25 \
139
- --cluster number-theory
140
- erdos maintainer review problem 25 \
141
- --from-pull .erdos/pulls/25
160
+ erdos maintainer review problem 25 --from-pull .erdos/pulls/25
161
+ erdos maintainer seed problem 25 --from-pull .erdos/pulls/25 --cluster number-theory
142
162
  ```
143
163
 
144
- What maintainer seeding does:
145
- - reads the pull bundle provenance
146
- - generates a canonical `problems/<id>/` dossier
147
- - writes:
148
- - `problem.yaml`
149
- - `STATEMENT.md`
150
- - `REFERENCES.md`
151
- - `EVIDENCE.md`
152
- - `FORMALIZATION.md`
153
- - starter loop files:
154
- - `AGENT_START.md`
155
- - `ROUTES.md`
156
- - `CHECKPOINT_NOTES.md`
157
- - public-truth starter files:
158
- - `PUBLIC_STATUS_REVIEW.md`
159
- - `AGENT_WEBSEARCH_BRIEF.md`
160
- - preserves upstream/site provenance in the local record
161
- - `erdos maintainer review problem <id>` also creates a review checklist before promotion
162
-
163
- ## Sunflower pack
164
+ ## Packs
165
+
166
+ ### Sunflower Pack
164
167
 
165
168
  The first deep pack is the sunflower quartet:
166
169
  - `20`: strong / uniform sunflower core
@@ -168,334 +171,155 @@ The first deep pack is the sunflower quartet:
168
171
  - `536`: natural-density LCM analogue
169
172
  - `856`: harmonic-density LCM analogue
170
173
 
171
- Sunflower problems now ship pack packets:
172
- - `20`: `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`
173
- - `857`: `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`
174
- - `536`: `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`
175
- - `856`: `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`
176
-
177
- Useful sunflower commands:
174
+ Useful commands:
178
175
 
179
176
  ```bash
180
- erdos cluster show sunflower
181
- erdos sunflower status 20
182
- erdos sunflower status 536
183
- erdos sunflower board 536
184
- erdos sunflower ready 857
185
- erdos sunflower ladder 20
177
+ erdos sunflower status 857
178
+ erdos sunflower board 857
186
179
  erdos sunflower frontier 857
187
180
  erdos sunflower routes 857
188
181
  erdos sunflower tickets 857
189
182
  erdos sunflower route 857 anchored_selector_linearization
190
- erdos sunflower ticket 20 T6
191
183
  erdos sunflower atom 857 T10.G3.A2
192
184
  erdos sunflower compute run 857
193
- erdos sunflower board 857
194
- erdos sunflower status 857 --json
195
185
  ```
196
186
 
197
- `erdos sunflower status` surfaces:
198
- - family role
199
- - harness profile
200
- - active route
201
- - route breakthrough state
202
- - problem-solved distinction
203
- - atomic board posture, active ticket, ready-atom count, and first ready atom when a board packet exists
204
- - compute posture when a packet exists
205
-
206
- `erdos sunflower board` surfaces:
207
- - mirrored lab atomic boards for `20` and `857`
208
- - lighter dossier-bridge boards for `536` and `856`
209
- - route status
210
- - ticket board summary
211
- - first-principles ladder
212
- - ready queue
213
-
214
- `erdos sunflower ready` surfaces:
215
- - the current dependency-satisfied ready queue for the active sunflower board
216
-
217
- `erdos sunflower ladder` surfaces:
218
- - the first-principles ladder for the active sunflower board
219
-
220
- `erdos sunflower routes` surfaces:
221
- - the strategic route table for the active sunflower board
222
- - loose and strict progress for every publicized route
223
- - which route is the currently active frontier
224
-
225
- `erdos sunflower tickets` surfaces:
226
- - the operational ticket table for the active sunflower board
227
- - the active ticket, leaf theorem, and gate/atom counts
228
- - which tickets are closed versus still honest live pressure
229
-
230
- `erdos sunflower frontier` surfaces:
231
- - the compressed cockpit view:
232
- - active route
233
- - active ticket
234
- - first ready atom
235
- - checkpoint focus
236
- - compute posture
237
-
238
- `erdos sunflower route|ticket|atom` surfaces:
239
- - the deeper public drill-down packet for a specific route, ticket, or atom
240
- - live summary, blocker, next move, and source paths when available
241
-
242
- `erdos sunflower compute run` surfaces:
243
- - a governed local-scout run bundle only when the packaged compute posture admits a local scout
244
- - writes reproducible run artifacts into `.erdos/runs/<run-id>/`
245
- - records governance and ORP-facing packet context
246
- - does not silently escalate into paid or unbounded compute
247
-
248
- ## Number-theory starter cockpit
249
-
250
- The first non-sunflower pack is now a light but real cockpit for two number-theory problems:
251
- - `1`: open starter cockpit around a distinct-subset-sum lower-bound route
252
- - `2`: archive cockpit around a disproved / counterexample-facing record
253
-
254
- Useful number-theory commands:
187
+ What makes it special:
188
+ - mirrored public board packets
189
+ - route / ticket / atom cockpit views
190
+ - checkpoint and report packets
191
+ - governed local-scout compute posture
192
+
193
+ ### Number-Theory Starter Cockpit
194
+
195
+ The first lighter non-sunflower pack is number theory:
196
+ - `1`: open starter cockpit around a distinct-subset-sum route
197
+ - `2`: counterexample/archive cockpit
198
+
199
+ Useful commands:
255
200
 
256
201
  ```bash
257
202
  erdos number-theory status 1
258
203
  erdos number-theory frontier 1
259
204
  erdos number-theory routes 1
260
- erdos number-theory tickets 1
261
205
  erdos number-theory route 1 distinct_subset_sum_lower_bound
262
206
  erdos number-theory ticket 1 N1
263
207
  erdos number-theory atom 1 N1.G1.A1
264
- erdos number-theory status 2 --json
265
208
  ```
266
209
 
267
- The number-theory pack is intentionally lighter than sunflower:
268
- - no mirrored theorem board yet
269
- - explicit route/frontier/ticket packet layer
270
- - honest archive posture for disproved problems
271
-
272
- ## Graph-theory archive cockpit
210
+ ### Graph-Theory Archive Cockpit
273
211
 
274
- The next family pack is a deliberately honest archive/decision cockpit for seeded graph-theory problems:
212
+ The first archive-first pack outside sunflower is graph theory:
275
213
  - `19`: decision archive cockpit
276
214
  - `22`: proof archive cockpit
277
215
  - `1008`: Lean-facing proof archive cockpit
278
216
 
279
- Useful graph-theory commands:
217
+ Useful commands:
280
218
 
281
219
  ```bash
282
220
  erdos graph-theory status 19
283
221
  erdos graph-theory frontier 22
284
222
  erdos graph-theory routes 1008
285
- erdos graph-theory tickets 1008
286
- erdos graph-theory status 1008 --json
223
+ erdos graph-theory tickets 19
224
+ erdos archive scaffold 1008 --json
287
225
  ```
288
226
 
289
- The graph-theory pack is intentionally archive-first:
290
- - no fake open frontier for solved or decided problems
291
- - route/ticket packets exist to preserve archive discipline, not to cosplay theorem pressure
292
- - the public job is to keep solved/decided records reusable as method exemplars and clean references
227
+ Design rule:
228
+ - no fake live frontier for solved or decided problems
229
+ - keep the archive usable as a method exemplar
230
+ - preserve public status discipline instead of inflating pressure where none exists
231
+
232
+ ## Built For Agents
293
233
 
294
- ## Archive mode
234
+ If you are using Codex, Claude Code, or another agent harness, the package gives your agent:
235
+ - canonical dossier files
236
+ - upstream provenance
237
+ - pack-aware context when available
238
+ - `.erdos/` workspace state
239
+ - ORP templates and protocol guidance
240
+ - checkpoint shelves
241
+ - explicit next-honest-move framing
242
+ - machine-readable JSON on the important public surfaces
295
243
 
296
- Solved problems can now be treated as method exemplars instead of dead entries.
244
+ Especially useful commands for agent workflows:
297
245
 
298
246
  ```bash
299
- erdos problem show 1008
300
- erdos archive show 1008
301
- erdos archive scaffold 1008
302
- erdos number-theory status 1
303
- erdos number-theory frontier 1
304
- erdos number-theory routes 1
305
- erdos number-theory tickets 1
247
+ erdos problem artifacts 857 --json
248
+ erdos workspace show --json
249
+ erdos pull literature 857 --include-crossref --include-openalex --json
250
+ erdos upstream drift 857 --json
306
251
  ```
307
252
 
308
- Archive scaffolds land in:
309
- - `.erdos/archives/<id>/`
253
+ ## ORP And Truth Hygiene
310
254
 
311
- and include:
312
- - `ARCHIVE.json`
313
- - `ARCHIVE_SUMMARY.md`
314
- - `METHOD_PACKET.md`
315
-
316
- ## ORP
317
-
318
- `erdos-problems` now ships a bundled Open Research Protocol kit:
255
+ `erdos-problems` ships a bundled Open Research Protocol kit:
319
256
  - `PROTOCOL.md`
320
257
  - `AGENT_INTEGRATION.md`
321
258
  - `templates/CLAIM.md`
322
259
  - `templates/VERIFICATION_RECORD.md`
323
260
  - `templates/FAILED_TOPIC.md`
324
261
 
325
- Workspace copy:
326
- - `.erdos/orp/PROTOCOL.md`
327
- - `.erdos/orp/AGENT_INTEGRATION.md`
328
- - `.erdos/orp/templates/`
262
+ The package is opinionated about a clean truth ladder:
263
+ - upstream public truth
264
+ - local canonical dossier truth
265
+ - workspace bundle truth
266
+ - pack-specific route / checkpoint / run truth
329
267
 
330
- Useful ORP commands:
268
+ That separation is one of the main product features.
331
269
 
332
- ```bash
333
- erdos orp show
334
- erdos orp sync
335
- ```
336
-
337
- ## CLI
270
+ ## Command Gallery
338
271
 
339
272
  ```bash
340
- erdos problem list
341
273
  erdos problem list --cluster sunflower
342
- erdos problem list --repo-status historical
343
- erdos problem list --harness-depth deep
344
- erdos problem list --site-status solved
345
- erdos problem use 857
346
- erdos problem show
347
- erdos problem artifacts 857
274
+ erdos problem show 857
348
275
  erdos problem artifacts 857 --json
349
- erdos cluster list
350
- erdos cluster show sunflower
351
- erdos cluster show number-theory
276
+
277
+ erdos cluster list --json
352
278
  erdos cluster show graph-theory
353
- erdos workspace show
279
+
354
280
  erdos workspace show --json
355
- erdos orp show
356
- erdos orp sync
357
- erdos sunflower status 857
358
- erdos sunflower board 857
359
- erdos sunflower ready 857
360
- erdos sunflower ladder 857
281
+ erdos checkpoints sync
282
+ erdos preflight
283
+
361
284
  erdos sunflower frontier 857
362
- erdos sunflower routes 857
363
- erdos sunflower tickets 857
364
- erdos sunflower route 857 anchored_selector_linearization
365
- erdos sunflower ticket 857 T10
366
- erdos sunflower atom 857 T10.G3.A2
285
+ erdos sunflower ready 857
367
286
  erdos sunflower compute run 857
368
- erdos number-theory status 1
369
- erdos number-theory frontier 1
370
- erdos number-theory routes 1
371
- erdos number-theory tickets 1
287
+
372
288
  erdos number-theory route 1 distinct_subset_sum_lower_bound
373
- erdos number-theory ticket 1 N1
374
- erdos number-theory atom 1 N1.G1.A1
375
289
  erdos graph-theory status 1008
376
- erdos graph-theory frontier 22
377
- erdos graph-theory routes 1008
378
- erdos graph-theory tickets 19
379
- erdos sunflower status --json
380
- erdos dossier show
381
- erdos upstream show
382
- erdos upstream sync
383
- erdos upstream diff
384
- erdos upstream drift
385
- erdos upstream drift 857 --json
386
- erdos scaffold problem 857
387
- erdos bootstrap problem 857
388
- erdos bootstrap problem 857 --sync-upstream
389
- erdos seed problem 25 --cluster number-theory
290
+
390
291
  erdos pull problem 857
391
- erdos pull artifacts 857
392
- erdos pull literature 857
393
- erdos pull literature 857 --json
394
- erdos pull literature 857 --include-crossref --include-openalex
292
+ erdos pull literature 857 --include-crossref --include-openalex --json
293
+
294
+ erdos seed problem 25 --cluster number-theory
395
295
  erdos maintainer review problem 25 --from-pull .erdos/pulls/25
396
- erdos maintainer seed problem 25 --from-pull .erdos/pulls/25 --cluster number-theory
397
- erdos archive show 1008
398
- erdos archive scaffold 1008
296
+ erdos archive scaffold 1008 --json
399
297
  ```
400
298
 
401
- ## Canonical sources
299
+ ## Canonical Sources
402
300
 
403
- - local atlas truth: `problems/<id>/problem.yaml`
301
+ - local dossier truth: `problems/<id>/problem.yaml`
404
302
  - bundled upstream snapshot: `data/upstream/erdosproblems/`
405
303
  - workspace upstream snapshot: `.erdos/upstream/erdosproblems/`
406
- - live upstream repo: `https://github.com/teorth/erdosproblems`
407
- - live public site: `https://www.erdosproblems.com/`
408
-
409
- ## Agent-facing artifact model
410
-
411
- For each seeded problem, the canonical local dossier lives in `problems/<id>/`:
412
- - `problem.yaml`
413
- - `STATEMENT.md`
414
- - `REFERENCES.md`
415
- - `EVIDENCE.md`
416
- - `FORMALIZATION.md`
417
-
418
- Many seeded dossiers now also carry starter-loop artifacts:
419
- - `AGENT_START.md`
420
- - `ROUTES.md`
421
- - `CHECKPOINT_NOTES.md`
422
- - `PUBLIC_STATUS_REVIEW.md`
423
- - `AGENT_WEBSEARCH_BRIEF.md`
424
-
425
- The CLI can surface these directly:
426
- - `erdos problem artifacts <id>` shows the canonical inventory
427
- - `erdos problem artifacts <id> --json` emits machine-readable inventory
428
- - `erdos scaffold problem <id>` copies the seeded dossier into the active workspace
429
- - `erdos bootstrap problem <id>` selects the problem and creates the scaffold in one step
430
- - `erdos seed problem <id>` self-seeds an unseeded problem into `.erdos/seeded-problems/` and syncs the loop
431
- - `erdos pull problem <id>` creates a workspace bundle for any problem in the upstream snapshot
432
- - `erdos maintainer seed problem <id>` promotes a pull bundle into a canonical local dossier
433
-
434
- For sunflower problems, the CLI also surfaces pack-specific artifacts:
435
- - pack README context
436
- - per-problem context files under `packs/sunflower/problems/<id>/`
437
- - route packets, checkpoint/report packets, and board packets for the full sunflower quartet
438
- - compute packets under `packs/sunflower/compute/<id>/` when available
439
- - compute-governance evaluation under `breakthroughs`, surfaced through `erdos sunflower status`
440
-
441
- For number-theory starter-cockpit problems, the CLI now also surfaces:
442
- - pack README context
443
- - per-problem context files under `packs/number-theory/problems/<id>/`
444
- - route packets, frontier notes, route histories, checkpoint/report templates, and ops-detail packets
445
- - route/ticket/atom drill-down packets through `erdos number-theory route|ticket|atom`
446
- - archive posture for disproved problems through `erdos number-theory status`
447
-
448
- For graph-theory archive-cockpit problems, the CLI now also surfaces:
449
- - pack README context
450
- - per-problem context files under `packs/graph-theory/problems/<id>/`
451
- - route packets, frontier notes, route histories, checkpoint/report templates, and ops-detail packets
452
- - archive and decision posture through `erdos graph-theory status|frontier|routes|tickets`
453
-
454
- ## Notes
455
-
456
- - `erdos-problems` is the canonical npm package name.
457
- - The compact unscoped alias `erdosproblems` is not publishable because npm rejects it as too similar to `erdos-problems`.
304
+ - live upstream repo: <https://github.com/teorth/erdosproblems>
305
+ - live public site: <https://www.erdosproblems.com/>
458
306
 
459
307
  ## Docs
460
308
 
461
309
  - `docs/ERDOS_PROBLEMS_REPO_SPEC.md`
462
310
  - `docs/ERDOS_PROBLEMS_PROBLEM_SCHEMA.md`
463
311
  - `docs/ERDOS_SUNFLOWER_CLUSTER_SEED_PLAN.md`
312
+ - `docs/RESEARCH_LOOP.md`
313
+ - `docs/LAUNCH_KIT.md`
464
314
 
465
- ## Research loop
315
+ ## Launch Assets
466
316
 
467
- `erdos-problems` now carries the staged loop we defined in the sunflower lab and the `.gpd`-style harness work:
317
+ If you are about to push the public GitHub launch, start here:
318
+ - [docs/LAUNCH_KIT.md](docs/LAUNCH_KIT.md)
319
+ - `assets/social-card.svg`
468
320
 
469
- ```bash
470
- erdos problem use 857
471
- erdos state sync
472
- erdos preflight
473
- erdos continuation use route
474
- erdos checkpoints sync
475
- erdos workspace show
476
- ```
321
+ ## Notes
477
322
 
478
- This runtime writes:
479
- - `.erdos/config.json`
480
- - `.erdos/state.json`
481
- - `.erdos/STATE.md`
482
- - `.erdos/QUESTION-LEDGER.md`
483
- - `.erdos/checkpoints/CHECKPOINTS.md`
484
- - `.erdos/checkpoints/CHECKPOINTS.json`
485
- - `.erdos/orp/PROTOCOL.md`
486
- - `.erdos/orp/AGENT_INTEGRATION.md`
487
- - `.erdos/orp/templates/`
488
- - `.erdos/registry/preflight/`
489
-
490
- The public package uses the same status ladder we settled on in the lab:
491
- - open problem
492
- - active route
493
- - route breakthrough
494
- - problem solved
495
-
496
- That means a fresh install now supports two clean research starts:
497
- - `erdos bootstrap problem <seeded-id>` for native packaged dossiers
498
- - `erdos seed problem <unseeded-id>` for workspace-local self-seeding with the same loop
499
-
500
- See also:
501
- - `docs/RESEARCH_LOOP.md`
323
+ - `erdos-problems` is the canonical npm package name.
324
+ - the package is already live on npm
325
+ - the compact unscoped alias `erdosproblems` is not publishable because npm rejects it as too similar to `erdos-problems`
package/assets/social-card.png ADDED
Binary file
package/assets/social-card.svg ADDED
@@ -0,0 +1,15 @@
1
+ <svg width="1280" height="640" viewBox="0 0 1280 640" fill="none" xmlns="http://www.w3.org/2000/svg">
2
+ <rect width="1280" height="640" fill="#F3EBDD"/>
3
+ <rect x="40" y="40" width="1200" height="560" rx="28" fill="#111111"/>
4
+ <rect x="78" y="78" width="1124" height="484" rx="18" fill="#181818" stroke="#C86A3E" stroke-width="2"/>
5
+
6
+ <text x="104" y="168" fill="#F3EBDD" font-family="Menlo, Monaco, Consolas, monospace" font-size="28">erdos-problems</text>
7
+ <text x="104" y="228" fill="#F3EBDD" font-family="Georgia, 'Times New Roman', serif" font-size="68" font-weight="700">Research cockpit</text>
8
+ <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>
9
+
10
+ <text x="104" y="392" fill="#DDB892" font-family="Menlo, Monaco, Consolas, monospace" font-size="28">atlas -> dossier -> pack -> checkpoint -> archive</text>
11
+ <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>
12
+
13
+ <rect x="104" y="490" width="350" height="54" rx="12" fill="#C86A3E"/>
14
+ <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>
15
+ </svg>
package/docs/LAUNCH_KIT.md ADDED
@@ -0,0 +1,89 @@
1
+ # Launch Kit
2
+
3
+ ## Positioning
4
+
5
+ Short version:
6
+ - `erdos-problems` is a research cockpit for Paul Erdos problems.
7
+
8
+ Medium version:
9
+ - `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.
10
+
11
+ Long version:
12
+ - `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.
13
+
14
+ ## Launch Copy
15
+
16
+ ### One-liner
17
+ - Research cockpit for Paul Erdos problems.
18
+
19
+ ### Short post
20
+ - 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
21
+
22
+ ### Longer post
23
+ - 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.
24
+
25
+ ## Demo Flow
26
+
27
+ ```bash
28
+ npm install -g erdos-problems
29
+ erdos bootstrap problem 857
30
+ erdos sunflower frontier 857
31
+ erdos problem artifacts 857 --json
32
+ ```
33
+
34
+ Backup demo flow:
35
+
36
+ ```bash
37
+ erdos seed problem 25 --cluster number-theory
38
+ erdos workspace show --json
39
+ ```
40
+
41
+ Archive demo flow:
42
+
43
+ ```bash
44
+ erdos graph-theory status 1008
45
+ erdos archive scaffold 1008 --json
46
+ ```
47
+
48
+ ## What To Emphasize
49
+
50
+ - It is not just a metadata dump.
51
+ - It is agent-ready out of the box.
52
+ - It preserves truth hygiene.
53
+ - It supports both open and solved problems.
54
+ - It already has a deep sunflower cockpit.
55
+
56
+ ## GitHub Presentation Notes
57
+
58
+ Recommended repo tagline:
59
+ - Research cockpit for Paul Erdos problems.
60
+
61
+ Recommended social preview:
62
+ - editable source: `assets/social-card.svg`
63
+ - upload-ready raster: `assets/social-card.png`
64
+
65
+ Recommended pinned bullets:
66
+ - atlas + dossiers
67
+ - ORP-governed workspaces
68
+ - self-seeding from public sources
69
+ - sunflower family cockpit
70
+
71
+ ## npm Presentation Notes
72
+
73
+ Recommended lead screenshot substitute:
74
+ - use the README's command-output sections
75
+ - keep the top fast and cinematic
76
+ - lead with install + immediate payoff
77
+
78
+ ## Suggested Release Checklist
79
+
80
+ - publish npm package
81
+ - set GitHub social preview image
82
+ - add repo description/tagline
83
+ - pin a short demo GIF or screenshot later if desired
84
+ - post the one-liner + short post copy
85
+
86
+ ## Live links
87
+
88
+ - GitHub: https://github.com/SproutSeeds/erdos-problems
89
+ - npm: https://www.npmjs.com/package/erdos-problems
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "erdos-problems",
3
- "version": "0.2.2",
4
- "description": "CLI atlas and staged research harness for Paul Erdos problems.",
3
+ "version": "0.2.4",
4
+ "description": "Research cockpit and agent-ready CLI atlas for Paul Erdos problems.",
5
5
  "type": "module",
6
6
  "bin": {
7
7
  "erdos": "bin/erdos"
@@ -13,6 +13,7 @@
13
13
  "AGENT_INTEGRATION.md",
14
14
  "bin",
15
15
  "data",
16
+ "assets",
16
17
  "docs",
17
18
  "packs",
18
19
  "problems",
@@ -25,14 +26,30 @@
25
26
  },
26
27
  "keywords": [
27
28
  "erdos",
28
- "combinatorics",
29
- "open-problems",
30
29
  "research",
30
+ "cli",
31
+ "open-problems",
32
+ "combinatorics",
33
+ "number-theory",
34
+ "graph-theory",
35
+ "theorem-proving",
36
+ "agents",
31
37
  "sunflower"
32
38
  ],
33
39
  "dependencies": {
34
40
  "breakthroughs": "^0.1.1",
35
41
  "yaml": "^2.8.3"
36
42
  },
37
- "license": "MIT"
43
+ "license": "MIT",
44
+ "engines": {
45
+ "node": ">=20"
46
+ },
47
+ "repository": {
48
+ "type": "git",
49
+ "url": "git+https://github.com/SproutSeeds/erdos-problems.git"
50
+ },
51
+ "homepage": "https://github.com/SproutSeeds/erdos-problems#readme",
52
+ "bugs": {
53
+ "url": "https://github.com/SproutSeeds/erdos-problems/issues"
54
+ }
38
55
  }