erdos-problems 0.1.9 → 0.1.11

package/README.md

@@ -22,6 +22,7 @@ Official binary:
 - workspace `.erdos/` state for active-problem selection, upstream refreshes, scaffolds, and pull bundles
 - sunflower cluster as the first deep harness pack
 - quartet-aware sunflower context for `20`, `536`, `856`, and `857`
+- packaged atomic/bridge board packets for the full sunflower quartet
 - packaged compute-lane metadata for deep sunflower problems, surfaced directly in the CLI
 - seeded atlas now includes open and solved problems beyond sunflower
 - unseeded problems can still be pulled into a workspace from the bundled upstream snapshot
@@ -39,13 +40,14 @@ erdos problem list --cluster sunflower
 erdos bootstrap problem 857
 erdos problem artifacts 857 --json
 erdos sunflower status 857
+erdos sunflower board 857
 erdos dossier show 857
 ```
 
 For an unseeded problem, the one-step self-seeding flow is now:
 
 ```bash
-erdos seed problem 25 --include-site --cluster number-theory
+erdos seed problem 25 --cluster number-theory
 erdos problem show 25
 erdos workspace show
 ```
@@ -60,6 +62,8 @@ What `bootstrap` does:
 
 What `seed` does:
 - creates a pull bundle for any problem in the upstream snapshot
+- defaults to a live site snapshot plus a public-search review bundle
+- treats a problem as seed-admissible only when the public site says `open`, unless you intentionally pass `--allow-non-open`
 - promotes that bundle into `.erdos/seeded-problems/<id>/`
 - auto-selects the problem in the workspace
 - syncs the bundled ORP workspace kit into `.erdos/orp/`
@@ -69,6 +73,8 @@ What `seed` does:
   - `AGENT_START.md`
   - `ROUTES.md`
   - `CHECKPOINT_NOTES.md`
+  - `PUBLIC_STATUS_REVIEW.md`
+  - `AGENT_WEBSEARCH_BRIEF.md`
 
 ## Pull lanes
 
@@ -78,7 +84,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 problem 999 --include-site
+erdos pull problem 999 --include-site --include-public-search
 erdos pull problem 999 --refresh-upstream
 ```
 
@@ -91,6 +97,10 @@ What the pull lanes do:
 - `erdos pull literature <id>` creates only the literature lane
 - when a problem is locally seeded, the artifact lane includes the canonical dossier, pack context, and compute packets
 - when `--include-site` is used, the literature lane can include a live site snapshot and plain-text extract
+- when `--include-public-search` is used, the literature lane also includes:
+  - `PUBLIC_STATUS_REVIEW.md`
+  - `PUBLIC_STATUS_REVIEW.json`
+  - `AGENT_WEBSEARCH_BRIEF.md`
 
 ## Maintainer seeding
 
@@ -115,6 +125,9 @@ What maintainer seeding does:
   - `AGENT_START.md`
   - `ROUTES.md`
   - `CHECKPOINT_NOTES.md`
+- public-truth starter files:
+  - `PUBLIC_STATUS_REVIEW.md`
+  - `AGENT_WEBSEARCH_BRIEF.md`
 - preserves upstream/site provenance in the local record
 
 ## Sunflower pack
@@ -125,9 +138,11 @@ The first deep pack is the sunflower quartet:
 - `536`: natural-density LCM analogue
 - `856`: harmonic-density LCM analogue
 
-Deep sunflower problems now also ship route packets:
-- `20`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`
-- `857`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`
+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`
 
 Useful sunflower commands:
 
@@ -135,6 +150,8 @@ Useful sunflower commands:
 erdos cluster show sunflower
 erdos sunflower status 20
 erdos sunflower status 536
+erdos sunflower board 536
+erdos sunflower board 857
 erdos sunflower status 857 --json
 ```
 
@@ -144,8 +161,17 @@ erdos sunflower status 857 --json
 - active route
 - route breakthrough state
 - problem-solved distinction
+- atomic board posture, active ticket, ready-atom count, and first ready atom when a board packet exists
 - compute posture when a packet exists
 
+`erdos sunflower board` surfaces:
+- mirrored lab atomic boards for `20` and `857`
+- lighter dossier-bridge boards for `536` and `856`
+- route status
+- ticket board summary
+- first-principles ladder
+- ready queue
+
 ## ORP
 
 `erdos-problems` now ships a bundled Open Research Protocol kit:
