erdos-problems 0.2.1 → 0.2.3

package/docs/LAUNCH_KIT.md

@@ -0,0 +1,84 @@
+# Launch Kit
+
+## Positioning
+
+Short version:
+- `erdos-problems` is a research cockpit 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.
+
+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.
+
+## Launch Copy
+
+### One-liner
+- Research cockpit 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`.
+
+### 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.
+
+## Demo Flow
+
+```bash
+npm install -g erdos-problems
+erdos bootstrap problem 857
+erdos sunflower frontier 857
+erdos problem artifacts 857 --json
+```
+
+Backup demo flow:
+
+```bash
+erdos seed problem 25 --cluster number-theory
+erdos workspace show --json
+```
+
+Archive demo flow:
+
+```bash
+erdos graph-theory status 1008
+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.
+
+## GitHub Presentation Notes
+
+Recommended repo tagline:
+- Research cockpit for Paul Erdos problems.
+
+Recommended social preview:
+- `assets/social-card.svg`
+- export a PNG from it for GitHub social preview if GitHub wants raster upload
+
+Recommended pinned bullets:
+- atlas + dossiers
+- ORP-governed workspaces
+- self-seeding from public sources
+- sunflower family cockpit
+
+## 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
+
+## 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
+- post the one-liner + short post copy

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "erdos-problems",
-  "version": "0.2.1",
-  "description": "CLI atlas and staged research harness for Paul Erdos problems.",
+  "version": "0.2.3",
+  "description": "Research cockpit and agent-ready CLI atlas for Paul Erdos problems.",
   "type": "module",
   "bin": {
     "erdos": "bin/erdos"
@@ -25,14 +25,22 @@
   },
   "keywords": [
     "erdos",
-    "combinatorics",
-    "open-problems",
     "research",
+    "cli",
+    "open-problems",
+    "combinatorics",
+    "number-theory",
+    "graph-theory",
+    "theorem-proving",
+    "agents",
     "sunflower"
   ],
   "dependencies": {
     "breakthroughs": "^0.1.1",
     "yaml": "^2.8.3"
   },
-  "license": "MIT"
+  "license": "MIT",
+  "engines": {
+    "node": ">=20"
+  }
 }

package/packs/graph-theory/README.md

