erdos-problems 0.1.10 → 0.1.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -22,6 +22,7 @@ Official binary:
22
22
  - workspace `.erdos/` state for active-problem selection, upstream refreshes, scaffolds, and pull bundles
23
23
  - sunflower cluster as the first deep harness pack
24
24
  - quartet-aware sunflower context for `20`, `536`, `856`, and `857`
25
+ - packaged atomic/bridge board packets for the full sunflower quartet
25
26
  - packaged compute-lane metadata for deep sunflower problems, surfaced directly in the CLI
26
27
  - seeded atlas now includes open and solved problems beyond sunflower
27
28
  - unseeded problems can still be pulled into a workspace from the bundled upstream snapshot
@@ -39,6 +40,7 @@ erdos problem list --cluster sunflower
39
40
  erdos bootstrap problem 857
40
41
  erdos problem artifacts 857 --json
41
42
  erdos sunflower status 857
43
+ erdos sunflower board 857
42
44
  erdos dossier show 857
43
45
  ```
44
46
 
@@ -136,9 +138,11 @@ The first deep pack is the sunflower quartet:
136
138
  - `536`: natural-density LCM analogue
137
139
  - `856`: harmonic-density LCM analogue
138
140
 
139
- Deep sunflower problems now also ship route packets:
140
- - `20`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`
141
- - `857`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`
141
+ Sunflower problems now ship pack packets:
142
+ - `20`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
143
+ - `857`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
144
+ - `536`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
145
+ - `856`: `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
142
146
 
143
147
  Useful sunflower commands:
144
148
 
@@ -146,6 +150,10 @@ Useful sunflower commands:
146
150
  erdos cluster show sunflower
147
151
  erdos sunflower status 20
148
152
  erdos sunflower status 536
153
+ erdos sunflower board 536
154
+ erdos sunflower ready 857
155
+ erdos sunflower ladder 20
156
+ erdos sunflower board 857
149
157
  erdos sunflower status 857 --json