@@ -185,6 +211,7 @@ erdos workspace show
 erdos orp show
 erdos orp sync
 erdos sunflower status 857
+erdos sunflower board 857
 erdos sunflower status --json
 erdos dossier show
 erdos upstream show
@@ -193,7 +220,7 @@ erdos upstream diff
 erdos scaffold problem 857
 erdos bootstrap problem 857
 erdos bootstrap problem 857 --sync-upstream
-erdos seed problem 25 --include-site --cluster number-theory
+erdos seed problem 25 --cluster number-theory
 erdos pull problem 857
 erdos pull artifacts 857
 erdos pull literature 857
@@ -221,6 +248,8 @@ Many seeded dossiers now also carry starter-loop artifacts:
 - `AGENT_START.md`
 - `ROUTES.md`
 - `CHECKPOINT_NOTES.md`
+- `PUBLIC_STATUS_REVIEW.md`
+- `AGENT_WEBSEARCH_BRIEF.md`
 
 The CLI can surface these directly:
 - `erdos problem artifacts <id>` shows the canonical inventory
@@ -234,8 +263,9 @@ The CLI can surface these directly:
 For sunflower problems, the CLI also surfaces pack-specific artifacts:
 - pack README context
 - per-problem context files under `packs/sunflower/problems/<id>/`
-- route packets and checkpoint/report packets for `20` and `857`
+- route packets, checkpoint/report packets, and board packets for the full sunflower quartet
 - compute packets under `packs/sunflower/compute/<id>/` when available
+- compute-governance evaluation under `breakthroughs`, surfaced through `erdos sunflower status`
 
 ## Notes
 

package/docs/RESEARCH_LOOP.md

@@ -26,8 +26,9 @@ Workspace runtime files live under `.erdos/`:
 5. Set continuation mode.
 6. Sync checkpoints.
 7. Pull or scaffold artifacts.
-8. Work the active route.
-9. Sync checkpoints again at honest boundaries.
+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.
 
 ## Commands
 
@@ -44,7 +45,7 @@ erdos workspace show
 For problems that are not yet packaged as native dossiers, the loop can start with one-step self-seeding:
 
 ```bash
-erdos seed problem 25 --include-site --cluster number-theory
+erdos seed problem 25 --cluster number-theory
 erdos preflight
 erdos continuation use route
 erdos checkpoints sync
@@ -56,6 +57,8 @@ The seeded dossier now also includes starter-loop artifacts:
 - `AGENT_START.md`
 - `ROUTES.md`
 - `CHECKPOINT_NOTES.md`
+- `PUBLIC_STATUS_REVIEW.md`
+- `AGENT_WEBSEARCH_BRIEF.md`
 
 The ORP kit travels with the workspace too:
 - `PROTOCOL.md`
@@ -64,6 +67,12 @@ The ORP kit travels with the workspace too:
 - `templates/VERIFICATION_RECORD.md`
 - `templates/FAILED_TOPIC.md`
 
+For sunflower compute lanes, ORP now sits above `breakthroughs`:
+- `erdos sunflower status <id>` evaluates the packaged compute lane with `breakthroughs`
+- `erdos sunflower board <id>` exposes the packaged atomic or bridge board for the active sunflower problem
+- 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
+
 ## Status ladder
 
 The public package uses the same ladder we converged on in the lab:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "erdos-problems",
-  "version": "0.1.9",
+  "version": "0.1.11",
   "description": "CLI atlas and staged research harness for Paul Erdos problems.",
   "type": "module",
   "bin": {
@@ -31,6 +31,7 @@
     "sunflower"
   ],
   "dependencies": {
+    "breakthroughs": "^0.1.1",
     "yaml": "^2.8.3"
   },
   "license": "MIT"

package/packs/sunflower/README.md

@@ -15,5 +15,9 @@ 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`
-- `857` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`
+- `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`
+
+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`

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

