erdos-problems 0.1.12 → 0.2.0

package/README.md

@@ -33,6 +33,10 @@ Seeded problems:
 Native dossier count:
 - `18`
 
+Pack coverage:
+- sunflower pack: `4`
+- number-theory starter pack: `2`
+
 ## First-run flow
 
 ```bash
@@ -41,6 +45,9 @@ 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
 ```
 
@@ -76,6 +83,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:
@@ -84,6 +97,7 @@ 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 --include-crossref --include-openalex
 erdos pull problem 999 --include-site --include-public-search
 erdos pull problem 999 --refresh-upstream
 ```
@@ -101,6 +115,12 @@ 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`
 
 ## Maintainer seeding
 
@@ -110,6 +130,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:
@@ -129,6 +151,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
 
@@ -139,10 +162,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`, `OPS_DETAILS.yaml`
+- `856`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`, `OPS_DETAILS.yaml`
 
 Useful sunflower commands:
 
@@ -153,6 +176,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
 ```
@@ -180,6 +210,52 @@ erdos sunflower status 857 --json
 `erdos sunflower ladder` surfaces:
 - the first-principles ladder for the active sunflower board
 
+`erdos sunflower routes` surfaces:
+- the strategic route table for the active sunflower board
+- loose and strict progress for every publicized route
+- which route is the currently active frontier
+
+`erdos sunflower tickets` surfaces:
+- the operational ticket table for the active sunflower board
+- 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
+
+## 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
+```
+
+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:
@@ -222,11 +298,20 @@ 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 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
@@ -234,7 +319,11 @@ erdos seed problem 25 --cluster number-theory
 erdos pull problem 857
 erdos pull artifacts 857
 erdos pull literature 857
