erdos-problems 0.1.13 → 0.2.1

package/README.md

@@ -33,6 +33,10 @@ Seeded problems:
 Native dossier count:
 - `18`
 
+Pack coverage:
+- sunflower pack: `4`
+- number-theory starter cockpit: `2`
+
 ## First-run flow
 
 ```bash
@@ -41,9 +45,11 @@ erdos bootstrap problem 857
 erdos problem artifacts 857 --json
 erdos sunflower status 857
 erdos sunflower board 857
+erdos sunflower frontier 857
 erdos sunflower routes 857
 erdos sunflower tickets 857
 erdos dossier show 857
+erdos number-theory status 1
 ```
 
 For an unseeded problem, the one-step self-seeding flow is now:
@@ -78,6 +84,12 @@ What `seed` does:
   - `PUBLIC_STATUS_REVIEW.md`
   - `AGENT_WEBSEARCH_BRIEF.md`
 
+The seeded workspace also now has a clearer runtime shape:
+- `.erdos/runs/`
+- `.erdos/archives/`
+- `.erdos/checkpoints/`
+- `.erdos/orp/`
+
 ## Pull lanes
 
 For any problem number in the upstream snapshot, you can create a workspace bundle even if the problem is not yet seeded locally:
@@ -86,6 +98,8 @@ For any problem number in the upstream snapshot, you can create a workspace bund
 erdos pull problem 857
 erdos pull artifacts 857
 erdos pull literature 857
+erdos pull literature 857 --json
+erdos pull literature 857 --include-crossref --include-openalex
 erdos pull problem 999 --include-site --include-public-search
 erdos pull problem 999 --refresh-upstream
 ```
@@ -103,6 +117,13 @@ What the pull lanes do:
   - `PUBLIC_STATUS_REVIEW.md`
   - `PUBLIC_STATUS_REVIEW.json`
   - `AGENT_WEBSEARCH_BRIEF.md`
+- when `--include-crossref` is used, the literature lane also includes:
+  - `CROSSREF_RESULTS.json`
+  - `CROSSREF_RESULTS.md`
+- when `--include-openalex` is used, the literature lane also includes:
+  - `OPENALEX_RESULTS.json`
+  - `OPENALEX_RESULTS.md`
+- when `--json` is used, the pull command emits an agent-friendly machine summary instead of prose
 
 ## Maintainer seeding
 
@@ -112,6 +133,8 @@ To turn a pulled bundle into a new canonical dossier in the repo:
 erdos maintainer seed problem 25 \
   --from-pull .erdos/pulls/25 \
   --cluster number-theory
+erdos maintainer review problem 25 \
+  --from-pull .erdos/pulls/25
 ```
 
 What maintainer seeding does:
@@ -131,6 +154,7 @@ What maintainer seeding does:
   - `PUBLIC_STATUS_REVIEW.md`
   - `AGENT_WEBSEARCH_BRIEF.md`
 - preserves upstream/site provenance in the local record
+- `erdos maintainer review problem <id>` also creates a review checklist before promotion
 
 ## Sunflower pack
 
@@ -141,10 +165,10 @@ The first deep pack is the sunflower quartet:
 - `856`: harmonic-density LCM analogue
 
 Sunflower problems now ship pack packets:
-- `20`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
-- `857`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
-- `536`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
-- `856`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
+- `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`
+- `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`
+- `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`
+- `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`
 
 Useful sunflower commands:
 
@@ -155,8 +179,13 @@ erdos sunflower status 536
 erdos sunflower board 536
 erdos sunflower ready 857
 erdos sunflower ladder 20
+erdos sunflower frontier 857
 erdos sunflower routes 857
 erdos sunflower tickets 857