@@ -0,0 +1,45 @@
+# Problem 20 Atomic Board Packet
+
+- Profile: `deep_atomic_ops`
+- Source board JSON: `sunflower-coda/repo/analysis/problem20_k3_gateboard.json`
+- Source board markdown: `sunflower-coda/repo/docs/PROBLEM20_K3_OPS_BOARD.md`
+- Module target: `sunflower-coda/repo/sunflower_lean/SunflowerLean/ErdosProblem20.lean`
+
+## Route Status
+
+| Route | Loose | Strict |
+|---|---:|---:|
+| `uniform_prize` | `7/7` | `7/7` |
+| `uniform_prize_final_k3` | `5/5` | `5/5` |
+| `uniform_prize_full_all_k` | `0/1` | `0/1` |
+
+## Ticket Board
+
+| Ticket | Leaf | Status | Gates | Atoms |
+|---|---|---|---:|---:|
+| `T1` | `UniformBoundF3Global` | `done` | `5/5` | `16/16` |
+| `T2` | `UniformBoundF4Global` | `done` | `5/5` | `15/15` |
+| `T3` | `UniformBoundF5Global` | `done` | `5/5` | `15/15` |
+| `T4` | `UniformBoundF6Global` | `done` | `5/5` | `15/15` |
+| `T5` | `UniformK3EnvelopeFrom7WithPolySlack` | `done` | `5/5` | `15/15` |
+| `T6` | `UniformK3From7BaseRangeHyp` | `open` | `5/5` | `77/77` |
+
+## First-Principles Ladder
+
+| Tier | Done |
+|---|---:|
+| `P0-SpecLock` | `18/18` |
+| `P1-StructuralKernel` | `18/18` |
+| `P2-QuantAssembly` | `13/13` |
+| `P3-InterfaceLift` | `18/18` |
+| `P4-Verification` | `86/86` |
+
+## Ready Queue
+
+- *(none)*
+
+## Public-Pack Interpretation
+
+- The public pack mirrors a lab board where the `uniform_prize_final_k3` route is closed.
+- The support lane `T6` remains visible because it carries future reusable witness-construction pressure.
+- The honest next move is not a dependency-satisfied atom today; it is to freeze the next support-lane witness packet before pretending progress is locally admissible.

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

@@ -0,0 +1,98 @@
+board_packet_id: strong20_uniform_k3_atomic_board_v1
+board_profile: deep_atomic_ops
+board_title: Problem 20 K=3 Closure Ops Board
+problem_id: "20"
+active_route: uniform_k3_frontier
+frontier_claim: Keep the public strong-sunflower pack aligned with the live k=3 closure board and surface the remaining support-lane pressure honestly.
+module_target: sunflower-coda/repo/sunflower_lean/SunflowerLean/ErdosProblem20.lean
+source_kind: mirrored_from_lab
+source_board_json: sunflower-coda/repo/analysis/problem20_k3_gateboard.json
+source_board_markdown: sunflower-coda/repo/docs/PROBLEM20_K3_OPS_BOARD.md
+active_ticket_id: T6
+route_status:
+  - route: uniform_prize
+    loose_done: 7
+    loose_total: 7
+    strict_done: 7
+    strict_total: 7
+  - route: uniform_prize_final_k3
+    loose_done: 5
+    loose_total: 5
+    strict_done: 5
+    strict_total: 5
+  - route: uniform_prize_full_all_k
+    loose_done: 0
+    loose_total: 1
+    strict_done: 0
+    strict_total: 1
+tickets:
+  - ticket_id: T1
+    ticket_name: "Closure Lane T1: UniformBoundF3Global"
+    route_leaf: UniformBoundF3Global
+    leaf_status: done
+    gates_done: 5
+    gates_total: 5
+    atoms_done: 16
+    atoms_total: 16
+  - ticket_id: T2
+    ticket_name: "Closure Lane T2: UniformBoundF4Global"
+    route_leaf: UniformBoundF4Global
+    leaf_status: done
+    gates_done: 5
+    gates_total: 5
+    atoms_done: 15
+    atoms_total: 15
+  - ticket_id: T3
+    ticket_name: "Closure Lane T3: UniformBoundF5Global"
+    route_leaf: UniformBoundF5Global
+    leaf_status: done
+    gates_done: 5
+    gates_total: 5
+    atoms_done: 15
+    atoms_total: 15
+  - ticket_id: T4
+    ticket_name: "Closure Lane T4: UniformBoundF6Global"
+    route_leaf: UniformBoundF6Global
+    leaf_status: done
+    gates_done: 5
+    gates_total: 5
+    atoms_done: 15
+    atoms_total: 15
+  - ticket_id: T5
+    ticket_name: "Closure Lane T5: UniformK3EnvelopeFrom7WithPolySlack"
+    route_leaf: UniformK3EnvelopeFrom7WithPolySlack
+    leaf_status: done
+    gates_done: 5
+    gates_total: 5
+    atoms_done: 15
+    atoms_total: 15
+  - ticket_id: T6
+    ticket_name: "Support Lane T6: UniformK3From7 Base/Step Witness Construction"
+    route_leaf: UniformK3From7BaseRangeHyp
+    leaf_status: open
+    gates_done: 5
+    gates_total: 5
+    atoms_done: 77
+    atoms_total: 77
+ladder:
+  - tier: P0-SpecLock
+    done: 18
+    total: 18
+  - tier: P1-StructuralKernel
+    done: 18
+    total: 18
+  - tier: P2-QuantAssembly
+    done: 13
+    total: 13
+  - tier: P3-InterfaceLift
+    done: 18
+    total: 18
+  - tier: P4-Verification
+    done: 86
+    total: 86
+ready_queue: []
+mirage_frontiers: []
+notes:
+  - Mirrored from the live sunflower-coda problem-20 lab board; counts reflect the lab closure/support frontier.
+  - The final k=3 route is closed in the mirrored board.
+  - The support lane remains open but currently has no dependency-satisfied ready atom.

