erdos-problems 0.2.0 → 0.2.2
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.
- package/README.md +88 -3
- package/docs/RESEARCH_LOOP.md +7 -0
- package/package.json +1 -1
- package/packs/graph-theory/README.md +17 -0
- package/packs/graph-theory/problems/1008/CHECKPOINT_TEMPLATE.md +9 -0
- package/packs/graph-theory/problems/1008/CONTEXT.md +9 -0
- package/packs/graph-theory/problems/1008/FRONTIER_NOTE.md +8 -0
- package/packs/graph-theory/problems/1008/OPS_DETAILS.yaml +25 -0
- package/packs/graph-theory/problems/1008/REPORT_TEMPLATE.md +9 -0
- package/packs/graph-theory/problems/1008/ROUTE_HISTORY.md +5 -0
- package/packs/graph-theory/problems/1008/ROUTE_PACKET.yaml +13 -0
- package/packs/graph-theory/problems/1008/context.yaml +27 -0
- package/packs/graph-theory/problems/19/CHECKPOINT_TEMPLATE.md +9 -0
- package/packs/graph-theory/problems/19/CONTEXT.md +9 -0
- package/packs/graph-theory/problems/19/FRONTIER_NOTE.md +8 -0
- package/packs/graph-theory/problems/19/OPS_DETAILS.yaml +25 -0
- package/packs/graph-theory/problems/19/REPORT_TEMPLATE.md +9 -0
- package/packs/graph-theory/problems/19/ROUTE_HISTORY.md +5 -0
- package/packs/graph-theory/problems/19/ROUTE_PACKET.yaml +13 -0
- package/packs/graph-theory/problems/19/context.yaml +25 -0
- package/packs/graph-theory/problems/22/CHECKPOINT_TEMPLATE.md +9 -0
- package/packs/graph-theory/problems/22/CONTEXT.md +9 -0
- package/packs/graph-theory/problems/22/FRONTIER_NOTE.md +8 -0
- package/packs/graph-theory/problems/22/OPS_DETAILS.yaml +25 -0
- package/packs/graph-theory/problems/22/REPORT_TEMPLATE.md +9 -0
- package/packs/graph-theory/problems/22/ROUTE_HISTORY.md +5 -0
- package/packs/graph-theory/problems/22/ROUTE_PACKET.yaml +13 -0
- package/packs/graph-theory/problems/22/context.yaml +26 -0
- package/packs/number-theory/README.md +16 -9
- package/packs/number-theory/problems/1/CHECKPOINT_TEMPLATE.md +7 -0
- package/packs/number-theory/problems/1/FRONTIER_NOTE.md +8 -0
- package/packs/number-theory/problems/1/OPS_DETAILS.yaml +25 -0
- package/packs/number-theory/problems/1/REPORT_TEMPLATE.md +7 -0
- package/packs/number-theory/problems/1/ROUTE_HISTORY.md +5 -0
- package/packs/number-theory/problems/1/ROUTE_PACKET.yaml +13 -0
- package/packs/number-theory/problems/1/context.yaml +10 -10
- package/packs/number-theory/problems/2/CHECKPOINT_TEMPLATE.md +7 -0
- package/packs/number-theory/problems/2/FRONTIER_NOTE.md +8 -0
- package/packs/number-theory/problems/2/OPS_DETAILS.yaml +25 -0
- package/packs/number-theory/problems/2/REPORT_TEMPLATE.md +7 -0
- package/packs/number-theory/problems/2/ROUTE_HISTORY.md +5 -0
- package/packs/number-theory/problems/2/ROUTE_PACKET.yaml +13 -0
- package/packs/number-theory/problems/2/context.yaml +11 -11
- package/packs/sunflower/README.md +2 -2
- package/packs/sunflower/problems/536/CHECKPOINT_TEMPLATE.md +7 -0
- package/packs/sunflower/problems/536/FRONTIER_NOTE.md +8 -0
- package/packs/sunflower/problems/536/REPORT_TEMPLATE.md +7 -0
- package/packs/sunflower/problems/536/ROUTE_HISTORY.md +5 -0
- package/packs/sunflower/problems/856/CHECKPOINT_TEMPLATE.md +7 -0
- package/packs/sunflower/problems/856/FRONTIER_NOTE.md +8 -0
- package/packs/sunflower/problems/856/REPORT_TEMPLATE.md +7 -0
- package/packs/sunflower/problems/856/ROUTE_HISTORY.md +5 -0
- package/src/cli/index.js +25 -8
- package/src/commands/archive.js +10 -1
- package/src/commands/cluster.js +19 -1
- package/src/commands/graph-theory.js +180 -0
- package/src/commands/number-theory.js +304 -0
- package/src/commands/pull.js +56 -4
- package/src/commands/workspace.js +55 -1
- package/src/runtime/graph-theory.js +167 -0
- package/src/runtime/number-theory.js +229 -0
- package/src/runtime/state.js +62 -0
package/README.md
CHANGED
|
@@ -22,6 +22,8 @@ Official binary:
|
|
|
22
22
|
- workspace `.erdos/` state for active-problem selection, upstream refreshes, scaffolds, and pull bundles
|
|
23
23
|
- sunflower cluster as the first deep harness pack
|
|
24
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
|
|
25
27
|
- packaged atomic/bridge board packets for the full sunflower quartet
|
|
26
28
|
- packaged compute-lane metadata for deep sunflower problems, surfaced directly in the CLI
|
|
27
29
|
- seeded atlas now includes open and solved problems beyond sunflower
|
|
@@ -35,7 +37,8 @@ Native dossier count:
|
|
|
35
37
|
|
|
36
38
|
Pack coverage:
|
|
37
39
|
- sunflower pack: `4`
|
|
38
|
-
- number-theory starter
|
|
40
|
+
- number-theory starter cockpit: `2`
|
|
41
|
+
- graph-theory archive cockpit: `3`
|
|
39
42
|
|
|
40
43
|
## First-run flow
|
|
41
44
|
|
|
@@ -49,6 +52,8 @@ erdos sunflower frontier 857
|
|
|
49
52
|
erdos sunflower routes 857
|
|
50
53
|
erdos sunflower tickets 857
|
|
51
54
|
erdos dossier show 857
|
|
55
|
+
erdos number-theory status 1
|
|
56
|
+
erdos graph-theory status 1008
|
|
52
57
|
```
|
|
53
58
|
|
|
54
59
|
For an unseeded problem, the one-step self-seeding flow is now:
|
|
@@ -97,6 +102,7 @@ For any problem number in the upstream snapshot, you can create a workspace bund
|
|
|
97
102
|
erdos pull problem 857
|
|
98
103
|
erdos pull artifacts 857
|
|
99
104
|
erdos pull literature 857
|
|
105
|
+
erdos pull literature 857 --json
|
|
100
106
|
erdos pull literature 857 --include-crossref --include-openalex
|
|
101
107
|
erdos pull problem 999 --include-site --include-public-search
|
|
102
108
|
erdos pull problem 999 --refresh-upstream
|
|
@@ -121,6 +127,7 @@ What the pull lanes do:
|
|
|
121
127
|
- when `--include-openalex` is used, the literature lane also includes:
|
|
122
128
|
- `OPENALEX_RESULTS.json`
|
|
123
129
|
- `OPENALEX_RESULTS.md`
|
|
130
|
+
- when `--json` is used, the pull command emits an agent-friendly machine summary instead of prose
|
|
124
131
|
|
|
125
132
|
## Maintainer seeding
|
|
126
133
|
|
|
@@ -164,8 +171,8 @@ The first deep pack is the sunflower quartet:
|
|
|
164
171
|
Sunflower problems now ship pack packets:
|
|
165
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`
|
|
166
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`
|
|
167
|
-
- `536`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `OPS_DETAILS.yaml`
|
|
168
|
-
- `856`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.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`
|
|
169
176
|
|
|
170
177
|
Useful sunflower commands:
|
|
171
178
|
|
|
@@ -238,6 +245,52 @@ erdos sunflower status 857 --json
|
|
|
238
245
|
- records governance and ORP-facing packet context
|
|
239
246
|
- does not silently escalate into paid or unbounded compute
|
|
240
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:
|
|
255
|
+
|
|
256
|
+
```bash
|
|
257
|
+
erdos number-theory status 1
|
|
258
|
+
erdos number-theory frontier 1
|
|
259
|
+
erdos number-theory routes 1
|
|
260
|
+
erdos number-theory tickets 1
|
|
261
|
+
erdos number-theory route 1 distinct_subset_sum_lower_bound
|
|
262
|
+
erdos number-theory ticket 1 N1
|
|
263
|
+
erdos number-theory atom 1 N1.G1.A1
|
|
264
|
+
erdos number-theory status 2 --json
|
|
265
|
+
```
|
|
266
|
+
|
|
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
|
|
273
|
+
|
|
274
|
+
The next family pack is a deliberately honest archive/decision cockpit for seeded graph-theory problems:
|
|
275
|
+
- `19`: decision archive cockpit
|
|
276
|
+
- `22`: proof archive cockpit
|
|
277
|
+
- `1008`: Lean-facing proof archive cockpit
|
|
278
|
+
|
|
279
|
+
Useful graph-theory commands:
|
|
280
|
+
|
|
281
|
+
```bash
|
|
282
|
+
erdos graph-theory status 19
|
|
283
|
+
erdos graph-theory frontier 22
|
|
284
|
+
erdos graph-theory routes 1008
|
|
285
|
+
erdos graph-theory tickets 1008
|
|
286
|
+
erdos graph-theory status 1008 --json
|
|
287
|
+
```
|
|
288
|
+
|
|
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
|
|
293
|
+
|
|
241
294
|
## Archive mode
|
|
242
295
|
|
|
243
296
|
Solved problems can now be treated as method exemplars instead of dead entries.
|
|
@@ -246,6 +299,10 @@ Solved problems can now be treated as method exemplars instead of dead entries.
|
|
|
246
299
|
erdos problem show 1008
|
|
247
300
|
erdos archive show 1008
|
|
248
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
|
|
249
306
|
```
|
|
250
307
|
|
|
251
308
|
Archive scaffolds land in:
|
|
@@ -291,7 +348,10 @@ erdos problem artifacts 857
|
|
|
291
348
|
erdos problem artifacts 857 --json
|
|
292
349
|
erdos cluster list
|
|
293
350
|
erdos cluster show sunflower
|
|
351
|
+
erdos cluster show number-theory
|
|
352
|
+
erdos cluster show graph-theory
|
|
294
353
|
erdos workspace show
|
|
354
|
+
erdos workspace show --json
|
|
295
355
|
erdos orp show
|
|
296
356
|
erdos orp sync
|
|
297
357
|
erdos sunflower status 857
|
|
@@ -305,6 +365,17 @@ erdos sunflower route 857 anchored_selector_linearization
|
|
|
305
365
|
erdos sunflower ticket 857 T10
|
|
306
366
|
erdos sunflower atom 857 T10.G3.A2
|
|
307
367
|
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
|
|
372
|
+
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
|
+
erdos graph-theory status 1008
|
|
376
|
+
erdos graph-theory frontier 22
|
|
377
|
+
erdos graph-theory routes 1008
|
|
378
|
+
erdos graph-theory tickets 19
|
|
308
379
|
erdos sunflower status --json
|
|
309
380
|
erdos dossier show
|
|
310
381
|
erdos upstream show
|
|
@@ -319,6 +390,7 @@ erdos seed problem 25 --cluster number-theory
|
|
|
319
390
|
erdos pull problem 857
|
|
320
391
|
erdos pull artifacts 857
|
|
321
392
|
erdos pull literature 857
|
|
393
|
+
erdos pull literature 857 --json
|
|
322
394
|
erdos pull literature 857 --include-crossref --include-openalex
|
|
323
395
|
erdos maintainer review problem 25 --from-pull .erdos/pulls/25
|
|
324
396
|
erdos maintainer seed problem 25 --from-pull .erdos/pulls/25 --cluster number-theory
|
|
@@ -366,6 +438,19 @@ For sunflower problems, the CLI also surfaces pack-specific artifacts:
|
|
|
366
438
|
- compute packets under `packs/sunflower/compute/<id>/` when available
|
|
367
439
|
- compute-governance evaluation under `breakthroughs`, surfaced through `erdos sunflower status`
|
|
368
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
|
+
|
|
369
454
|
## Notes
|
|
370
455
|
|
|
371
456
|
- `erdos-problems` is the canonical npm package name.
|
package/docs/RESEARCH_LOOP.md
CHANGED
|
@@ -85,6 +85,13 @@ For sunflower compute lanes, ORP now sits above `breakthroughs`:
|
|
|
85
85
|
- the CLI surfaces the selected rung, dispatch action, and the reason compute is admissible
|
|
86
86
|
- this is compute governance and traceability, not an automatic paid or unbounded compute launch
|
|
87
87
|
|
|
88
|
+
For number-theory starter-cockpit problems:
|
|
89
|
+
- `erdos number-theory status <id>` exposes the current route/frontier posture
|
|
90
|
+
- `erdos number-theory frontier <id>` compresses the honest next move
|
|
91
|
+
- `erdos number-theory routes <id>` exposes the small route table
|
|
92
|
+
- `erdos number-theory tickets <id>` exposes the current ticket/archive packet
|
|
93
|
+
- this is deliberately lighter than the sunflower pack and should stay honest about that
|
|
94
|
+
|
|
88
95
|
For solved problems:
|
|
89
96
|
- `erdos archive show <id>` exposes archival posture
|
|
90
97
|
- `erdos archive scaffold <id>` creates a method-exemplar bundle under `.erdos/archives/<id>/`
|
package/package.json
CHANGED
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# Graph-Theory Pack
|
|
2
|
+
|
|
3
|
+
Archive and decision cockpit for graph-theory problems in `erdos-problems`.
|
|
4
|
+
|
|
5
|
+
Current seeded cockpit problems:
|
|
6
|
+
- `19`: decision/archive cockpit around the chromatic-number record
|
|
7
|
+
- `22`: proof archive cockpit around the Ramsey-Turan `K_4` construction record
|
|
8
|
+
- `1008`: Lean-facing proof archive cockpit for the `C_4`-free density problem
|
|
9
|
+
|
|
10
|
+
Useful commands:
|
|
11
|
+
- `erdos graph-theory status 19`
|
|
12
|
+
- `erdos graph-theory frontier 22`
|
|
13
|
+
- `erdos graph-theory routes 1008`
|
|
14
|
+
- `erdos graph-theory tickets 1008`
|
|
15
|
+
|
|
16
|
+
Design rule:
|
|
17
|
+
- keep this pack honest as an archive/decision cockpit until a real open graph-theory frontier earns deeper gated flow
|
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
# Problem 1008 Graph-Theory Pack Context
|
|
2
|
+
|
|
3
|
+
Role in pack:
|
|
4
|
+
- Lean-facing proof archive for the `C_4`-free density problem
|
|
5
|
+
- solved graph-theory cockpit rather than a live open frontier
|
|
6
|
+
|
|
7
|
+
Bootstrap focus:
|
|
8
|
+
- preserve the solved status and Lean-facing badge
|
|
9
|
+
- keep the extremal-graph question and archive references synchronized
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
# Problem 1008 Frontier Note
|
|
2
|
+
|
|
3
|
+
Problem 1008 is packaged as a Lean-facing proof archive.
|
|
4
|
+
|
|
5
|
+
Current honest posture:
|
|
6
|
+
- preserve the solved public record
|
|
7
|
+
- keep the `C_4`-free density framing explicit
|
|
8
|
+
- treat improvements here as archive or method-exemplar work, not open-frontier work
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
packet_id: gt1008_ops_details_v1
|
|
2
|
+
summary: Lean-facing proof archive cockpit packet for the `C_4`-free density result.
|
|
3
|
+
routes:
|
|
4
|
+
- route_id: c4_free_lean_archive
|
|
5
|
+
title: "`C_4`-Free Lean Proof Archive"
|
|
6
|
+
status: closed
|
|
7
|
+
summary: Keep the solved `C_4`-free density record explicit and preserve the Lean-facing archive posture.
|
|
8
|
+
why_now: This is the honest archive framing for Problem 1008.
|
|
9
|
+
next_move: Freeze the best Lean-facing source hook and checkpoint the archive packet.
|
|
10
|
+
tickets:
|
|
11
|
+
- ticket_id: G1008
|
|
12
|
+
title: "Tighten the `C_4`-free Lean archive packet"
|
|
13
|
+
route_id: c4_free_lean_archive
|
|
14
|
+
status: active
|
|
15
|
+
summary: Package the solved record clearly enough that the archive stays usable as a method exemplar.
|
|
16
|
+
current_blocker: The archive still needs a sharper Lean-facing source hook.
|
|
17
|
+
next_move: Close `G1008.G1.A1`.
|
|
18
|
+
atoms:
|
|
19
|
+
- atom_id: G1008.G1.A1
|
|
20
|
+
title: "Freeze the primary Lean-facing archive hook for the `C_4`-free density result"
|
|
21
|
+
route_id: c4_free_lean_archive
|
|
22
|
+
ticket_id: G1008
|
|
23
|
+
status: ready
|
|
24
|
+
summary: This is the smallest honest archive move for Problem 1008.
|
|
25
|
+
next_move: Record the best public/formalization hook and checkpoint the archive packet.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
route_packet_id: gt1008_c4_free_lean_archive_v1
|
|
2
|
+
route_id: c4_free_lean_archive
|
|
3
|
+
frontier_claim: Preserve the solved `C_4`-free density record as a Lean-facing archive packet and keep the source trail synchronized with the dossier.
|
|
4
|
+
theorem_module: ""
|
|
5
|
+
checkpoint_packet: CHECKPOINT_TEMPLATE.md
|
|
6
|
+
report_packet: REPORT_TEMPLATE.md
|
|
7
|
+
ready_prompts:
|
|
8
|
+
- Which exact source or formalization hook should anchor the Lean archive packet first?
|
|
9
|
+
- Which wording best preserves the solved posture without inflating the public claim?
|
|
10
|
+
verification_hook:
|
|
11
|
+
- erdos graph-theory status 1008
|
|
12
|
+
- erdos archive show 1008 --json
|
|
13
|
+
- erdos archive scaffold 1008 --json
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
problem_id: "1008"
|
|
2
|
+
family_role: c4_free_lean_archive
|
|
3
|
+
harness_profile: lean_archive_cockpit
|
|
4
|
+
default_active_route: c4_free_lean_archive
|
|
5
|
+
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.
|
|
6
|
+
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.
|
|
7
|
+
frontier_label: c4_free_lean_archive
|
|
8
|
+
frontier_detail: Preserve the Lean-facing solved record and the `C_4`-free density framing without widening the claim beyond the public dossier.
|
|
9
|
+
checkpoint_focus: Keep the solved status, Lean-facing archive wording, and main source trail synchronized.
|
|
10
|
+
next_honest_move: Tighten the Lean proof archive note and freeze the best public/formalization source hook for the `C_4`-free density result.
|
|
11
|
+
related_core_problems: []
|
|
12
|
+
literature_focus:
|
|
13
|
+
- graph theory
|
|
14
|
+
- extremal graph theory
|
|
15
|
+
- formalization
|
|
16
|
+
artifact_focus:
|
|
17
|
+
- STATEMENT.md
|
|
18
|
+
- REFERENCES.md
|
|
19
|
+
- FORMALIZATION.md
|
|
20
|
+
question_ledger:
|
|
21
|
+
open_questions:
|
|
22
|
+
- Which exact Lean-facing artifact should anchor the archive packet first?
|
|
23
|
+
active_route_notes:
|
|
24
|
+
- Treat Problem 1008 as a solved Lean archive, not as a live frontier.
|
|
25
|
+
route_breakthroughs: []
|
|
26
|
+
problem_solved:
|
|
27
|
+
- The public site marks this problem as solved with a Lean-facing badge.
|
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
# Problem 19 Graph-Theory Pack Context
|
|
2
|
+
|
|
3
|
+
Role in pack:
|
|
4
|
+
- chromatic-number decision archive
|
|
5
|
+
- graph-theory archive cockpit rather than a live theorem frontier today
|
|
6
|
+
|
|
7
|
+
Bootstrap focus:
|
|
8
|
+
- keep the public decision posture explicit
|
|
9
|
+
- preserve the best source trail for the record
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
packet_id: gt19_ops_details_v1
|
|
2
|
+
summary: Decision/archive cockpit packet for the chromatic-number record.
|
|
3
|
+
routes:
|
|
4
|
+
- route_id: chromatic_decision_record
|
|
5
|
+
title: Chromatic Decision Record
|
|
6
|
+
status: archival
|
|
7
|
+
summary: Keep the public decision posture and chromatic-number framing synchronized.
|
|
8
|
+
why_now: This is the honest archive framing for Problem 19 today.
|
|
9
|
+
next_move: Freeze the best source hook describing the decision record.
|
|
10
|
+
tickets:
|
|
11
|
+
- ticket_id: G19
|
|
12
|
+
title: Tighten the chromatic decision archive packet
|
|
13
|
+
route_id: chromatic_decision_record
|
|
14
|
+
status: active
|
|
15
|
+
summary: Package the decision record clearly enough that future agents do not misread the dossier.
|
|
16
|
+
current_blocker: The primary source hook for the decision posture is still too loose.
|
|
17
|
+
next_move: Close `G19.G1.A1`.
|
|
18
|
+
atoms:
|
|
19
|
+
- atom_id: G19.G1.A1
|
|
20
|
+
title: Freeze the primary chromatic-number decision source hook
|
|
21
|
+
route_id: chromatic_decision_record
|
|
22
|
+
ticket_id: G19
|
|
23
|
+
status: ready
|
|
24
|
+
summary: This is the smallest honest archive move for Problem 19.
|
|
25
|
+
next_move: Record the strongest public source hook and checkpoint the archive packet.
|
|
@@ -0,0 +1,5 @@
|
|
|
1
|
+
# Problem 19 Route History
|
|
2
|
+
|
|
3
|
+
- Initial public pack lift: moved the dossier into a graph-theory decision archive cockpit.
|
|
4
|
+
- Current route: `chromatic_decision_record`.
|
|
5
|
+
- Honest next improvement: freeze the best source explaining the decision posture and checkpoint it.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
route_packet_id: gt19_chromatic_decision_archive_v1
|
|
2
|
+
route_id: chromatic_decision_record
|
|
3
|
+
frontier_claim: Preserve the chromatic-number decision record as a clean archive packet and keep the source trail synchronized with the dossier.
|
|
4
|
+
theorem_module: ""
|
|
5
|
+
checkpoint_packet: CHECKPOINT_TEMPLATE.md
|
|
6
|
+
report_packet: REPORT_TEMPLATE.md
|
|
7
|
+
ready_prompts:
|
|
8
|
+
- Which exact source or note should anchor the decision archive first?
|
|
9
|
+
- Which wording most clearly prevents future agents from treating this as an open frontier?
|
|
10
|
+
verification_hook:
|
|
11
|
+
- erdos graph-theory status 19
|
|
12
|
+
- erdos graph-theory tickets 19
|
|
13
|
+
- erdos archive show 19 --json
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
problem_id: "19"
|
|
2
|
+
family_role: chromatic_number_decision_archive
|
|
3
|
+
harness_profile: decision_archive_cockpit
|
|
4
|
+
default_active_route: chromatic_decision_record
|
|
5
|
+
bootstrap_focus: Freeze the exact chromatic-number decision posture, the dossier provenance, and the archive packet without drifting back into open-problem language.
|
|
6
|
+
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.
|
|
7
|
+
frontier_label: chromatic_decision_record
|
|
8
|
+
frontier_detail: Keep the decision posture and the primary chromatic-number source trail explicit.
|
|
9
|
+
checkpoint_focus: Synchronize the public decision status, archive packet, and primary references every time this dossier is touched.
|
|
10
|
+
next_honest_move: Tighten the decision archive note and freeze the best public-facing source hook for the chromatic-number record.
|
|
11
|
+
related_core_problems: []
|
|
12
|
+
literature_focus:
|
|
13
|
+
- graph theory
|
|
14
|
+
- chromatic number
|
|
15
|
+
artifact_focus:
|
|
16
|
+
- STATEMENT.md
|
|
17
|
+
- REFERENCES.md
|
|
18
|
+
- EVIDENCE.md
|
|
19
|
+
question_ledger:
|
|
20
|
+
open_questions:
|
|
21
|
+
- Which exact source best explains why the public record marks this problem as decidable?
|
|
22
|
+
active_route_notes:
|
|
23
|
+
- Treat Problem 19 as a decision archive, not as a live open frontier.
|
|
24
|
+
route_breakthroughs: []
|
|
25
|
+
problem_solved: []
|
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
# Problem 22 Graph-Theory Pack Context
|
|
2
|
+
|
|
3
|
+
Role in pack:
|
|
4
|
+
- Ramsey-Turan proof archive
|
|
5
|
+
- solved graph-theory cockpit rather than a live open frontier
|
|
6
|
+
|
|
7
|
+
Bootstrap focus:
|
|
8
|
+
- preserve the solved status cleanly
|
|
9
|
+
- keep the extremal-graph framing and reference trail synchronized
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
packet_id: gt22_ops_details_v1
|
|
2
|
+
summary: Proof archive cockpit packet for the Ramsey-Turan `K_4` record.
|
|
3
|
+
routes:
|
|
4
|
+
- route_id: ramsey_turan_k4_archive
|
|
5
|
+
title: Ramsey-Turan `K_4` Proof Archive
|
|
6
|
+
status: archival
|
|
7
|
+
summary: Keep the solved Ramsey-Turan record explicit and preserve the extremal-graph proof framing.
|
|
8
|
+
why_now: This is the honest public posture for Problem 22.
|
|
9
|
+
next_move: Freeze the strongest proof reference and checkpoint the archive packet.
|
|
10
|
+
tickets:
|
|
11
|
+
- ticket_id: G22
|
|
12
|
+
title: Tighten the Ramsey-Turan proof archive packet
|
|
13
|
+
route_id: ramsey_turan_k4_archive
|
|
14
|
+
status: active
|
|
15
|
+
summary: Package the solved record clearly enough that agents cannot mistake it for an open frontier.
|
|
16
|
+
current_blocker: The archive still needs a stronger primary proof hook.
|
|
17
|
+
next_move: Close `G22.G1.A1`.
|
|
18
|
+
atoms:
|
|
19
|
+
- atom_id: G22.G1.A1
|
|
20
|
+
title: Freeze the primary solved-reference hook for the Ramsey-Turan record
|
|
21
|
+
route_id: ramsey_turan_k4_archive
|
|
22
|
+
ticket_id: G22
|
|
23
|
+
status: ready
|
|
24
|
+
summary: This is the smallest honest archive move for Problem 22.
|
|
25
|
+
next_move: Record the strongest public proof hook and checkpoint the archive packet.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
route_packet_id: gt22_ramsey_turan_proof_archive_v1
|
|
2
|
+
route_id: ramsey_turan_k4_archive
|
|
3
|
+
frontier_claim: Preserve the solved Ramsey-Turan `K_4` record as a proof archive packet and keep the strongest reference trail explicit.
|
|
4
|
+
theorem_module: ""
|
|
5
|
+
checkpoint_packet: CHECKPOINT_TEMPLATE.md
|
|
6
|
+
report_packet: REPORT_TEMPLATE.md
|
|
7
|
+
ready_prompts:
|
|
8
|
+
- Which exact proof reference should anchor the archive packet first?
|
|
9
|
+
- Which wording best prevents agents from drifting back into open-problem language here?
|
|
10
|
+
verification_hook:
|
|
11
|
+
- erdos graph-theory status 22
|
|
12
|
+
- erdos graph-theory frontier 22
|
|
13
|
+
- erdos archive show 22 --json
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
problem_id: "22"
|
|
2
|
+
family_role: ramsey_turan_proof_archive
|
|
3
|
+
harness_profile: proof_archive_cockpit
|
|
4
|
+
default_active_route: ramsey_turan_k4_archive
|
|
5
|
+
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.
|
|
6
|
+
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.
|
|
7
|
+
frontier_label: ramsey_turan_k4_archive
|
|
8
|
+
frontier_detail: Preserve the affirmative proof posture and the extremal graph framing without blurring it into an open program.
|
|
9
|
+
checkpoint_focus: Keep the proof archive wording, the public solved status, and the main source trail synchronized.
|
|
10
|
+
next_honest_move: Tighten the Ramsey-Turan proof archive note and freeze the strongest source hook for the solved record.
|
|
11
|
+
related_core_problems: []
|
|
12
|
+
literature_focus:
|
|
13
|
+
- graph theory
|
|
14
|
+
- Ramsey-Turan theory
|
|
15
|
+
artifact_focus:
|
|
16
|
+
- STATEMENT.md
|
|
17
|
+
- REFERENCES.md
|
|
18
|
+
- EVIDENCE.md
|
|
19
|
+
question_ledger:
|
|
20
|
+
open_questions:
|
|
21
|
+
- Which exact reference should anchor the proof archive packet first?
|
|
22
|
+
active_route_notes:
|
|
23
|
+
- Treat Problem 22 as a proof archive, not as a live open cockpit.
|
|
24
|
+
route_breakthroughs: []
|
|
25
|
+
problem_solved:
|
|
26
|
+
- The public site marks this problem as proved.
|
|
@@ -1,13 +1,20 @@
|
|
|
1
1
|
# Number Theory Pack
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Light starter cockpit for number-theory problems in `erdos-problems`.
|
|
4
4
|
|
|
5
|
-
Current
|
|
6
|
-
-
|
|
7
|
-
-
|
|
8
|
-
- no deep board/compute loop yet
|
|
5
|
+
Current seeded cockpit problems:
|
|
6
|
+
- `1`: open starter cockpit around a distinct-subset-sum lower-bound route
|
|
7
|
+
- `2`: counterexample/archive cockpit for a disproved covering-systems problem
|
|
9
8
|
|
|
10
|
-
|
|
11
|
-
-
|
|
12
|
-
-
|
|
13
|
-
-
|
|
9
|
+
Useful commands:
|
|
10
|
+
- `erdos number-theory status 1`
|
|
11
|
+
- `erdos number-theory frontier 1`
|
|
12
|
+
- `erdos number-theory routes 1`
|
|
13
|
+
- `erdos number-theory tickets 1`
|
|
14
|
+
- `erdos number-theory route 1 distinct_subset_sum_lower_bound`
|
|
15
|
+
- `erdos number-theory ticket 1 N1`
|
|
16
|
+
- `erdos number-theory atom 1 N1.G1.A1`
|
|
17
|
+
- `erdos number-theory status 2 --json`
|
|
18
|
+
|
|
19
|
+
Design rule:
|
|
20
|
+
- keep this pack lighter than sunflower until a deeper theorem-board frontier is honestly earned
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
# Problem 1 Frontier Note
|
|
2
|
+
|
|
3
|
+
This is a starter cockpit, not a deep theorem board.
|
|
4
|
+
|
|
5
|
+
The honest live route is the distinct-subset-sum lower-bound route:
|
|
6
|
+
- keep the problem statement exact
|
|
7
|
+
- keep the additive lower-bound framing explicit
|
|
8
|
+
- do not widen this into a generic additive-combinatorics program
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
packet_id: nt1_ops_details_v1
|
|
2
|
+
summary: Starter cockpit packet for the distinct-subset-sum lower-bound route.
|
|
3
|
+
routes:
|
|
4
|
+
- route_id: distinct_subset_sum_lower_bound
|
|
5
|
+
title: Distinct Subset-Sum Lower Bound
|
|
6
|
+
status: active
|
|
7
|
+
summary: Keep the problem centered on the exponential-growth lower-bound route implied by distinct subset sums.
|
|
8
|
+
why_now: This is the smallest honest route that turns the dossier into a real cockpit.
|
|
9
|
+
next_move: Freeze the first exact reduction and connect it to the canonical references.
|
|
10
|
+
tickets:
|
|
11
|
+
- ticket_id: N1
|
|
12
|
+
title: Freeze the lower-bound route note
|
|
13
|
+
route_id: distinct_subset_sum_lower_bound
|
|
14
|
+
status: active
|
|
15
|
+
summary: Turn the starter dossier into a stable lower-bound cockpit.
|
|
16
|
+
current_blocker: The first exact reduction and evidence stack are not yet frozen together.
|
|
17
|
+
next_move: Close `N1.G1.A1`.
|
|
18
|
+
atoms:
|
|
19
|
+
- atom_id: N1.G1.A1
|
|
20
|
+
title: Freeze the first exact lower-bound reduction and its reference hook
|
|
21
|
+
route_id: distinct_subset_sum_lower_bound
|
|
22
|
+
ticket_id: N1
|
|
23
|
+
status: ready
|
|
24
|
+
summary: This is the smallest honest move that upgrades the dossier into a route-aware cockpit.
|
|
25
|
+
next_move: Record the first reduction and checkpoint it without overclaiming theorem progress.
|