+erdos sunflower route 857 anchored_selector_linearization
+erdos sunflower ticket 20 T6
+erdos sunflower atom 857 T10.G3.A2
+erdos sunflower compute run 857
 erdos sunflower board 857
 erdos sunflower status 857 --json
 ```
@@ -194,6 +223,67 @@ erdos sunflower status 857 --json
 - the active ticket, leaf theorem, and gate/atom counts
 - which tickets are closed versus still honest live pressure
 
+`erdos sunflower frontier` surfaces:
+- the compressed cockpit view:
+  - active route
+  - active ticket
+  - first ready atom
+  - checkpoint focus
+  - compute posture
+
+`erdos sunflower route|ticket|atom` surfaces:
+- the deeper public drill-down packet for a specific route, ticket, or atom
+- live summary, blocker, next move, and source paths when available
+
+`erdos sunflower compute run` surfaces:
+- a governed local-scout run bundle only when the packaged compute posture admits a local scout
+- writes reproducible run artifacts into `.erdos/runs/<run-id>/`
+- records governance and ORP-facing packet context
+- does not silently escalate into paid or unbounded compute
+
+## Number-theory starter cockpit
+
+The first non-sunflower pack is now a light but real cockpit for two number-theory problems:
+- `1`: open starter cockpit around a distinct-subset-sum lower-bound route
+- `2`: archive cockpit around a disproved / counterexample-facing record
+
+Useful number-theory commands:
+
+```bash
+erdos number-theory status 1
+erdos number-theory frontier 1
+erdos number-theory routes 1
+erdos number-theory tickets 1
+erdos number-theory status 2 --json
+```
+
+The number-theory pack is intentionally lighter than sunflower:
+- no mirrored theorem board yet
+- explicit route/frontier/ticket packet layer
+- honest archive posture for disproved problems
+
+## Archive mode
+
+Solved problems can now be treated as method exemplars instead of dead entries.
+
+```bash
+erdos problem show 1008
+erdos archive show 1008
+erdos archive scaffold 1008
+erdos number-theory status 1
+erdos number-theory frontier 1
+erdos number-theory routes 1
+erdos number-theory tickets 1
+```
+
+Archive scaffolds land in:
+- `.erdos/archives/<id>/`
+
+and include:
+- `ARCHIVE.json`
+- `ARCHIVE_SUMMARY.md`
+- `METHOD_PACKET.md`
+
 ## ORP
 
 `erdos-problems` now ships a bundled Open Research Protocol kit:
@@ -229,6 +319,7 @@ erdos problem artifacts 857
 erdos problem artifacts 857 --json
 erdos cluster list
 erdos cluster show sunflower
+erdos cluster show number-theory
 erdos workspace show
 erdos orp show
 erdos orp sync
@@ -236,13 +327,24 @@ erdos sunflower status 857
 erdos sunflower board 857
 erdos sunflower ready 857
 erdos sunflower ladder 857
+erdos sunflower frontier 857
 erdos sunflower routes 857
 erdos sunflower tickets 857
+erdos sunflower route 857 anchored_selector_linearization
+erdos sunflower ticket 857 T10
+erdos sunflower atom 857 T10.G3.A2
+erdos sunflower compute run 857
+erdos number-theory status 1
+erdos number-theory frontier 1
+erdos number-theory routes 1
+erdos number-theory tickets 1
 erdos sunflower status --json
 erdos dossier show
 erdos upstream show
 erdos upstream sync
 erdos upstream diff
+erdos upstream drift
+erdos upstream drift 857 --json
 erdos scaffold problem 857
 erdos bootstrap problem 857
 erdos bootstrap problem 857 --sync-upstream
@@ -250,7 +352,12 @@ erdos seed problem 25 --cluster number-theory
 erdos pull problem 857
 erdos pull artifacts 857
 erdos pull literature 857
+erdos pull literature 857 --json
+erdos pull literature 857 --include-crossref --include-openalex
+erdos maintainer review problem 25 --from-pull .erdos/pulls/25
 erdos maintainer seed problem 25 --from-pull .erdos/pulls/25 --cluster number-theory
+erdos archive show 1008
+erdos archive scaffold 1008
 ```
 
 ## Canonical sources
@@ -293,6 +400,12 @@ For sunflower problems, the CLI also surfaces pack-specific artifacts:
 - compute packets under `packs/sunflower/compute/<id>/` when available
 - compute-governance evaluation under `breakthroughs`, surfaced through `erdos sunflower status`
 
+For number-theory starter-cockpit problems, the CLI now also surfaces:
+- pack README context
+- per-problem context files under `packs/number-theory/problems/<id>/`
+- route packets, frontier notes, route histories, checkpoint/report templates, and ops-detail packets
+- archive posture for disproved problems through `erdos number-theory status`
+
 ## Notes
 
 - `erdos-problems` is the canonical npm package name.