package/packs/sunflower/problems/536/AGENT_START.md

@@ -0,0 +1,15 @@
+# Problem 536 Agent Start
+
+Start here:
+- treat `536` as a sunflower-family bridge problem, not a deep theorem harness yet
+- read the dossier, the pack context, and the atomic bridge board together
+- preserve the exact relation to `857`, `856`, and `20`
+
+First loop:
+- verify the publicized open status with the seeded public-status review
+- freeze the exact statement and reference surface
+- record the cleanest natural-density analogue back to the weak sunflower program
+
+Do not do:
+- do not pretend `536` already has Lean-scanner route depth
+- do not overclaim progress on `857` from a loose analogy note alone

package/packs/sunflower/problems/536/ATOMIC_BOARD.md

@@ -0,0 +1,25 @@
+# Problem 536 Bridge Board Packet
+
+- Profile: `dossier_bridge`
+- Source kind: `public_pack_bridge`
+
+## Route Status
+
+| Route | Loose | Strict |
+|---|---:|---:|
+| `natural_density_lcm_bridge` | `0/3` | `0/3` |
+
+## Active Ticket
+
+| Ticket | Leaf | Status | Gates | Atoms |
+|---|---|---|---:|---:|
+| `T1` Dossier Source Lock | `public_status_and_statement_lock` | `open` | `1/3` | `2/6` |
+
+## Ready Queue
+
+- `T1.G1.A3`: Run the public-status review and freeze the exact open-state snapshot for problem `536`
+
+## Notes
+
+- This board is intentionally lighter than the theorem-engine boards for `20` and `857`.
+- It exists to give agents a disciplined analogue bridge workflow instead of a loose note-taking lane.

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