150
158
  ```
151
159
 
@@ -155,8 +163,23 @@ erdos sunflower status 857 --json
155
163
  - active route
156
164
  - route breakthrough state
157
165
  - problem-solved distinction
166
+ - atomic board posture, active ticket, ready-atom count, and first ready atom when a board packet exists
158
167
  - compute posture when a packet exists
159
168
 
169
+ `erdos sunflower board` surfaces:
170
+ - mirrored lab atomic boards for `20` and `857`
171
+ - lighter dossier-bridge boards for `536` and `856`
172
+ - route status
173
+ - ticket board summary
174
+ - first-principles ladder
175
+ - ready queue
176
+
177
+ `erdos sunflower ready` surfaces:
178
+ - the current dependency-satisfied ready queue for the active sunflower board
179
+
180
+ `erdos sunflower ladder` surfaces:
181
+ - the first-principles ladder for the active sunflower board
182
+
160
183
  ## ORP
161
184
 
162
185
  `erdos-problems` now ships a bundled Open Research Protocol kit:
@@ -196,6 +219,9 @@ erdos workspace show
196
219
  erdos orp show
197
220
  erdos orp sync
198
221
  erdos sunflower status 857
222
+ erdos sunflower board 857
223
+ erdos sunflower ready 857
224
+ erdos sunflower ladder 857
199
225
  erdos sunflower status --json
200
226
  erdos dossier show
201
227
  erdos upstream show
@@ -247,7 +273,7 @@ The CLI can surface these directly:
247
273
  For sunflower problems, the CLI also surfaces pack-specific artifacts:
248
274
  - pack README context
249
275
  - per-problem context files under `packs/sunflower/problems/<id>/`
250
- - route packets and checkpoint/report packets for `20` and `857`
276
+ - route packets, checkpoint/report packets, and board packets for the full sunflower quartet
251
277
  - compute packets under `packs/sunflower/compute/<id>/` when available
252
278
  - compute-governance evaluation under `breakthroughs`, surfaced through `erdos sunflower status`
253
279
 
@@ -69,6 +69,9 @@ The ORP kit travels with the workspace too:
69
69
 
70
70
  For sunflower compute lanes, ORP now sits above `breakthroughs`:
71
71
  - `erdos sunflower status <id>` evaluates the packaged compute lane with `breakthroughs`
72
+ - `erdos sunflower board <id>` exposes the packaged atomic or bridge board for the active sunflower problem
73
+ - `erdos sunflower ready <id>` exposes the dependency-satisfied ready queue for the packaged board
74
+ - `erdos sunflower ladder <id>` exposes the first-principles ladder for the packaged board
72
75
  - the CLI surfaces the selected rung, dispatch action, and the reason compute is admissible
73
76
  - this is compute governance and traceability, not an automatic compute launch
74
77
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "erdos-problems",
3
- "version": "0.1.10",
3
+ "version": "0.1.12",
4
4
  "description": "CLI atlas and staged research harness for Paul Erdos problems.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -15,5 +15,9 @@ Profiles:
15
15
  - `856`: dossier bridge, harmonic-density LCM analogue
16
16
 
17
17
  Deep route packets:
18
- - `20` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`
19
- - `857` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`
18
+ - `20` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
19
+ - `857` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
20
+
21
+ Bridge packets:
22
+ - `536` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
23
+ - `856` ships `AGENT_START.md`, `ROUTE_PACKET.yaml`, `CHECKPOINT_PACKET.md`, `REPORT_PACKET.md`, `ATOMIC_BOARD.yaml`, `ATOMIC_BOARD.md`
@@ -0,0 +1,45 @@
1
+ # Problem 20 Atomic Board Packet
2
+
3
+ - Profile: `deep_atomic_ops`
4
+ - Source board JSON: `sunflower-coda/repo/analysis/problem20_k3_gateboard.json`
5
+ - Source board markdown: `sunflower-coda/repo/docs/PROBLEM20_K3_OPS_BOARD.md`
6
+ - Module target: `sunflower-coda/repo/sunflower_lean/SunflowerLean/ErdosProblem20.lean`
7
+
8
+ ## Route Status
9
+
10
+ | Route | Loose | Strict |
11
+ |---|---:|---:|
12
+ | `uniform_prize` | `7/7` | `7/7` |
13
+ | `uniform_prize_final_k3` | `5/5` | `5/5` |
14
+ | `uniform_prize_full_all_k` | `0/1` | `0/1` |
15
+
16
+ ## Ticket Board
17
+
18
+ | Ticket | Leaf | Status | Gates | Atoms |
19
+ |---|---|---|---:|---:|
20
+ | `T1` | `UniformBoundF3Global` | `done` | `5/5` | `16/16` |
21
+ | `T2` | `UniformBoundF4Global` | `done` | `5/5` | `15/15` |
22
+ | `T3` | `UniformBoundF5Global` | `done` | `5/5` | `15/15` |
23
+ | `T4` | `UniformBoundF6Global` | `done` | `5/5` | `15/15` |
24
+ | `T5` | `UniformK3EnvelopeFrom7WithPolySlack` | `done` | `5/5` | `15/15` |
25
+ | `T6` | `UniformK3From7BaseRangeHyp` | `open` | `5/5` | `77/77` |
26
+
27
+ ## First-Principles Ladder
28
+
29
+ | Tier | Done |
30
+ |---|---:|
31
+ | `P0-SpecLock` | `18/18` |
32
+ | `P1-StructuralKernel` | `18/18` |
33
+ | `P2-QuantAssembly` | `13/13` |
34
+ | `P3-InterfaceLift` | `18/18` |
35
+ | `P4-Verification` | `86/86` |
36
+
37
+ ## Ready Queue
38
+
39
+ - *(none)*
40
+
41
+ ## Public-Pack Interpretation
42
+
43
+ - The public pack mirrors a lab board where the `uniform_prize_final_k3` route is closed.
44
+ - The support lane `T6` remains visible because it carries future reusable witness-construction pressure.
45
+ - 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.
@@ -0,0 +1,98 @@
1
+ board_packet_id: strong20_uniform_k3_atomic_board_v1
2
+ board_profile: deep_atomic_ops
3
+ board_title: Problem 20 K=3 Closure Ops Board
4
+ problem_id: "20"
5
+ active_route: uniform_k3_frontier
6
+ frontier_claim: Keep the public strong-sunflower pack aligned with the live k=3 closure board and surface the remaining support-lane pressure honestly.
7
+ module_target: sunflower-coda/repo/sunflower_lean/SunflowerLean/ErdosProblem20.lean
8
+ source_kind: mirrored_from_lab
9
+ source_board_json: sunflower-coda/repo/analysis/problem20_k3_gateboard.json
10
+ source_board_markdown: sunflower-coda/repo/docs/PROBLEM20_K3_OPS_BOARD.md
11
+ active_ticket_id: T6
12
+ route_status:
13
+ - route: uniform_prize
14
+ loose_done: 7
15
+ loose_total: 7
16
+ strict_done: 7
17
+ strict_total: 7
18
+ - route: uniform_prize_final_k3
19
+ loose_done: 5
20
+ loose_total: 5
21
+ strict_done: 5
22
+ strict_total: 5
23
+ - route: uniform_prize_full_all_k
24
+ loose_done: 0
25
+ loose_total: 1
26
+ strict_done: 0
27
+ strict_total: 1
28
+ tickets:
29
+ - ticket_id: T1
30
+ ticket_name: "Closure Lane T1: UniformBoundF3Global"
31
+ route_leaf: UniformBoundF3Global
32
+ leaf_status: done
33
+ gates_done: 5
34
+ gates_total: 5
35
+ atoms_done: 16
36
+ atoms_total: 16
37
+ - ticket_id: T2
38
+ ticket_name: "Closure Lane T2: UniformBoundF4Global"
39
+ route_leaf: UniformBoundF4Global
40
+ leaf_status: done
41
+ gates_done: 5
42
+ gates_total: 5
43
+ atoms_done: 15
44
+ atoms_total: 15
45
+ - ticket_id: T3
46
+ ticket_name: "Closure Lane T3: UniformBoundF5Global"
47
+ route_leaf: UniformBoundF5Global
48
+ leaf_status: done
49
+ gates_done: 5
50
+ gates_total: 5
51
+ atoms_done: 15
52
+ atoms_total: 15
53
+ - ticket_id: T4
54
+ ticket_name: "Closure Lane T4: UniformBoundF6Global"
55
+ route_leaf: UniformBoundF6Global
56
+ leaf_status: done
57
+ gates_done: 5
58
+ gates_total: 5
59
+ atoms_done: 15
60
+ atoms_total: 15
61
+ - ticket_id: T5
62
+ ticket_name: "Closure Lane T5: UniformK3EnvelopeFrom7WithPolySlack"
63
+ route_leaf: UniformK3EnvelopeFrom7WithPolySlack
64
+ leaf_status: done
65
+ gates_done: 5
66
+ gates_total: 5
67
+ atoms_done: 15
68
+ atoms_total: 15
69
+ - ticket_id: T6
70
+ ticket_name: "Support Lane T6: UniformK3From7 Base/Step Witness Construction"
71
+ route_leaf: UniformK3From7BaseRangeHyp
72
+ leaf_status: open
73
+ gates_done: 5
74
+ gates_total: 5
75
+ atoms_done: 77
76
+ atoms_total: 77
77
+ ladder:
78
+ - tier: P0-SpecLock
79
+ done: 18
80
+ total: 18
81
+ - tier: P1-StructuralKernel
82
+ done: 18
83
+ total: 18
84
+ - tier: P2-QuantAssembly
85
+ done: 13
86
+ total: 13
87
+ - tier: P3-InterfaceLift
88
+ done: 18
89
+ total: 18
90
+ - tier: P4-Verification
91
+ done: 86
92
+ total: 86
93
+ ready_queue: []
94
+ mirage_frontiers: []
95
+ notes:
96
+ - Mirrored from the live sunflower-coda problem-20 lab board; counts reflect the lab closure/support frontier.
97
+ - The final k=3 route is closed in the mirrored board.
98
+ - The support lane remains open but currently has no dependency-satisfied ready atom.
@@ -0,0 +1,15 @@
1
+ # Problem 536 Agent Start
2
+
3
+ Start here:
4
+ - treat `536` as a sunflower-family bridge problem, not a deep theorem harness yet
5
+ - read the dossier, the pack context, and the atomic bridge board together
6
+ - preserve the exact relation to `857`, `856`, and `20`
7
+
8
+ First loop:
9
+ - verify the publicized open status with the seeded public-status review
10
+ - freeze the exact statement and reference surface
11
+ - record the cleanest natural-density analogue back to the weak sunflower program
12
+
13
+ Do not do:
14
+ - do not pretend `536` already has Lean-scanner route depth
15
+ - do not overclaim progress on `857` from a loose analogy note alone
@@ -0,0 +1,25 @@
1
+ # Problem 536 Bridge Board Packet
2
+
3
+ - Profile: `dossier_bridge`
4
+ - Source kind: `public_pack_bridge`
5
+
6
+ ## Route Status
7
+
8
+ | Route | Loose | Strict |
9
+ |---|---:|---:|
10
+ | `natural_density_lcm_bridge` | `0/3` | `0/3` |
11
+
12
+ ## Active Ticket
13
+
14
+ | Ticket | Leaf | Status | Gates | Atoms |
15
+ |---|---|---|---:|---:|
16
+ | `T1` Dossier Source Lock | `public_status_and_statement_lock` | `open` | `1/3` | `2/6` |
17
+
18
+ ## Ready Queue
19
+
20
+ - `T1.G1.A3`: Run the public-status review and freeze the exact open-state snapshot for problem `536`
21
+
22
+ ## Notes
23
+
24
+ - This board is intentionally lighter than the theorem-engine boards for `20` and `857`.
25
+ - It exists to give agents a disciplined analogue bridge workflow instead of a loose note-taking lane.
@@ -0,0 +1,62 @@
1
+ board_packet_id: sunflower536_bridge_board_v1
2
+ board_profile: dossier_bridge
3
+ board_title: Problem 536 Natural-Density LCM Bridge Board
4
+ problem_id: "536"
5
+ active_route: natural_density_lcm_bridge
6
+ frontier_claim: Keep 536 research-ready by freezing public status, exact analogue statements, and explicit bridge artifacts back to 857.
7
+ module_target: ""
8
+ source_kind: public_pack_bridge
9
+ active_ticket_id: T1
10
+ route_status:
11
+ - route: natural_density_lcm_bridge
12
+ loose_done: 0
13
+ loose_total: 3
14
+ strict_done: 0
15
+ strict_total: 3
16
+ tickets:
17
+ - ticket_id: T1
18
+ ticket_name: Dossier Source Lock
19
+ route_leaf: public_status_and_statement_lock
20
+ leaf_status: open
21
+ gates_done: 1
22
+ gates_total: 3
23
+ atoms_done: 2
24
+ atoms_total: 6
25
+ - ticket_id: T2
26
+ ticket_name: Analogue Translation Bridge
27
+ route_leaf: lcm_analogue_bridge_note
28
+ leaf_status: open
29
+ gates_done: 0
30
+ gates_total: 3
31
+ atoms_done: 0
32
+ atoms_total: 6
33
+ - ticket_id: T3
34
+ ticket_name: Transfer Back To 857
35
+ route_leaf: density_to_weak_sunflower_hook
36
+ leaf_status: open
37
+ gates_done: 0
38
+ gates_total: 3
39
+ atoms_done: 0
40
+ atoms_total: 6
41
+ ladder:
42
+ - tier: P0-SpecLock
43
+ done: 2
44
+ total: 6
45
+ - tier: P1-StructuralKernel
46
+ done: 0
47
+ total: 6
48
+ - tier: P2-QuantAssembly
49
+ done: 0
50
+ total: 6
51
+ ready_queue:
52
+ - atom_id: T1.G1.A3
53
+ ticket_id: T1
54
+ gate_id: T1.G1
55
+ tier: P0-SpecLock
56
+ kind: review
57
+ title: Run the public-status review and freeze the exact open-state snapshot for problem 536
58
+ status: ready
59
+ mirage_frontiers: []
60
+ notes:
61
+ - This is a public-pack bridge board, not a Lean-scanner board.
62
+ - Counts track dossier and bridge completeness so agents can move with the same disciplined loop as the deep sunflower problems.
@@ -0,0 +1,11 @@
1
+ # Problem 536 Checkpoint Packet
2
+
3
+ Checkpoint when one of these becomes true:
4
+ - the public-status review is refreshed and clearly archived
5
+ - the exact analogue statement is normalized in dossier language
6
+ - a crisp bridge note back to `857` is written and cited
7
+
8
+ What to record:
9
+ - upstream/site/public-search provenance
10
+ - exact wording of the analogue
11
+ - what changed for the next agent
@@ -0,0 +1,11 @@
1
+ # Problem 536 Report Packet
2
+
3
+ Public-facing report shape:
4
+ - open problem status
5
+ - natural-density LCM framing
6
+ - relation to `857`, `856`, and `20`
7
+ - exact artifacts pulled this pass
8
+ - next honest bridge move
9
+
10
+ Avoid:
11
+ - speaking as if a theorem-harness closure happened here unless a real deeper pack is added later
@@ -0,0 +1,13 @@
1
+ route_packet_id: sunflower536_natural_density_bridge_v1
2
+ route_id: natural_density_lcm_bridge
3
+ 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.
4
+ theorem_module: ""
5
+ checkpoint_packet: CHECKPOINT_PACKET.md
6
+ report_packet: REPORT_PACKET.md
7
+ ready_prompts:
8
+ - Which exact combinatorial-to-number-theoretic bridge from 536 to 857 should be frozen next?
9
+ - Which public-status or reference artifact is still missing from the 536 dossier bridge?
10
+ verification_hook:
11
+ - erdos sunflower status 536
12
+ - erdos sunflower board 536
13
+ - erdos problem artifacts 536 --json
@@ -0,0 +1,15 @@
1
+ # Problem 856 Agent Start
2
+
3
+ Start here:
4
+ - treat `856` as the harmonic-density / logarithmic-density LCM analogue inside the sunflower quartet
5
+ - keep the exponent-transfer story back to `857` explicit
6
+ - use the bridge board rather than improvising a loose literature pass
7
+
8
+ First loop:
9
+ - verify the publicized open status with the seeded public-status review
10
+ - freeze the exact statement and density language
11
+ - record how progress here would alter `857`-style exponent expectations
12
+
13
+ Do not do:
14
+ - do not pretend `856` already has the same theorem-board depth as `20` or `857`
15
+ - do not state an exponent consequence unless the supporting bridge artifact is explicitly written down
@@ -0,0 +1,25 @@
1
+ # Problem 856 Bridge Board Packet
2
+
3
+ - Profile: `dossier_bridge`
4
+ - Source kind: `public_pack_bridge`
5
+
6
+ ## Route Status
7
+
8
+ | Route | Loose | Strict |
9
+ |---|---:|---:|
10
+ | `harmonic_density_lcm_bridge` | `0/3` | `0/3` |
11
+
12
+ ## Active Ticket
13
+
14
+ | Ticket | Leaf | Status | Gates | Atoms |
15
+ |---|---|---|---:|---:|
16
+ | `T1` Dossier Source Lock | `public_status_and_density_lock` | `open` | `1/3` | `2/6` |
17
+
18
+ ## Ready Queue
19
+
20
+ - `T1.G1.A3`: Run the public-status review and freeze the exact open-state snapshot for problem `856`
21
+
22
+ ## Notes
23
+
24
+ - This board is intentionally lighter than the theorem-engine boards for `20` and `857`.
25
+ - It keeps the `856` to `857` exponent bridge explicit instead of leaving it as an unstructured literature hunch.
@@ -0,0 +1,62 @@
1
+ board_packet_id: sunflower856_bridge_board_v1
2
+ board_profile: dossier_bridge
3
+ board_title: Problem 856 Harmonic-Density LCM Bridge Board
4
+ problem_id: "856"
5
+ active_route: harmonic_density_lcm_bridge
6
+ frontier_claim: Keep 856 research-ready by freezing public status, exact density-language statements, and explicit exponent-transfer artifacts back to 857.
7
+ module_target: ""
8
+ source_kind: public_pack_bridge
9
+ active_ticket_id: T1
10
+ route_status:
11
+ - route: harmonic_density_lcm_bridge
12
+ loose_done: 0
13
+ loose_total: 3
14
+ strict_done: 0
15
+ strict_total: 3
16
+ tickets:
17
+ - ticket_id: T1
18
+ ticket_name: Dossier Source Lock
19
+ route_leaf: public_status_and_density_lock
20
+ leaf_status: open
21
+ gates_done: 1
22
+ gates_total: 3
23
+ atoms_done: 2
24
+ atoms_total: 6
25
+ - ticket_id: T2
26
+ ticket_name: Density Translation Bridge
27
+ route_leaf: harmonic_density_bridge_note
28
+ leaf_status: open
29
+ gates_done: 0
30
+ gates_total: 3
31
+ atoms_done: 0
32
+ atoms_total: 6
33
+ - ticket_id: T3
34
+ ticket_name: Exponent Transfer Back To 857
35
+ route_leaf: exponent_transfer_hook
36
+ leaf_status: open
37
+ gates_done: 0
38
+ gates_total: 3
39
+ atoms_done: 0
40
+ atoms_total: 6
41
+ ladder:
42
+ - tier: P0-SpecLock
43
+ done: 2
44
+ total: 6
45
+ - tier: P1-StructuralKernel
46
+ done: 0
47
+ total: 6
48
+ - tier: P2-QuantAssembly
49
+ done: 0
50
+ total: 6
51
+ ready_queue:
52
+ - atom_id: T1.G1.A3
53
+ ticket_id: T1
54
+ gate_id: T1.G1
55
+ tier: P0-SpecLock
56
+ kind: review
57
+ title: Run the public-status review and freeze the exact open-state snapshot for problem 856
58
+ status: ready
59
+ mirage_frontiers: []
60
+ notes:
61
+ - This is a public-pack bridge board, not a Lean-scanner board.
62
+ - Counts track dossier and bridge completeness so the exponent-transfer story stays explicit and checkpointable.
@@ -0,0 +1,11 @@
1
+ # Problem 856 Checkpoint Packet
2
+
3
+ Checkpoint when one of these becomes true:
4
+ - the public-status review is refreshed and archived
5
+ - the exact density-language statement is normalized in dossier form
6
+ - an explicit exponent-transfer note back to `857` is written
7
+
8
+ What to record:
9
+ - provenance for the status review
10
+ - exact wording of the density analogue
11
+ - what changed in the `856` to `857` bridge story
@@ -0,0 +1,11 @@
1
+ # Problem 856 Report Packet
2
+
3
+ Public-facing report shape:
4
+ - open problem status
5
+ - harmonic-density / logarithmic-density framing
6
+ - relation to `857`, `536`, and `20`
7
+ - exact artifacts pulled or normalized this pass
8
+ - next honest exponent-transfer move
9
+
10
+ Avoid:
11
+ - claiming more than a dossier/bridge advance unless a deeper theorem harness is actually added later
@@ -0,0 +1,13 @@
1
+ route_packet_id: sunflower856_harmonic_density_bridge_v1
2
+ route_id: harmonic_density_lcm_bridge
3
+ frontier_claim: Keep the harmonic-density LCM analogue synchronized with the weak sunflower program and preserve explicit exponent-transfer artifacts.
4
+ theorem_module: ""
5
+ checkpoint_packet: CHECKPOINT_PACKET.md
6
+ report_packet: REPORT_PACKET.md
7
+ ready_prompts:
8
+ - Which exact exponent-transfer statement from 856 back to 857 should be frozen next?
9
+ - Which density-language artifact is still missing from the 856 bridge dossier?
10
+ verification_hook:
11
+ - erdos sunflower status 856
12
+ - erdos sunflower board 856
13
+ - erdos problem artifacts 856 --json
@@ -0,0 +1,52 @@
1
+ # Problem 857 Atomic Board Packet
2
+
3
+ - Profile: `deep_atomic_ops`
4
+ - Source board JSON: `sunflower-coda/repo/analysis/problem857_redesign_gateboard.json`
5
+ - Source board markdown: `sunflower-coda/repo/docs/PROBLEM857_REDESIGN_OPS_BOARD.md`
6
+ - Module target: `sunflower-coda/repo/sunflower_lean/SunflowerLean/ObstructionExport.lean`
7
+
8
+ ## Route Status
9
+
10
+ | Route | Loose | Strict |
11
+ |---|---:|---:|
12
+ | `o1a_foundation` | `2/3` | `2/3` |
13
+ | `o1a_certificate_reduction` | `3/4` | `3/4` |
14
+ | `o1a_residual_router` | `2/5` | `2/5` |
15
+ | `o1a_hard_upgrade` | `1/5` | `1/5` |
16
+ | `b2_recurrence_spine` | `0/4` | `0/4` |
17
+ | `post_counting_redesign` | `3/9` | `3/9` |
18
+ | `global_family_card_export` | `1/1` | `1/1` |
19
+ | `chain_bucket_export` | `1/1` | `1/1` |
20
+ | `pair_count_export` | `1/1` | `1/1` |
21
+ | `core_slice_square_export` | `1/1` | `1/1` |
22
+ | `m_cube_export` | `1/1` | `1/1` |
23
+ | `explicit_remainder_export` | `1/1` | `1/1` |
24
+ | `explicit_M_remainder_export` | `1/1` | `1/1` |
25
+ | `o1a_existential_explicit_export` | `1/1` | `1/1` |
26
+ | `anchored_selector_linearization` | `0/1` | `0/1` |
27
+
28
+ ## Active Ticket
29
+
30
+ | Ticket | Leaf | Status | Gates | Atoms |
31
+ |---|---|---|---:|---:|
32
+ | `T10` Route Redesign T10: Anchored-Selector Linearization | `anchored_selector_linearization_realized` | `open` | `2/5` | `9/15` |
33
+
34
+ ## Ready Queue
35
+
36
+ - `T10.G3.A2`: Promote the helper/theorem stack into `anchored_selector_linearization_realized`
37
+
38
+ ## First-Principles Ladder
39
+
40
+ | Tier | Done |
41
+ |---|---:|
42
+ | `P0-SpecLock` | `30/30` |
43
+ | `P1-StructuralKernel` | `30/30` |
44
+ | `P2-QuantAssembly` | `24/30` |
45
+ | `P3-InterfaceLift` | `24/30` |
46
+ | `P4-Verification` | `26/30` |
47
+
48
+ ## Public-Pack Interpretation
49
+
50
+ - This packet mirrors the live redesign board rather than inventing a new public abstraction.
51
+ - The honest next atom is already known and dependency-satisfied.
52
+ - The public sunflower pack should therefore present `857` as a route with a concrete active atom, not just a broad frontier label.