+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

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,8 +75,19 @@ 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 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.12",
+  "version": "0.2.0",
   "description": "CLI atlas and staged research harness for Paul Erdos problems.",
   "type": "module",
   "bin": {

package/packs/number-theory/README.md

@@ -0,0 +1,13 @@
+# Number Theory Pack
+
+This is the first non-sunflower family-pack scaffold in `erdos-problems`.
+
+Current posture:
+- dossier-first
+- route-light
+- no deep board/compute loop yet
+
+Why it exists:
+- keep a clean home for reusable number-theory context
+- prove the core/pack split scales beyond sunflower
+- let selected number-theory problems accumulate pack context before they earn deeper gated flows

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/context.yaml

@@ -0,0 +1,25 @@
+problem_id: "1"
+family_role: additive_number_theory_seed
+harness_profile: dossier_seed_pack
+default_active_route: additive_structure_seed
+bootstrap_focus: Freeze the exact problem statement, the local dossier, and the first honest additive-number-theory route sketch.
+route_story: This problem currently lives in dossier-first mode inside the number-theory pack.
+frontier_label: dossier_seed_frontier
+frontier_detail: Tighten the statement, references, and first route sketch before pretending there is a deeper frontier engine here.
+checkpoint_focus: Preserve provenance and route honesty while the pack remains dossier-first.
+next_honest_move: Seed the first real route note and keep the public-status review current.
+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 honest additive-number-theory route worth freezing for problem 1?
+  active_route_notes:
+    - Keep this problem dossier-first until a real pack-specific route is earned.
+  route_breakthroughs: []
+  problem_solved: []

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/context.yaml

@@ -0,0 +1,25 @@
+problem_id: "2"
+family_role: additive_number_theory_seed
+harness_profile: dossier_seed_pack
+default_active_route: additive_structure_seed
+bootstrap_focus: Freeze the exact problem statement, local dossier, and first honest additive route sketch.
+route_story: This problem currently lives in dossier-first mode inside the number-theory pack.
+frontier_label: dossier_seed_frontier
+frontier_detail: Keep this number-theory problem in a disciplined dossier-first workflow until a deeper route is honestly earned.
+checkpoint_focus: Preserve provenance and route honesty while the pack remains dossier-first.
+next_honest_move: Seed the first route note and keep the public-status review current.
+related_core_problems: []
+literature_focus:
+  - additive number theory
+  - extremal sequences
+artifact_focus:
+  - STATEMENT.md
+  - REFERENCES.md
+  - EVIDENCE.md
+question_ledger:
+  open_questions:
+    - What is the first honest additive-number-theory route worth freezing for problem 2?
+  active_route_notes:
+    - Keep this problem dossier-first until a real pack-specific route is earned.
+  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`, `OPS_DETAILS.yaml`
+- `856` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.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?

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

@@ -0,0 +1,18 @@
+# Problem 20 Route History
+
+## Closed public route layers
+
+- `uniform_prize`
+- `uniform_prize_final_k3`
+
+## Current honest public route
+
+- `uniform_k3_frontier`
+
+## Residual route context
+
+- `uniform_prize_full_all_k`
+
+Why it matters:
+- the public pack should keep the closed `k=3` route visible
+- but it should also keep the remaining support-lane obligations visible without pretending there is a ready atom when there is not

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

@@ -0,0 +1,39 @@
+packet_id: sunflower536_ops_details_v1
+summary: Public bridge-board drill-down packet for problem 536.
+routes:
+  - route_id: natural_density_lcm_bridge
+    title: Natural-Density LCM Bridge
+    status: active
+    theorem_module: ""
+    summary: Freeze public status, exact analogue wording, and the bridge back to 857.
+    why_now: This is the active public bridge route for the natural-density analogue.
+    next_move: Close the public-status review atom before widening the analogue story.
+    ticket_ids: [T1, T2, T3]
+tickets:
+  - ticket_id: T1
+    title: Dossier Source Lock
+    route_id: natural_density_lcm_bridge
+    route_leaf: public_status_and_statement_lock
+    status: active
+    summary: Freeze the public open-state and exact statement wording.
+    gate_story: This is where the bridge board becomes trustworthy.
+    current_blocker: The public-status review still needs to be frozen.
+    next_move: Close `T1.G1.A3`.
+    atom_ids: [T1.G1.A3]
+atoms:
+  - atom_id: T1.G1.A3
+    title: Run the public-status review and freeze the exact open-state snapshot for problem 536
+    ticket_id: T1
+    route_id: natural_density_lcm_bridge
+    gate_id: T1.G1
+    tier: P0-SpecLock
+    kind: review
+    status: ready
+    summary: This is the smallest honest public move for 536.
+    why_now: The bridge board already marks it ready.
+    next_move: Freeze the public-status artifacts and checkpoint the bridge state.
+    verification_hook:
+      - erdos sunflower routes 536
+      - erdos sunflower tickets 536
+    dependencies:
+      - public-status review bundle

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

@@ -0,0 +1,39 @@
+packet_id: sunflower856_ops_details_v1
+summary: Public bridge-board drill-down packet for problem 856.
+routes:
+  - route_id: harmonic_density_lcm_bridge
+    title: Harmonic-Density LCM Bridge
+    status: active
+    theorem_module: ""
+    summary: Freeze public status, density-language wording, and the exponent-transfer bridge back to 857.
+    why_now: This is the active public bridge route for the harmonic-density analogue.
+    next_move: Close the public-status review atom before widening the exponent-transfer story.
+    ticket_ids: [T1, T2, T3]
+tickets:
+  - ticket_id: T1
+    title: Dossier Source Lock
+    route_id: harmonic_density_lcm_bridge
+    route_leaf: public_status_and_density_lock
+    status: active
+    summary: Freeze the public open-state and the exact density-language statement.
+    gate_story: This is where the bridge board becomes trustworthy.
+    current_blocker: The public-status review still needs to be frozen.
+    next_move: Close `T1.G1.A3`.
+    atom_ids: [T1.G1.A3]
+atoms:
+  - atom_id: T1.G1.A3
+    title: Run the public-status review and freeze the exact open-state snapshot for problem 856
+    ticket_id: T1
+    route_id: harmonic_density_lcm_bridge
+    gate_id: T1.G1
+    tier: P0-SpecLock
+    kind: review
+    status: ready
+    summary: This is the smallest honest public move for 856.
+    why_now: The bridge board already marks it ready.
+    next_move: Freeze the public-status artifacts and checkpoint the bridge state.
+    verification_hook:
+      - erdos sunflower routes 856
+      - erdos sunflower tickets 856
+    dependencies:
+      - public-status review bundle

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

@@ -0,0 +1,32 @@
+# Problem 857 Checkpoint Template
+
+## Status Ladder
+
+- Open problem:
+- Active route:
+- Route breakthrough:
+- Problem solved:
+
+## Active ticket
+
+- Ticket id:
+- Leaf theorem:
+- Gate progress:
+- Atom progress:
+
+## Frontier
+
+- First ready atom:
+- Why this atom is honest:
+- What changed since the last checkpoint:
+
+## Verification
+
+- Exact / Verified / Heuristic / Conjecture:
+- Verification hook:
+- Verification record:
+
+## Next move
+
+- Next honest move:
+- What remains blocked:

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

@@ -0,0 +1,18 @@
+# Problem 857 Frontier Note
+
+- Open problem: yes
+- Active route: `anchored_selector_linearization`
+- Active ticket: `T10`
+- First ready atom: `T10.G3.A2`
+- Route breakthrough: yes
+- Problem solved: no
+
+Current honest framing:
+- the public weak-sunflower pack is no longer bottlenecked on generic counting closure
+- the live public frontier is the anchored-selector linearization seam
+- the next honest move is to promote the helper/theorem stack into `anchored_selector_linearization_realized`
+
+Boundary:
+- historical tickets stay visible for context
+- they do not outrank the active `T10` frontier
+- no route breakthrough should be widened into a solved-problem claim