package/docs/RESEARCH_LOOP.md

@@ -11,6 +11,8 @@ Workspace runtime files live under `.erdos/`:
 - `QUESTION-LEDGER.md`
 - `checkpoints/CHECKPOINTS.md`
 - `checkpoints/CHECKPOINTS.json`
+- `runs/<run-id>/`
+- `archives/<id>/`
 - `orp/PROTOCOL.md`
 - `orp/AGENT_INTEGRATION.md`
 - `orp/templates/`
@@ -28,7 +30,8 @@ Workspace runtime files live under `.erdos/`:
 7. Pull or scaffold artifacts.
 8. Review public status and agent websearch brief if the problem was freshly seeded.
 9. Work the active route.
-10. Sync checkpoints again at honest boundaries.
+10. If the pack admits a local scout, run it intentionally and checkpoint the artifact.
+11. Sync checkpoints again at honest boundaries.
 
 ## Commands
 
@@ -72,10 +75,26 @@ For sunflower compute lanes, ORP now sits above `breakthroughs`:
 - `erdos sunflower board <id>` exposes the packaged atomic or bridge board for the active sunflower problem
 - `erdos sunflower ready <id>` exposes the dependency-satisfied ready queue for the packaged board
 - `erdos sunflower ladder <id>` exposes the first-principles ladder for the packaged board
+- `erdos sunflower frontier <id>` exposes the compressed cockpit view for the active board
 - `erdos sunflower routes <id>` exposes the public route table for the packaged board
 - `erdos sunflower tickets <id>` exposes the ticket table for the packaged board
+- `erdos sunflower route <id> <route-id>` exposes the deeper public route packet
+- `erdos sunflower ticket <id> <ticket-id>` exposes the deeper public ticket packet
+- `erdos sunflower atom <id> <atom-id>` exposes the deeper public atom packet
+- `erdos sunflower compute run <id>` writes a governed local-scout bundle when the packet admits it
 - the CLI surfaces the selected rung, dispatch action, and the reason compute is admissible