@@ -0,0 +1,62 @@
+board_packet_id: sunflower536_bridge_board_v1
+board_profile: dossier_bridge
+board_title: Problem 536 Natural-Density LCM Bridge Board
+problem_id: "536"
+active_route: natural_density_lcm_bridge
+frontier_claim: Keep 536 research-ready by freezing public status, exact analogue statements, and explicit bridge artifacts back to 857.
+module_target: ""
+source_kind: public_pack_bridge
+active_ticket_id: T1
+route_status:
+  - route: natural_density_lcm_bridge
+    loose_done: 0
+    loose_total: 3
+    strict_done: 0
+    strict_total: 3
+tickets:
+  - ticket_id: T1
+    ticket_name: Dossier Source Lock
+    route_leaf: public_status_and_statement_lock
+    leaf_status: open
+    gates_done: 1
+    gates_total: 3
+    atoms_done: 2
+    atoms_total: 6
+  - ticket_id: T2
+    ticket_name: Analogue Translation Bridge
+    route_leaf: lcm_analogue_bridge_note
+    leaf_status: open
+    gates_done: 0
+    gates_total: 3
+    atoms_done: 0
+    atoms_total: 6
+  - ticket_id: T3
+    ticket_name: Transfer Back To 857
+    route_leaf: density_to_weak_sunflower_hook
+    leaf_status: open
+    gates_done: 0
+    gates_total: 3
+    atoms_done: 0
+    atoms_total: 6
+ladder:
+  - tier: P0-SpecLock
+    done: 2
+    total: 6
+  - tier: P1-StructuralKernel
+    done: 0
+    total: 6
+  - tier: P2-QuantAssembly
+    done: 0
+    total: 6
+ready_queue:
+  - atom_id: T1.G1.A3
+    ticket_id: T1
+    gate_id: T1.G1
+    tier: P0-SpecLock
+    kind: review
+    title: Run the public-status review and freeze the exact open-state snapshot for problem 536
+    status: ready
+mirage_frontiers: []
+notes:
+  - This is a public-pack bridge board, not a Lean-scanner board.
+  - Counts track dossier and bridge completeness so agents can move with the same disciplined loop as the deep sunflower problems.

package/packs/sunflower/problems/536/CHECKPOINT_PACKET.md

@@ -0,0 +1,11 @@
+# Problem 536 Checkpoint Packet
+
+Checkpoint when one of these becomes true:
+- the public-status review is refreshed and clearly archived
+- the exact analogue statement is normalized in dossier language
+- a crisp bridge note back to `857` is written and cited
+
+What to record:
+- upstream/site/public-search provenance
+- exact wording of the analogue
+- what changed for the next agent

package/packs/sunflower/problems/536/REPORT_PACKET.md

@@ -0,0 +1,11 @@
+# Problem 536 Report Packet
+
+Public-facing report shape:
+- open problem status
+- natural-density LCM framing
+- relation to `857`, `856`, and `20`
+- exact artifacts pulled this pass
+- next honest bridge move
+
+Avoid:
+- speaking as if a theorem-harness closure happened here unless a real deeper pack is added later

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

@@ -0,0 +1,13 @@
+route_packet_id: sunflower536_natural_density_bridge_v1
+route_id: natural_density_lcm_bridge
+frontier_claim: Keep the natural-density LCM analogue synchronized with the weak sunflower program and preserve an honest bridge from public status to research artifacts.
+theorem_module: ""
+checkpoint_packet: CHECKPOINT_PACKET.md
+report_packet: REPORT_PACKET.md
+ready_prompts:
+  - Which exact combinatorial-to-number-theoretic bridge from 536 to 857 should be frozen next?
+  - Which public-status or reference artifact is still missing from the 536 dossier bridge?
+verification_hook:
+  - erdos sunflower status 536
+  - erdos sunflower board 536
+  - erdos problem artifacts 536 --json

package/packs/sunflower/problems/856/AGENT_START.md

@@ -0,0 +1,15 @@
+# Problem 856 Agent Start
+
+Start here:
+- treat `856` as the harmonic-density / logarithmic-density LCM analogue inside the sunflower quartet
+- keep the exponent-transfer story back to `857` explicit
+- use the bridge board rather than improvising a loose literature pass
+
+First loop:
+- verify the publicized open status with the seeded public-status review
+- freeze the exact statement and density language
+- record how progress here would alter `857`-style exponent expectations
+
+Do not do:
+- do not pretend `856` already has the same theorem-board depth as `20` or `857`
+- do not state an exponent consequence unless the supporting bridge artifact is explicitly written down

package/packs/sunflower/problems/856/ATOMIC_BOARD.md

@@ -0,0 +1,25 @@
+# Problem 856 Bridge Board Packet
+
+- Profile: `dossier_bridge`
+- Source kind: `public_pack_bridge`
+
+## Route Status
+
+| Route | Loose | Strict |
+|---|---:|---:|
+| `harmonic_density_lcm_bridge` | `0/3` | `0/3` |
+
+## Active Ticket
+
+| Ticket | Leaf | Status | Gates | Atoms |
+|---|---|---|---:|---:|
+| `T1` Dossier Source Lock | `public_status_and_density_lock` | `open` | `1/3` | `2/6` |
+
+## Ready Queue
+
+- `T1.G1.A3`: Run the public-status review and freeze the exact open-state snapshot for problem `856`
+
+## Notes
+
+- This board is intentionally lighter than the theorem-engine boards for `20` and `857`.
+- It keeps the `856` to `857` exponent bridge explicit instead of leaving it as an unstructured literature hunch.

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