@@ -0,0 +1,17 @@
+# Graph-Theory Pack
+
+Archive and decision cockpit 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
+
+Useful commands:
+- `erdos graph-theory status 19`
+- `erdos graph-theory frontier 22`
+- `erdos graph-theory routes 1008`
+- `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

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

@@ -0,0 +1,9 @@
+# Problem 1008 Checkpoint Template
+
+## Lean Archive
+- Solved status wording:
+- Lean-facing artifact frozen:
+- Archive drift risk:
+
+## Next Honest Move
+- 

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

@@ -0,0 +1,9 @@
+# Problem 1008 Graph-Theory Pack Context
+
+Role in pack:
+- Lean-facing proof archive for the `C_4`-free density problem
+- solved graph-theory cockpit rather than a live open frontier
+
+Bootstrap focus:
+- preserve the solved status and Lean-facing badge
+- keep the extremal-graph question and archive references synchronized

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

@@ -0,0 +1,8 @@
+# Problem 1008 Frontier Note
+
+Problem 1008 is packaged as a Lean-facing proof archive.
+
+Current honest posture:
+- preserve the solved public record
+- keep the `C_4`-free density framing explicit
+- treat improvements here as archive or method-exemplar work, not open-frontier work

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

@@ -0,0 +1,25 @@
+packet_id: gt1008_ops_details_v1
+summary: Lean-facing proof archive cockpit packet for the `C_4`-free density result.
+routes:
+  - route_id: c4_free_lean_archive
+    title: "`C_4`-Free Lean Proof Archive"
+    status: closed
+    summary: Keep the solved `C_4`-free density record explicit and preserve the Lean-facing archive posture.
+    why_now: This is the honest archive framing for Problem 1008.
+    next_move: Freeze the best Lean-facing source hook and checkpoint the archive packet.
+tickets:
+  - ticket_id: G1008
+    title: "Tighten the `C_4`-free Lean archive packet"
+    route_id: c4_free_lean_archive
+    status: active
+    summary: Package the solved record clearly enough that the archive stays usable as a method exemplar.
+    current_blocker: The archive still needs a sharper Lean-facing source hook.
+    next_move: Close `G1008.G1.A1`.
+atoms:
+  - atom_id: G1008.G1.A1
+    title: "Freeze the primary Lean-facing archive hook for the `C_4`-free density result"
+    route_id: c4_free_lean_archive
+    ticket_id: G1008
+    status: ready
+    summary: This is the smallest honest archive move for Problem 1008.
+    next_move: Record the best public/formalization hook and checkpoint the archive packet.

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

@@ -0,0 +1,9 @@
+# Problem 1008 Report Template
+
+## Archive Summary
+- Lean archive status:
+- Source alignment:
+- Reusable method note:
+
+## Follow-up
+- 

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

@@ -0,0 +1,5 @@
+# Problem 1008 Route History
+
+- Initial public pack lift: moved the dossier into a graph-theory Lean archive cockpit.
+- 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/ROUTE_PACKET.yaml

@@ -0,0 +1,13 @@
+route_packet_id: gt1008_c4_free_lean_archive_v1
+route_id: c4_free_lean_archive
+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.
+theorem_module: ""
+checkpoint_packet: CHECKPOINT_TEMPLATE.md
+report_packet: REPORT_TEMPLATE.md
+ready_prompts:
+  - Which exact source or formalization hook should anchor the Lean archive packet first?
+  - Which wording best preserves the solved posture without inflating the public claim?
+verification_hook:
+  - erdos graph-theory status 1008
+  - erdos archive show 1008 --json
+  - erdos archive scaffold 1008 --json

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

@@ -0,0 +1,27 @@
+problem_id: "1008"
+family_role: c4_free_lean_archive
+harness_profile: lean_archive_cockpit
+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.
+frontier_label: c4_free_lean_archive
+frontier_detail: Preserve the Lean-facing solved record and the `C_4`-free density framing without widening the claim beyond the public dossier.
+checkpoint_focus: Keep the solved status, Lean-facing archive wording, and main source trail synchronized.
+next_honest_move: Tighten the Lean proof archive note and freeze the best public/formalization source hook for the `C_4`-free density result.
+related_core_problems: []
+literature_focus:
+  - graph theory
+  - extremal graph theory
+  - formalization
+artifact_focus:
+  - STATEMENT.md
+  - REFERENCES.md
+  - FORMALIZATION.md
+question_ledger:
+  open_questions:
+    - Which exact Lean-facing artifact should anchor the archive packet first?
+  active_route_notes:
+    - Treat Problem 1008 as a solved Lean archive, not as a live frontier.
+  route_breakthroughs: []
+  problem_solved:
+    - The public site marks this problem as solved with a Lean-facing badge.

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

@@ -0,0 +1,9 @@
+# Problem 19 Checkpoint Template
+
+## Decision Archive
+- Exact decision posture:
+- Primary source frozen:
+- Public wording preserved:
+
+## Next Honest Move
+- 

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

@@ -0,0 +1,9 @@
+# Problem 19 Graph-Theory Pack Context
+
+Role in pack:
+- chromatic-number decision archive
+- graph-theory archive cockpit rather than a live theorem frontier today
+
+Bootstrap focus:
+- keep the public decision posture explicit
+- preserve the best source trail for the record

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

@@ -0,0 +1,8 @@
+# Problem 19 Frontier Note
+
+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

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

@@ -0,0 +1,25 @@
+packet_id: gt19_ops_details_v1
+summary: Decision/archive cockpit packet for the chromatic-number record.
+routes:
+  - route_id: chromatic_decision_record
+    title: Chromatic Decision Record
+    status: archival
+    summary: Keep the public decision posture and chromatic-number framing synchronized.
+    why_now: This is the honest archive framing for Problem 19 today.
+    next_move: Freeze the best source hook describing the decision record.
+tickets:
+  - ticket_id: G19
+    title: Tighten the chromatic decision archive packet
+    route_id: chromatic_decision_record
+    status: active
+    summary: Package the decision record clearly enough that future agents do not misread the dossier.
+    current_blocker: The primary source hook for the decision posture is still too loose.
+    next_move: Close `G19.G1.A1`.
+atoms:
+  - atom_id: G19.G1.A1
+    title: Freeze the primary chromatic-number decision source hook
+    route_id: chromatic_decision_record
+    ticket_id: G19
+    status: ready
+    summary: This is the smallest honest archive move for Problem 19.
+    next_move: Record the strongest public source hook and checkpoint the archive packet.

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

@@ -0,0 +1,9 @@
+# Problem 19 Report Template
+
+## Archive Summary
+- Decision posture:
+- Source alignment:
+- Drift risk:
+
+## Follow-up
+- 

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

@@ -0,0 +1,5 @@
+# Problem 19 Route History
+
+- Initial public pack lift: moved the dossier into a graph-theory decision archive cockpit.
+- 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/ROUTE_PACKET.yaml

@@ -0,0 +1,13 @@
+route_packet_id: gt19_chromatic_decision_archive_v1
+route_id: chromatic_decision_record
+frontier_claim: Preserve the chromatic-number decision record as a clean archive packet and keep the source trail synchronized with the dossier.
+theorem_module: ""
+checkpoint_packet: CHECKPOINT_TEMPLATE.md
+report_packet: REPORT_TEMPLATE.md
+ready_prompts:
+  - Which exact source or note should anchor the decision archive first?
+  - Which wording most clearly prevents future agents from treating this as an open frontier?
+verification_hook:
+  - erdos graph-theory status 19
+  - erdos graph-theory tickets 19
+  - erdos archive show 19 --json

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

@@ -0,0 +1,25 @@
+problem_id: "19"
+family_role: chromatic_number_decision_archive
+harness_profile: decision_archive_cockpit
+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.
+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.
+next_honest_move: Tighten the decision archive note and freeze the best public-facing source hook for the chromatic-number record.
+related_core_problems: []
+literature_focus:
+  - graph theory
+  - chromatic number
+artifact_focus:
+  - STATEMENT.md
+  - REFERENCES.md
+  - EVIDENCE.md
+question_ledger:
+  open_questions:
+    - Which exact source best explains why the public record marks this problem as decidable?
+  active_route_notes:
+    - Treat Problem 19 as a decision archive, not as a live open frontier.
+  route_breakthroughs: []
+  problem_solved: []

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

@@ -0,0 +1,9 @@
+# Problem 22 Checkpoint Template
+
+## Proof Archive
+- Solved status wording:
+- Primary proof source frozen:
+- Archive drift risk:
+
+## Next Honest Move
+- 

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

@@ -0,0 +1,9 @@
+# Problem 22 Graph-Theory Pack Context
+
+Role in pack:
+- Ramsey-Turan proof archive
+- solved graph-theory cockpit rather than a live open frontier
+
+Bootstrap focus:
+- preserve the solved status cleanly
+- keep the extremal-graph framing and reference trail synchronized

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

@@ -0,0 +1,8 @@
+# Problem 22 Frontier Note
+
+Problem 22 is packaged as a proof archive.
+
+Current honest posture:
+- preserve the public solved status
+- keep the Ramsey-Turan framing explicit
+- treat improvements here as archive clarification, not live frontier pressure

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

@@ -0,0 +1,25 @@
+packet_id: gt22_ops_details_v1
+summary: Proof archive cockpit packet for the Ramsey-Turan `K_4` record.
+routes:
+  - route_id: ramsey_turan_k4_archive
+    title: Ramsey-Turan `K_4` Proof Archive
+    status: archival
+    summary: Keep the solved Ramsey-Turan record explicit and preserve the extremal-graph proof framing.
+    why_now: This is the honest public posture for Problem 22.
+    next_move: Freeze the strongest proof reference and checkpoint the archive packet.
+tickets:
+  - ticket_id: G22
+    title: Tighten the Ramsey-Turan proof archive packet
+    route_id: ramsey_turan_k4_archive
+    status: active
+    summary: Package the solved record clearly enough that agents cannot mistake it for an open frontier.
+    current_blocker: The archive still needs a stronger primary proof hook.
+    next_move: Close `G22.G1.A1`.
+atoms:
+  - atom_id: G22.G1.A1
+    title: Freeze the primary solved-reference hook for the Ramsey-Turan record
+    route_id: ramsey_turan_k4_archive
+    ticket_id: G22
+    status: ready
+    summary: This is the smallest honest archive move for Problem 22.
+    next_move: Record the strongest public proof hook and checkpoint the archive packet.

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

@@ -0,0 +1,9 @@
+# Problem 22 Report Template
+
+## Archive Summary
+- Proof archive status:
+- Source alignment:
+- Remaining clarification work:
+
+## Follow-up
+- 

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

@@ -0,0 +1,5 @@
+# Problem 22 Route History
+
+- Initial public pack lift: moved the dossier into a graph-theory proof archive cockpit.
+- 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/ROUTE_PACKET.yaml

@@ -0,0 +1,13 @@
+route_packet_id: gt22_ramsey_turan_proof_archive_v1
+route_id: ramsey_turan_k4_archive
+frontier_claim: Preserve the solved Ramsey-Turan `K_4` record as a proof archive packet and keep the strongest reference trail explicit.
+theorem_module: ""
+checkpoint_packet: CHECKPOINT_TEMPLATE.md
+report_packet: REPORT_TEMPLATE.md
+ready_prompts:
+  - Which exact proof reference should anchor the archive packet first?
+  - Which wording best prevents agents from drifting back into open-problem language here?
+verification_hook:
+  - erdos graph-theory status 22
+  - erdos graph-theory frontier 22
+  - erdos archive show 22 --json

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

@@ -0,0 +1,26 @@
+problem_id: "22"
+family_role: ramsey_turan_proof_archive
+harness_profile: proof_archive_cockpit
+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.
+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.
+next_honest_move: Tighten the Ramsey-Turan proof archive note and freeze the strongest source hook for the solved record.
+related_core_problems: []
+literature_focus:
+  - graph theory
+  - Ramsey-Turan theory
+artifact_focus:
+  - STATEMENT.md
+  - REFERENCES.md
+  - EVIDENCE.md
+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.
+  route_breakthroughs: []
+  problem_solved:
+    - The public site marks this problem as proved.

package/packs/number-theory/README.md

@@ -11,6 +11,9 @@ Useful commands:
 - `erdos number-theory frontier 1`
 - `erdos number-theory routes 1`
 - `erdos number-theory tickets 1`
+- `erdos number-theory route 1 distinct_subset_sum_lower_bound`
+- `erdos number-theory ticket 1 N1`
+- `erdos number-theory atom 1 N1.G1.A1`
 - `erdos number-theory status 2 --json`
 
 Design rule:

package/src/cli/index.js

@@ -4,6 +4,7 @@ import { runCheckpointsCommand } from '../commands/checkpoints.js';
 import { runClusterCommand } from '../commands/cluster.js';
 import { runContinuationCommand } from '../commands/continuation.js';
 import { runDossierCommand } from '../commands/dossier.js';
+import { runGraphTheoryCommand } from '../commands/graph-theory.js';
 import { runMaintainerCommand } from '../commands/maintainer.js';
 import { runNumberTheoryCommand } from '../commands/number-theory.js';
 import { runOrpCommand } from '../commands/orp.js';
@@ -26,15 +27,22 @@ function printUsage() {
   console.log('  erdos problem use <id>');
   console.log('  erdos problem current');
   console.log('  erdos problem artifacts [<id>] [--json]');
-  console.log('  erdos cluster list');
-  console.log('  erdos cluster show <name>');
-  console.log('  erdos archive show <id>');
-  console.log('  erdos archive scaffold <id>');
+  console.log('  erdos cluster list [--json]');
+  console.log('  erdos cluster show <name> [--json]');
+  console.log('  erdos archive show <id> [--json]');
+  console.log('  erdos archive scaffold <id> [--json]');
+  console.log('  erdos graph-theory status [<id>] [--json]');
+  console.log('  erdos graph-theory frontier [<id>] [--json]');
+  console.log('  erdos graph-theory routes [<id>] [--json]');
+  console.log('  erdos graph-theory tickets [<id>] [--json]');
   console.log('  erdos number-theory status [<id>] [--json]');
   console.log('  erdos number-theory frontier [<id>] [--json]');
   console.log('  erdos number-theory routes [<id>] [--json]');
   console.log('  erdos number-theory tickets [<id>] [--json]');
-  console.log('  erdos workspace show');
+  console.log('  erdos number-theory route <problem-id> <route-id> [--json]');
+  console.log('  erdos number-theory ticket <problem-id> <ticket-id> [--json]');
+  console.log('  erdos number-theory atom <problem-id> <atom-id> [--json]');
+  console.log('  erdos workspace show [--json]');
   console.log('  erdos orp show [--json]');
   console.log('  erdos orp sync [--json]');
   console.log('  erdos state sync [--json]');
@@ -82,6 +90,8 @@ if (!command || command === 'help' || command === '--help') {
   exitCode = runClusterCommand(rest);
 } else if (command === 'archive') {
   exitCode = runArchiveCommand(rest);
+} else if (command === 'graph-theory') {
+  exitCode = runGraphTheoryCommand(rest);
 } else if (command === 'number-theory') {
   exitCode = runNumberTheoryCommand(rest);
 } else if (command === 'workspace') {

package/src/commands/archive.js

@@ -1,7 +1,8 @@
 import { getArchiveView, scaffoldArchive } from '../runtime/archive.js';
 
 export function runArchiveCommand(args) {
-  const [subcommand, problemId] = args;
+  const [subcommand, problemId, ...rest] = args;
+  const asJson = rest.includes('--json');
 
   if (!subcommand || subcommand === 'help' || subcommand === '--help') {
     console.log('Usage:');
@@ -21,6 +22,10 @@ export function runArchiveCommand(args) {
       console.error(`Unknown problem: ${problemId}`);
       return 1;
     }
+    if (asJson) {
+      console.log(JSON.stringify(archive, null, 2));
+      return 0;
+    }
     console.log(`${archive.displayName} archive view`);
     console.log(`Title: ${archive.title}`);
     console.log(`Solved: ${archive.solved ? 'yes' : 'no'}`);
@@ -32,6 +37,10 @@ export function runArchiveCommand(args) {
   if (subcommand === 'scaffold') {
     try {
       const result = scaffoldArchive(problemId);
+      if (asJson) {
+        console.log(JSON.stringify(result, null, 2));
+        return 0;
+      }
       console.log(`Archive scaffold created: ${result.archiveDir}`);
       console.log(`Archive mode: ${result.payload.archiveMode}`);
       return 0;

package/src/commands/cluster.js

@@ -14,11 +14,16 @@ function printCluster(cluster) {
     console.log('  Open starter cockpit: 1');
     console.log('  Counterexample/archive cockpit: 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');
   }
 }
 
 export function runClusterCommand(args) {
-  const [subcommand, value] = args;
+  const [subcommand, value, ...rest] = args;
+  const asJson = [value, ...rest].includes('--json');
 
   if (!subcommand || subcommand === 'help' || subcommand === '--help') {
     console.log('Usage:');
@@ -28,6 +33,10 @@ export function runClusterCommand(args) {
   }
 
   if (subcommand === 'list') {
+    if (asJson) {
+      console.log(JSON.stringify(listClusters(), null, 2));
+      return 0;
+    }
     console.log('Clusters:');
     for (const cluster of listClusters()) {
       console.log(`- ${cluster.name}: ${cluster.problems.length} problems, ${cluster.deepHarnessProblems.length} deep-harness`);
@@ -51,6 +60,11 @@ export function runClusterCommand(args) {
     return 1;
   }
 
+  if (asJson) {
+    console.log(JSON.stringify(cluster, null, 2));
+    return 0;
+  }
+
   printCluster(cluster);
   return 0;
 }