-- this is compute governance and traceability, not an automatic compute launch
+- this is compute governance and traceability, not an automatic paid or unbounded compute launch
+
+For number-theory starter-cockpit problems:
+- `erdos number-theory status <id>` exposes the current route/frontier posture
+- `erdos number-theory frontier <id>` compresses the honest next move
+- `erdos number-theory routes <id>` exposes the small route table
+- `erdos number-theory tickets <id>` exposes the current ticket/archive packet
+- this is deliberately lighter than the sunflower pack and should stay honest about that
+
+For solved problems:
+- `erdos archive show <id>` exposes archival posture
+- `erdos archive scaffold <id>` creates a method-exemplar bundle under `.erdos/archives/<id>/`
 
 ## Status ladder
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "erdos-problems",
-  "version": "0.1.13",
+  "version": "0.2.1",
   "description": "CLI atlas and staged research harness for Paul Erdos problems.",
   "type": "module",
   "bin": {

package/packs/number-theory/README.md

@@ -0,0 +1,17 @@
+# Number Theory Pack
+
+Light starter cockpit for number-theory problems in `erdos-problems`.
+
+Current seeded cockpit problems:
+- `1`: open starter cockpit around a distinct-subset-sum lower-bound route
+- `2`: counterexample/archive cockpit for a disproved covering-systems problem
+
+Useful commands:
+- `erdos number-theory status 1`
+- `erdos number-theory frontier 1`
+- `erdos number-theory routes 1`
+- `erdos number-theory tickets 1`
+- `erdos number-theory status 2 --json`
+
+Design rule:
+- keep this pack lighter than sunflower until a deeper theorem-board frontier is honestly earned

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

@@ -0,0 +1,7 @@
+# Problem 1 Checkpoint Template
+
+- Active route:
+- Exact lower-bound reduction touched:
+- New reference/evidence frozen:
+- Public-status drift checked:
+- Next honest move:

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

@@ -0,0 +1,8 @@
+# Problem 1 Number Theory Pack Context
+
+- Family role: additive_number_theory_seed
+- Harness profile: dossier_seed_pack
+- Active route posture: additive_structure_seed
+
+This problem is intentionally lighter than the sunflower pack.
+The point is to give number theory a clean pack home before we move any deep gated flow over.

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

@@ -0,0 +1,8 @@
+# Problem 1 Frontier Note
+
+This is a starter cockpit, not a deep theorem board.
+
+The honest live route is the distinct-subset-sum lower-bound route:
+- keep the problem statement exact
+- keep the additive lower-bound framing explicit
+- do not widen this into a generic additive-combinatorics program

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

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

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

@@ -0,0 +1,7 @@
+# Problem 1 Report Template
+
+- Route:
+- What changed:
+- What remains open:
+- Verification hook:
+- Archive or promote:

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

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

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

@@ -0,0 +1,13 @@
+route_packet_id: nt1_distinct_subset_sum_lower_bound_v1
+route_id: distinct_subset_sum_lower_bound
+frontier_claim: Preserve the exponential-growth lower-bound route for distinct subset sums and keep the first honest reduction explicit.
+theorem_module: ""
+checkpoint_packet: CHECKPOINT_TEMPLATE.md
+report_packet: REPORT_TEMPLATE.md
+ready_prompts:
+  - Which exact lower-bound reduction should be frozen first for the distinct-subset-sum route?
+  - Which reference or historical bound is still missing from the canonical dossier?
+verification_hook:
+  - erdos number-theory status 1
+  - erdos number-theory routes 1
+  - erdos problem artifacts 1 --json

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

@@ -0,0 +1,25 @@
+problem_id: "1"
+family_role: additive_number_theory_seed
+harness_profile: starter_cockpit
+default_active_route: distinct_subset_sum_lower_bound
+bootstrap_focus: Freeze the exact problem statement, the local dossier, and the first honest lower-bound route for distinct subset sums.
+route_story: This problem now has a starter cockpit whose job is to keep the lower-bound route explicit without pretending we already have a deep theorem engine.
+frontier_label: distinct_subset_sum_lower_bound
+frontier_detail: Keep the problem anchored to the binary-growth lower-bound route and freeze the exact first reduction before widening claims.
+checkpoint_focus: Preserve provenance, the exact lower-bound route, and the open-problem boundary in every checkpoint.
+next_honest_move: Freeze the first additive lower-bound route note and tighten the evidence stack around the distinct-subset-sum hypothesis.
+related_core_problems: []
+literature_focus:
+  - additive number theory
+  - extremal sets
+artifact_focus:
+  - STATEMENT.md
+  - REFERENCES.md
+  - EVIDENCE.md
+question_ledger:
+  open_questions:
+    - What is the first exact lower-bound reduction worth freezing for the distinct-subset-sum route?
+  active_route_notes:
+    - Keep the active route tied to distinct subset sums and exponential-growth pressure, not generic additive chatter.
+  route_breakthroughs: []
+  problem_solved: []

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

@@ -0,0 +1,7 @@
+# Problem 2 Checkpoint Template
+
+- Archive route:
+- Disproval/counterexample reference touched:
+- Public wording checked:
+- Method lesson captured:
+- Next honest move:

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

@@ -0,0 +1,8 @@
+# Problem 2 Number Theory Pack Context
+
+- Family role: additive_number_theory_seed
+- Harness profile: dossier_seed_pack
+- Active route posture: additive_structure_seed
+
+This is a light pack context packet.
+It exists so the next family pack can grow inside the same architecture without forcing sunflower-style machinery prematurely.

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

@@ -0,0 +1,8 @@
+# Problem 2 Archive Note
+
+This is not a live open-problem frontier.
+
+The honest posture is:
+- preserve the disproval cleanly
+- keep the references synchronized
+- package the problem as a counterexample/method archive instead of a live cockpit

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

@@ -0,0 +1,25 @@
+packet_id: nt2_ops_details_v1
+summary: Archive cockpit packet for the disproved covering-systems problem.
+routes:
+  - route_id: counterexample_archive
+    title: Counterexample Archive
+    status: archival
+    summary: Keep the problem packaged as a disproval archive rather than a live open frontier.
+    why_now: This is the honest public posture for a disproved problem.
+    next_move: Freeze the strongest disproval/counterexample references in the archive packet.
+tickets:
+  - ticket_id: N2
+    title: Tighten the disproval archive packet
+    route_id: counterexample_archive
+    status: active
+    summary: Package the disproval cleanly enough that future agents cannot mistake this for an open problem.
+    current_blocker: The archive packet still needs a sharper reference-centered summary.
+    next_move: Close `N2.G1.A1`.
+atoms:
+  - atom_id: N2.G1.A1
+    title: Freeze the primary disproval reference and method note
+    route_id: counterexample_archive
+    ticket_id: N2
+    status: ready
+    summary: This is the smallest archive improvement that meaningfully clarifies the public dossier.
+    next_move: Record the best disproval reference and checkpoint the archive packet.

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

@@ -0,0 +1,7 @@
+# Problem 2 Report Template
+
+- Archive route:
+- What was clarified:
+- Which disproval/counterexample artifact was frozen:
+- Verification hook:
+- Next archive action:

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

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

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

@@ -0,0 +1,13 @@
+route_packet_id: nt2_counterexample_archive_v1
+route_id: counterexample_archive
+frontier_claim: Preserve the disproval and counterexample-facing references cleanly so the problem remains useful as a method exemplar.
+theorem_module: ""
+checkpoint_packet: CHECKPOINT_TEMPLATE.md
+report_packet: REPORT_TEMPLATE.md
+ready_prompts:
+  - Which exact disproval reference should be frozen first in the archive packet?
+  - Which method lesson from the counterexample should be made explicit for future number-theory dossiers?
+verification_hook:
+  - erdos number-theory status 2
+  - erdos number-theory routes 2
+  - erdos problem show 2

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

@@ -0,0 +1,25 @@
+problem_id: "2"
+family_role: covering_systems_counterexample_archive
+harness_profile: archive_cockpit
+default_active_route: counterexample_archive
+bootstrap_focus: Freeze the exact disproval record, the dossier provenance, and the counterexample-facing archive packet.
+route_story: This problem is not a live open frontier; the honest public job is to preserve the disproval and keep it usable as a method/counterexample exemplar.
+frontier_label: counterexample_archive
+frontier_detail: Preserve the counterexample/archive posture cleanly and avoid drifting back into open-problem language.
+checkpoint_focus: Keep the disproval record, references, and archive packet synchronized.
+next_honest_move: Tighten the counterexample archive note and make the public references impossible to misread as an open frontier.
+related_core_problems: []
+literature_focus:
+  - additive number theory
+  - extremal sequences
+artifact_focus:
+  - STATEMENT.md
+  - REFERENCES.md
+  - EVIDENCE.md
+question_ledger:
+  open_questions:
+    - Which exact disproval or counterexample references should be frozen first in the archive packet?
+  active_route_notes:
+    - Treat this as an archive cockpit, not a live open-problem route.
+  route_breakthroughs: []
+  problem_solved: []

package/packs/sunflower/README.md

@@ -15,9 +15,22 @@ Profiles:
 - `856`: dossier bridge, harmonic-density LCM analogue
 
 Deep route packets:
-- `20` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
-- `857` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
+- `20` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `FRONTIER_NOTE.md`, `ROUTE_HISTORY.md`, `CHECKPOINT_TEMPLATE.md`, `REPORT_TEMPLATE.md`, `OPS_DETAILS.yaml`
+- `857` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `FRONTIER_NOTE.md`, `ROUTE_HISTORY.md`, `CHECKPOINT_TEMPLATE.md`, `REPORT_TEMPLATE.md`, `OPS_DETAILS.yaml`
 
 Bridge packets:
-- `536` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
-- `856` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
+- `536` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `FRONTIER_NOTE.md`, `ROUTE_HISTORY.md`, `CHECKPOINT_TEMPLATE.md`, `REPORT_TEMPLATE.md`, `OPS_DETAILS.yaml`
+- `856` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `FRONTIER_NOTE.md`, `ROUTE_HISTORY.md`, `CHECKPOINT_TEMPLATE.md`, `REPORT_TEMPLATE.md`, `OPS_DETAILS.yaml`
+
+Public cockpit commands:
+- `erdos sunflower status <id>`
+- `erdos sunflower board <id>`
+- `erdos sunflower ready <id>`
+- `erdos sunflower ladder <id>`
+- `erdos sunflower frontier <id>`
+- `erdos sunflower routes <id>`
+- `erdos sunflower tickets <id>`
+- `erdos sunflower route <id> <route-id>`
+- `erdos sunflower ticket <id> <ticket-id>`
+- `erdos sunflower atom <id> <atom-id>`
+- `erdos sunflower compute run <id>`

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

@@ -0,0 +1,29 @@
+# Problem 20 Checkpoint Template
+
+## Status Ladder
+
+- Open problem:
+- Active route:
+- Route breakthrough:
+- Problem solved:
+
+## Board posture
+
+- Active ticket:
+- Ready atoms:
+- Ladder summary:
+
+## Support lane
+
+- What remains open in the support lane:
+- What was only historical support:
+
+## Verification
+
+- Claim level:
+- Verification hook:
+- Verification record:
+
+## Next move
+
+- Next honest move:

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

@@ -0,0 +1,13 @@
+# Problem 20 Frontier Note
+
+- Open problem: yes
+- Active route: `uniform_k3_frontier`
+- Active ticket: `T6`
+- Ready atoms: `0`
+- Route breakthrough: yes
+- Problem solved: no
+
+Current honest framing:
+- the mirrored final `k=3` route is closed in the public board
+- the support lane remains open
+- there is no dependency-satisfied ready atom right now, so the next move is checkpoint/report discipline rather than forcing fake atomic urgency

package/packs/sunflower/problems/20/OPS_DETAILS.yaml

@@ -0,0 +1,44 @@
+packet_id: strong20_ops_details_v1
+summary: Public drill-down packet for the strong sunflower k=3 frontier.
+routes:
+  - route_id: uniform_k3_frontier
+    title: Uniform K=3 Frontier
+    status: active
+    theorem_module: sunflower-coda/repo/sunflower_lean/SunflowerLean/ErdosProblem20.lean
+    summary: Keep the public strong-sunflower pack aligned with the closed k=3 route and the still-open support lane.
+    why_now: This is the honest public route posture after the mirrored closure board.
+    next_move: Work the support lane carefully and checkpoint any real change before widening claims.
+    ticket_ids: [T6]
+    source_paths:
+      - packs/sunflower/problems/20/ATOMIC_BOARD.yaml
+      - packs/sunflower/problems/20/FRONTIER_NOTE.md
+  - route_id: uniform_prize_final_k3
+    title: Uniform Prize Final K=3
+    status: strict_closed
+    theorem_module: sunflower-coda/repo/sunflower_lean/SunflowerLean/ErdosProblem20.lean
+    summary: Closed mirrored route for the public k=3 lane.
+    why_now: It is important support context, but it is not the current support-lane frontier.
+    next_move: Treat it as closed historical support.
+    ticket_ids: [T5]
+tickets:
+  - ticket_id: T6
+    title: "Support Lane T6: UniformK3From7 Base/Step Witness Construction"
+    route_id: uniform_k3_frontier
+    route_leaf: UniformK3From7BaseRangeHyp
+    status: active
+    summary: The support lane remains open even though the final mirrored k=3 route is closed.
+    gate_story: Gate counts are closed but there is no currently dependency-satisfied ready atom.
+    current_blocker: The public pack does not yet have a genuine next atom; the correct move is checkpoint/report discipline and support-lane clarification.
+    next_move: Preserve the support-lane context and avoid inventing urgency that the board does not justify.
+    atom_ids: []
+  - ticket_id: T5
+    title: "Closure Lane T5: UniformK3EnvelopeFrom7WithPolySlack"
+    route_id: uniform_prize_final_k3
+    route_leaf: UniformK3EnvelopeFrom7WithPolySlack
+    status: closed
+    summary: Closed mirrored route ticket for the public k=3 closure lane.
+    gate_story: This ticket is historical support and should remain visible as such.
+    current_blocker: none
+    next_move: Keep as closure context only.
+    atom_ids: []
+atoms: []

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

@@ -0,0 +1,23 @@
+# Problem 20 Report Template
+
+## Summary
+
+- Route worked:
+- Ticket worked:
+- Why the support lane matters:
+
+## Artifacts
+
+- Mirrored board artifacts:
+- Checkpoint updates:
+- Any compute/scout artifacts:
+
+## Frontier shift
+
+- Did the ready queue change?
+- Did the support lane meaningfully tighten?
+
+## Honesty check
+
+- What remains open in problem 20?
+- What closed route should not be mistaken for a full solution?