@@ -0,0 +1,62 @@
+board_packet_id: sunflower856_bridge_board_v1
+board_profile: dossier_bridge
+board_title: Problem 856 Harmonic-Density LCM Bridge Board
+problem_id: "856"
+active_route: harmonic_density_lcm_bridge
+frontier_claim: Keep 856 research-ready by freezing public status, exact density-language statements, and explicit exponent-transfer artifacts back to 857.
+module_target: ""
+source_kind: public_pack_bridge
+active_ticket_id: T1
+route_status:
+  - route: harmonic_density_lcm_bridge
+    loose_done: 0
+    loose_total: 3
+    strict_done: 0
+    strict_total: 3
+tickets:
+  - ticket_id: T1
+    ticket_name: Dossier Source Lock
+    route_leaf: public_status_and_density_lock
+    leaf_status: open
+    gates_done: 1
+    gates_total: 3
+    atoms_done: 2
+    atoms_total: 6
+  - ticket_id: T2
+    ticket_name: Density Translation Bridge
+    route_leaf: harmonic_density_bridge_note
+    leaf_status: open
+    gates_done: 0
+    gates_total: 3
+    atoms_done: 0
+    atoms_total: 6
+  - ticket_id: T3
+    ticket_name: Exponent Transfer Back To 857
+    route_leaf: exponent_transfer_hook
+    leaf_status: open
+    gates_done: 0
+    gates_total: 3
+    atoms_done: 0
+    atoms_total: 6
+ladder:
+  - tier: P0-SpecLock
+    done: 2
+    total: 6
+  - tier: P1-StructuralKernel
+    done: 0
+    total: 6
+  - tier: P2-QuantAssembly
+    done: 0
+    total: 6
+ready_queue:
+  - atom_id: T1.G1.A3
+    ticket_id: T1
+    gate_id: T1.G1
+    tier: P0-SpecLock
+    kind: review
+    title: Run the public-status review and freeze the exact open-state snapshot for problem 856
+    status: ready
+mirage_frontiers: []
+notes:
+  - This is a public-pack bridge board, not a Lean-scanner board.
+  - Counts track dossier and bridge completeness so the exponent-transfer story stays explicit and checkpointable.

package/packs/sunflower/problems/856/CHECKPOINT_PACKET.md

@@ -0,0 +1,11 @@
+# Problem 856 Checkpoint Packet
+
+Checkpoint when one of these becomes true:
+- the public-status review is refreshed and archived
+- the exact density-language statement is normalized in dossier form
+- an explicit exponent-transfer note back to `857` is written
+
+What to record:
+- provenance for the status review
+- exact wording of the density analogue
+- what changed in the `856` to `857` bridge story

package/packs/sunflower/problems/856/REPORT_PACKET.md

@@ -0,0 +1,11 @@
+# Problem 856 Report Packet
+
+Public-facing report shape:
+- open problem status
+- harmonic-density / logarithmic-density framing
+- relation to `857`, `536`, and `20`
+- exact artifacts pulled or normalized this pass
+- next honest exponent-transfer move
+
+Avoid:
+- claiming more than a dossier/bridge advance unless a deeper theorem harness is actually added later

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

@@ -0,0 +1,13 @@
+route_packet_id: sunflower856_harmonic_density_bridge_v1
+route_id: harmonic_density_lcm_bridge
+frontier_claim: Keep the harmonic-density LCM analogue synchronized with the weak sunflower program and preserve explicit exponent-transfer artifacts.
+theorem_module: ""
+checkpoint_packet: CHECKPOINT_PACKET.md
+report_packet: REPORT_PACKET.md
+ready_prompts:
+  - Which exact exponent-transfer statement from 856 back to 857 should be frozen next?
+  - Which density-language artifact is still missing from the 856 bridge dossier?
+verification_hook:
+  - erdos sunflower status 856
+  - erdos sunflower board 856
+  - erdos problem artifacts 856 --json