erdos-problems 0.3.1 → 0.3.3

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.
Files changed (41) hide show
  1. package/README.md +1 -1
  2. package/package.json +1 -1
  3. package/packs/number-theory/README.md +1 -0
  4. package/packs/number-theory/problems/848/BOUNDED_VERIFICATION_PLAN.md +43 -0
  5. package/packs/number-theory/problems/848/BRANCH_COMPARISON_LEDGER.md +85 -0
  6. package/packs/number-theory/problems/848/CERTIFIED_NUMERICAL_LEDGER.md +88 -0
  7. package/packs/number-theory/problems/848/CHECKPOINT_TEMPLATE.md +8 -0
  8. package/packs/number-theory/problems/848/CONTEXT.md +11 -0
  9. package/packs/number-theory/problems/848/EXTERNAL_VERIFICATION_LEDGER.md +56 -0
  10. package/packs/number-theory/problems/848/EXTRACTION_CHECKLIST.md +114 -0
  11. package/packs/number-theory/problems/848/FRONTIER_NOTE.md +48 -0
  12. package/packs/number-theory/problems/848/LEMMA21_EXPLICIT_BOUND.md +200 -0
  13. package/packs/number-theory/problems/848/LEMMA21_TRUNCATION_SCAN.md +111 -0
  14. package/packs/number-theory/problems/848/LEMMA22_EXPLICIT_BOUND.md +133 -0
  15. package/packs/number-theory/problems/848/LEMMA22_PRIME_COUNT_BOUND.md +58 -0
  16. package/packs/number-theory/problems/848/OPS_DETAILS.yaml +169 -0
  17. package/packs/number-theory/problems/848/PROOF_OBLIGATIONS.md +101 -0
  18. package/packs/number-theory/problems/848/PROPOSITION_EXPLICIT_CANDIDATE.md +69 -0
  19. package/packs/number-theory/problems/848/REPORT_TEMPLATE.md +8 -0
  20. package/packs/number-theory/problems/848/ROUTE_HISTORY.md +24 -0
  21. package/packs/number-theory/problems/848/ROUTE_PACKET.yaml +16 -0
  22. package/packs/number-theory/problems/848/THEOREM_STYLE_EXPLICIT_NOTE.md +91 -0
  23. package/packs/number-theory/problems/848/THRESHOLD_LEDGER.md +132 -0
  24. package/packs/number-theory/problems/848/VERIFICATION_CERTIFICATE_SPEC.md +60 -0
  25. package/packs/number-theory/problems/848/VERIFICATION_REGIMES.md +87 -0
  26. package/packs/number-theory/problems/848/WEAKEST_BRANCH_T250_ASSEMBLY.md +109 -0
  27. package/packs/number-theory/problems/848/WEAKEST_BRANCH_T250_BUDGET.md +107 -0
  28. package/packs/number-theory/problems/848/WEAKEST_CASE_BUDGET.md +183 -0
  29. package/packs/number-theory/problems/848/context.yaml +44 -0
  30. package/problems/848/AGENT_START.md +33 -0
  31. package/problems/848/AGENT_WEBSEARCH_BRIEF.md +21 -0
  32. package/problems/848/CHECKPOINT_NOTES.md +23 -0
  33. package/problems/848/EVIDENCE.md +112 -0
  34. package/problems/848/EXPLICIT_CANDIDATE_REVIEW.md +57 -0
  35. package/problems/848/FORMALIZATION.md +16 -0
  36. package/problems/848/PUBLIC_STATUS_REVIEW.md +16 -0
  37. package/problems/848/REFERENCES.md +25 -0
  38. package/problems/848/ROUTES.md +78 -0
  39. package/problems/848/SHARE_READY_SUMMARY.md +36 -0
  40. package/problems/848/STATEMENT.md +37 -0
  41. package/problems/848/problem.yaml +52 -0
@@ -0,0 +1,16 @@
1
+ route_packet_id: nt848_finite_check_gap_closure_v1
2
+ route_id: finite_check_gap_closure
3
+ frontier_claim: Close the finite decidable gap for Problem 848 while keeping imported threshold progress separate from repo-owned audited claims.
4
+ theorem_module: ""
5
+ checkpoint_packet: CHECKPOINT_TEMPLATE.md
6
+ report_packet: REPORT_TEMPLATE.md
7
+ ready_prompts:
8
+ - What is the best imported explicit `N0` currently visible on the public thread, and how trusted is it?
9
+ - What exact interval should the repo try to certify first in the bounded-verification lane?
10
+ - What certificate format is required before a claimed interval counts as canonically covered?
11
+ - Which public verification attempts should be treated as audit inputs rather than accepted coverage?
12
+ - How should the finite remainder be partitioned into regimes so that methods and trust levels stay visible?
13
+ verification_hook:
14
+ - erdos number-theory status 848
15
+ - erdos number-theory routes 848
16
+ - erdos problem show 848
@@ -0,0 +1,91 @@
1
+ # Problem 848 Theorem-Style Explicit Note
2
+
3
+ This note closes `N848.G1.A12`.
4
+
5
+ ## Statement
6
+
7
+ **Repo explicit candidate.**
8
+
9
+ Let
10
+ - `N >= exp(1420)`,
11
+ - `A subseteq [N]`,
12
+
13
+ and suppose that
14
+ - `ab + 1` is never squarefree for all `a, b in A`,
15
+ - `|A| >= (1/25 - 10^-4) * N`.
16
+
17
+ Then the current repo candidate says:
18
+ - `A` is contained in either the `7 mod 25` class or the `18 mod 25` class.
19
+
20
+ ## Witness parameters
21
+
22
+ The shared witness used throughout the current repo candidate is:
23
+ - truncation value `T = 250`
24
+ - threshold scale `N >= exp(1420)`
25
+ - stability parameter `eta = 10^-4`
26
+
27
+ ## Proof skeleton
28
+
29
+ ### Step 1. Split into the public branches from Sawhney's proof
30
+
31
+ The public proof breaks into the branches whose rounded bounds are:
32
+ - `0.0377`
33
+ - `0.0358`
34
+ - `0.0336`
35
+ - `0.0294`
36
+
37
+ ### Step 2. Use the shared explicit witness
38
+
39
+ The repo now has explicit ledger support for the shared witness:
40
+ - `LEMMA21_EXPLICIT_BOUND.md`
41
+ - `LEMMA21_TRUNCATION_SCAN.md`
42
+ - `LEMMA22_EXPLICIT_BOUND.md`
43
+ - `LEMMA22_PRIME_COUNT_BOUND.md`
44
+ - `CERTIFIED_NUMERICAL_LEDGER.md`
45
+
46
+ These notes provide the explicit replacements for the original `o(1)` and `<<` steps at the
47
+ chosen witness scale.
48
+
49
+ ### Step 3. Close the tightest branch
50
+
51
+ `WEAKEST_BRANCH_T250_ASSEMBLY.md` shows that the tightest public branch retains a certified
52
+ visible reserve of about
53
+ - `2.66e-4`
54
+
55
+ after all currently frozen lemma-level costs and the working choice
56
+ - `eta = 10^-4`.
57
+
58
+ ### Step 4. Check the remaining public branches
59
+
60
+ `BRANCH_COMPARISON_LEDGER.md` shows that the branches `0.0358`, `0.0336`, and `0.0294` all
61
+ retain strictly larger visible reserve than the weakest branch under the same witness.
62
+
63
+ So no new branch obstruction appears at the current explicit level.
64
+
65
+ ### Step 5. Conclude the repo candidate
66
+
67
+ Since every public branch in the proof skeleton is controlled by the same witness, the repo
68
+ arrives at the proposition-level candidate stated above.
69
+
70
+ ## What this note is and is not
71
+
72
+ This note **is**:
73
+ - a theorem-shaped packaging of the current repo candidate
74
+ - a bridge artifact for paper-writer mode
75
+ - a clean summary of the current explicit witness
76
+
77
+ This note is **not yet**:
78
+ - a final publication-ready proof
79
+ - a formal proof-assistant certificate
80
+ - a declaration that Problem 848 is fully solved in the repo
81
+
82
+ ## Remaining gap
83
+
84
+ The remaining work is no longer “find the right witness.”
85
+
86
+ It is:
87
+ - decide whether the current repo candidate is strong enough to publish internally as a public
88
+ review artifact
89
+ - port it into the paper bundle
90
+ - and, if desired, replace the current repo-level interval reasoning with stronger formal or
91
+ machine-checked certification
@@ -0,0 +1,132 @@
1
+ # Problem 848 Threshold Ledger
2
+
3
+ This file records the exact shape of the remaining finite-check gap for Problem 848.
4
+
5
+ It is intentionally conservative:
6
+ - do not promote tentative forum bounds to canonical theorem claims
7
+ - separate existential threshold statements from explicit ones
8
+ - separate sample finite checks from full finite closure
9
+
10
+ ## Current route claim
11
+
12
+ - Publicly established: there exists an integer `N0` such that the desired extremal statement holds for all `N >= N0`.
13
+ - Not yet canonically established here: a complete explicit threshold `N0`, or a finished proof for every `N`.
14
+
15
+ ## Source-backed threshold map
16
+
17
+ ### 1. Proposition 1.1 in Sawhney's note
18
+
19
+ Source:
20
+ - Sawhney, `Problem_848.pdf`, page 1
21
+
22
+ Public statement:
23
+ - There exists an integer `N0` such that for all `N >= N0`, if `A ⊆ [N]` and `ab+1` is never squarefree for all `a,b in A`, then
24
+ `|A| <= |{n in [N] : n ≡ 7 mod 25}|`.
25
+ - Equality is achieved by the `7 mod 25` class and possibly the `18 mod 25` class.
26
+
27
+ Classification:
28
+ - `existential`
29
+
30
+ Why:
31
+ - The theorem statement is explicitly existential.
32
+ - The note does not state a usable numerical `N0`.
33
+
34
+ ### 2. Lemma 2.1
35
+
36
+ Source:
37
+ - Sawhney, `Problem_848.pdf`, page 1
38
+
39
+ Public shape:
40
+ - The lemma gives an asymptotic count with error `<< N (log N)^(-1/2)`.
41
+ - The proof also uses an `N^(o(1))` style term through the product over small primes.
42
+
43
+ Classification:
44
+ - `weakly explicit`
45
+
46
+ Why:
47
+ - The proof architecture is explicit enough in principle to support numerical extraction.
48
+ - The constants are not packaged in the note as a direct computational threshold.
49
+
50
+ ### 3. Lemma 2.2
51
+
52
+ Source:
53
+ - Sawhney, `Problem_848.pdf`, pages 1-2
54
+
55
+ Public shape:
56
+ - The lemma gives an asymptotic estimate for squarefree obstructions on arithmetic progressions with error `<< N / sqrt(log N)`.
57
+
58
+ Classification:
59
+ - `weakly explicit`
60
+
61
+ Why:
62
+ - The structure is explicit in principle.
63
+ - The forum discussion repeatedly identifies this lemma as the harder place to sharpen if one wants a realistic explicit threshold.
64
+
65
+ ### 4. Final casework numerics in the proof
66
+
67
+ Source:
68
+ - Sawhney, `Problem_848.pdf`, pages 2-4
69
+
70
+ Public shape:
71
+ - The proof records rounded numerical bounds such as `0.0377`, `0.0358`, `0.0336`, and `0.0294`.
72
+ - These are used after absorbing `o(1)` errors under the assumption that `N` is sufficiently large.
73
+
74
+ Classification:
75
+ - `explicit case numerics + existential threshold absorption`
76
+
77
+ Why:
78
+ - The local case splits and main-term constants are concrete.
79
+ - The point where the error terms become small enough is still not canonically explicit in the note.
80
+
81
+ ## Public threshold-improvement chatter
82
+
83
+ These are useful research leads, not canonical solved artifacts.
84
+
85
+ ### 5. Forum-level explicit thresholds
86
+
87
+ Source:
88
+ - `erdosproblems.com/forum/thread/848`
89
+
90
+ Publicly mentioned:
91
+ - `exp(1958)` from a GPT-assisted threshold-extraction effort discussed by Terence Tao
92
+ - `exp(1420)` as a later plausible improvement discussed on the same thread
93
+
94
+ Classification:
95
+ - `tentative / not canonically frozen here`
96
+
97
+ Why:
98
+ - These values appear in forum discussion, not in the public theorem statement on the main problem page.
99
+ - The thread itself treats them as intermediate and in need of verification or better writeup.
100
+
101
+ ## Public finite-verification coverage
102
+
103
+ ### 6. Finite checks discussed publicly
104
+
105
+ Source:
106
+ - `erdosproblems.com/forum/thread/848`
107
+
108
+ Publicly mentioned:
109
+ - straightforward approaches only checked the problem up to a few hundred in one discussion branch
110
+ - the public Lean thread claims finite verification for `N = 50` and `N = 100`
111
+
112
+ Classification:
113
+ - `partial finite coverage`
114
+
115
+ Why:
116
+ - This is not a complete all-`N` finite closure.
117
+ - It does, however, show that some finite verification machinery already exists in public.
118
+
119
+ ## Immediate implications
120
+
121
+ - The cleanest honest next step is to turn the existential/weakly-explicit split above into a line-by-line extraction checklist from Sawhney's note.
122
+ - The weakest branch is now isolated in `WEAKEST_CASE_BUDGET.md`, including the exact place where the proof spends rounded branch numerics without yet freezing the usable explicit slack.
123
+ - The repo now also has a conservative numerical freeze of that weakest branch, suggesting the real main-term branch bound is about `0.0376113` with slack about `0.0023887` before analytic error absorption.
124
+ - The second step is to decide whether the best near-term route is:
125
+ - improving Lemma 2.2 and related error terms enough to get a practical explicit `N0`, or
126
+ - treating the current explicit-threshold discussion as support context and investing in bounded finite computation.
127
+
128
+ ## What not to claim yet
129
+
130
+ - Do not claim a canonical explicit threshold `N0`.
131
+ - Do not claim the forum bounds `exp(1958)` or `exp(1420)` are fully verified repo truth.
132
+ - Do not claim the public Lean files already close the entire finite remainder.
@@ -0,0 +1,60 @@
1
+ # Problem 848 Verification Certificate Spec
2
+
3
+ Any bounded-verification claim for Problem `848` should attach a certificate with these fields.
4
+
5
+ ## Required fields
6
+
7
+ - `interval`
8
+ - exact range covered, for example `N = 1..7306`
9
+ - `method_class`
10
+ - one of:
11
+ - `exact_small_n`
12
+ - `structured_breakpoints`
13
+ - `imported_external_computation`
14
+ - `hybrid`
15
+ - `claim_level`
16
+ - one of:
17
+ - `exact`
18
+ - `verified`
19
+ - `external_only`
20
+ - `artifacts`
21
+ - concrete files, repos, scripts, or notes used for the claim
22
+ - `reproduction`
23
+ - how a maintainer can rerun or recheck the claim
24
+ - `failure_mode`
25
+ - what would invalidate the interval claim
26
+ - `audit_status`
27
+ - one of:
28
+ - `repo_audited`
29
+ - `partially_audited`
30
+ - `external_unreviewed`
31
+ - `blocked`
32
+
33
+ ## Strongly preferred fields
34
+
35
+ - `breakpoint_definition`
36
+ - if the method uses breakpoint sufficiency, define exactly what the breakpoints are
37
+ - `monotonicity_justification`
38
+ - if interval coverage is inferred between checkpoints, explain why
39
+ - `independent_check`
40
+ - a second script, proof note, or reviewer confirmation
41
+ - `cost_profile`
42
+ - rough runtime or proof complexity
43
+
44
+ ## Rejection triggers
45
+
46
+ Do not count a range as canonically covered if any of the following is true:
47
+
48
+ - the claim silently uses the wrong asymptotic handoff threshold
49
+ - the method covers only sample points but is presented as interval coverage
50
+ - a breakpoint argument is used without a monotonicity justification
51
+ - the computation is public but explicitly criticized as unverified or likely incorrect and no
52
+ repo audit has answered that criticism
53
+ - the result cannot be rerun or inspected by a future maintainer
54
+
55
+ ## Why this matters here
56
+
57
+ The public thread already contains one verification attempt that was later corrected and
58
+ criticized as difficult to verify. That does not make bounded verification hopeless. It does
59
+ mean this repo should demand interval certificates rather than encouraging "I think this
60
+ covers everything up to X" style claims.
@@ -0,0 +1,87 @@
1
+ # Problem 848 Verification Regimes
2
+
3
+ This file partitions the finite remainder into regimes so the repo can track progress
4
+ without pretending that one method fits the whole gap.
5
+
6
+ ## Trusted public asymptotic handoff
7
+
8
+ - public theorem: Sawhney proves the statement for all sufficiently large `N`
9
+ - imported explicit threshold timeline:
10
+ - `7 x 10^17` on 2026-03-21
11
+ - `3.3 x 10^17` on 2026-03-22
12
+ - `2.64 x 10^17` on 2026-03-23
13
+ - current repo posture:
14
+ - these thresholds are imported public claims
15
+ - they size the finite remainder operationally
16
+ - they are not yet promoted to canonical repo-owned theorem statements
17
+
18
+ ## Verification regime split
19
+
20
+ ### Regime A: exact small-`N` coverage
21
+
22
+ Goal:
23
+ - cover a small base interval by exact methods that can be rerun and independently checked
24
+
25
+ Candidate methods:
26
+ - direct search
27
+ - pair-exchange lemmas
28
+ - exact residue-structure enumeration
29
+ - very small witness-prime case splits
30
+
31
+ Desired certificate:
32
+ - exact witness/counterexample status for each `N`
33
+ - reproducible script or proof note
34
+
35
+ ### Regime B: structured breakpoint verification
36
+
37
+ Goal:
38
+ - cover a medium interval by checking a monotone or breakpoint-sufficient inequality rather
39
+ than every raw instance independently
40
+
41
+ Candidate methods:
42
+ - structural breakpoint tables
43
+ - clique/exchange inequalities
44
+ - monotonicity-ledger arguments
45
+
46
+ Desired certificate:
47
+ - exact breakpoint set definition
48
+ - proof that breakpoint coverage implies interval coverage
49
+ - machine-readable result table
50
+
51
+ ### Regime C: audited imported computation
52
+
53
+ Goal:
54
+ - record public computational claims without treating them as canonical until the repo has an
55
+ audit story
56
+
57
+ Candidate inputs:
58
+ - public repos
59
+ - public verification notes
60
+ - independently rerun scripts
61
+
62
+ Desired certificate:
63
+ - imported source URL
64
+ - exact claimed interval
65
+ - audit outcome: accepted, external-only, or blocked
66
+
67
+ ### Regime D: asymptotic handoff
68
+
69
+ Goal:
70
+ - state the point above which the public theorem takes over
71
+
72
+ Desired certificate:
73
+ - cited theorem source
74
+ - exact threshold assumption being used operationally
75
+ - note whether the threshold is imported-only or repo-audited
76
+
77
+ ## Current honest posture
78
+
79
+ - Regime A: not frozen in this repo
80
+ - Regime B: not frozen in this repo
81
+ - Regime C: public attempts exist, but some were explicitly criticized on the forum as
82
+ difficult to verify or likely incorrect
83
+ - Regime D: public asymptotic theorem exists; imported explicit thresholds are tracked but not
84
+ yet repo-audited
85
+
86
+ So the next honest move is to freeze the certificate format before claiming any new verified
87
+ interval.
@@ -0,0 +1,109 @@
1
+ # Problem 848 Weakest Branch Assembly at `T = 250`
2
+
3
+ This note closes `N848.G1.A7`.
4
+
5
+ Goal:
6
+ - turn the `T = 250` weakest-branch witness budget into a line-by-line branch ledger
7
+ - freeze an honest working `eta` value for this branch
8
+
9
+ Scope:
10
+ - this is only the weakest public `0.0377` branch
11
+ - this is not yet a full explicit-threshold proof for Proposition 1.1
12
+ - the remaining repo question is whether the same witness closes the other public branches
13
+
14
+ ## Branch setup
15
+
16
+ Assume:
17
+ - `N >= exp(1420)`
18
+ - `eta > 0`
19
+ - `|A| >= (1/25 - eta) * N`
20
+ - the branch with an even element `b in A* = A \\ (A7 union A18)` is active
21
+ - truncation witness `T = 250`
22
+
23
+ ## Line-by-line upper bound ledger
24
+
25
+ ### 1. `A*` main term
26
+
27
+ From `WEAKEST_CASE_BUDGET.md`:
28
+ - `A* / N <= 0.0251587645... + remainder`
29
+
30
+ ### 2. `A*` explicit remainder
31
+
32
+ From `LEMMA21_TRUNCATION_SCAN.md`:
33
+ - `A*` tail density at `T = 250`: about `0.0005641453`
34
+ - `A*` discrete term: `23 * (3^23 - 1) / N`
35
+
36
+ At `N >= exp(1420)`, the discrete term is astronomically small and far below the visible
37
+ decimal budget.
38
+
39
+ ### 3. `A7 union A18` main term
40
+
41
+ From `WEAKEST_CASE_BUDGET.md`:
42
+ - `(A7 union A18) / N <= 0.0124525434... + remainder`
43
+
44
+ ### 4. `A7 union A18` explicit remainder
45
+
46
+ From `LEMMA22_EXPLICIT_BOUND.md` and `LEMMA22_PRIME_COUNT_BOUND.md`:
47
+ - Lemma 2.2 `N / p^2` tail density at `T = 250`: about `0.0000491054`
48
+ - Lemma 2.2 prime-count term at `N >= exp(1420)`: at most `0.0014095427`
49
+ - Lemma 2.2 discrete term: `2 * (2^51 - 1) / N`
50
+
51
+ Again, the discrete term is astronomically small at `N >= exp(1420)`.
52
+
53
+ ## Combined explicit branch bound
54
+
55
+ Collecting the frozen decimal contributions gives
56
+
57
+ - branch main term: `0.0376113079`
58
+ - `A*` tail: `0.0005641453`
59
+ - Lemma 2.2 tail: `0.0000491054`
60
+ - Lemma 2.2 prime-count term: `0.0014095427`
61
+
62
+ So the visible explicit branch bound is
63
+
64
+ - `0.0376113079 + 0.0005641453 + 0.0000491054 + 0.0014095427`
65
+ - `= 0.0396341013` up to rounding in the displayed decimals
66
+
67
+ This leaves visible room to `1/25 = 0.04` of about
68
+
69
+ - `0.04 - 0.0396341013 = 0.0003658987`.
70
+
71
+ ## Working `eta` choice
72
+
73
+ The branch contradiction only needs a positive margin after paying for `eta`.
74
+
75
+ A conservative working choice is
76
+
77
+ - `eta_work = 0.0001`.
78
+
79
+ Then the remaining visible reserve is still about
80
+
81
+ - `0.0003658987 - 0.0001 = 0.0002658987`.
82
+
83
+ So with this working choice, the branch still retains about `2.66e-4` of visible room for
84
+ the tiny discrete terms and any final rounding/bookkeeping losses.
85
+
86
+ ## Honest branch conclusion
87
+
88
+ At the witness scale
89
+ - `N >= exp(1420)`,
90
+ - `T = 250`,
91
+ - `eta = 10^-4`,
92
+
93
+ the weakest public branch now appears explicitly contradictory.
94
+
95
+ What this does **not** yet prove:
96
+ - that `exp(1420)` is a fully verified threshold for the whole proposition
97
+ - that the stronger public candidate thresholds are unnecessary
98
+ - that every other public branch has already been checked with the same explicit witness
99
+
100
+ What it **does** prove for the repo route:
101
+ - the weakest public branch is no longer the blocker
102
+ - the repo now has a concrete explicit branch witness with positive visible reserve
103
+
104
+ ## Next route consequence
105
+
106
+ The next honest move is:
107
+ - carry the same witness philosophy into the other public proof branches
108
+ - check whether `T = 250`, `N >= exp(1420)`, and `eta = 10^-4` also close them
109
+ - if one branch needs a different witness, record that precisely instead of forcing uniformity
@@ -0,0 +1,107 @@
1
+ # Problem 848 Weakest Branch Budget at `T = 250`
2
+
3
+ This note closes `N848.G1.A6` at a witness-budget level.
4
+
5
+ Goal:
6
+ - test whether the weakest public `0.0377` branch is still blocked once both Lemma 2.1 and
7
+ Lemma 2.2 use a larger witness truncation parameter
8
+
9
+ Witness choice:
10
+ - `T = 250`
11
+
12
+ Reason for this choice:
13
+ - it is large enough to shrink the live `A*` tail materially
14
+ - it is still tiny compared with the public candidate scales `exp(1420)` and `exp(1958)`
15
+ - the discrete inclusion-exclusion terms remain negligible at those scales
16
+
17
+ ## Frozen main-term branch data
18
+
19
+ From `WEAKEST_CASE_BUDGET.md`:
20
+ - `A*` main term: about `0.0251587645`
21
+ - `A7 union A18` main term: about `0.0124525434`
22
+ - combined weakest-branch main term: about `0.0376113079`
23
+ - branch slack to `1/25 = 0.04`: about `0.0023886921`
24
+
25
+ ## Explicit remainder ledger at `T = 250`
26
+
27
+ ### 1. `A*` via Lemma 2.1
28
+
29
+ From `LEMMA21_TRUNCATION_SCAN.md`:
30
+ - `A*` tail density at `T = 250`: about `0.0005641453`
31
+ - `A*` discrete term: `23 * (3^23 - 1) / N`
32
+
33
+ At `N = exp(1420)`:
34
+ - the `A*` discrete density is below about `exp(-1392)`
35
+
36
+ ### 2. `A7 union A18` via Lemma 2.2
37
+
38
+ From `LEMMA22_EXPLICIT_BOUND.md`:
39
+ - Lemma 2.2 tail density at `T = 250`: about `0.0000491054`
40
+ - worst-case Lemma 2.2 discrete term: `2 * (2^51 - 1) / N`
41
+ - prime-count term from `LEMMA22_PRIME_COUNT_BOUND.md`: at most `0.0014095427` for
42
+ every `N >= exp(1420)`
43
+
44
+ At `N = exp(1420)`:
45
+ - the Lemma 2.2 discrete density is below about `exp(-1384)`
46
+
47
+ ### 3. Combined explicit remainder
48
+
49
+ Adding the two live tail terms gives
50
+
51
+ - combined tail density about `0.0006132507`
52
+
53
+ and the combined discrete terms are still negligible at the public candidate scales.
54
+
55
+ What is still missing:
56
+ - no further lemma-level tail term; the remaining work is branch assembly and `eta`
57
+
58
+ ## Combined weakest-branch budget
59
+
60
+ Main term plus the live explicit tails:
61
+
62
+ - `0.0376113079 + 0.0006132507 = 0.0382245586`
63
+
64
+ So the remaining room to `0.04` is still about
65
+
66
+ - `0.0017754414`
67
+
68
+ before the final branch bookkeeping.
69
+
70
+ After inserting the explicit Lemma 2.2 prime-count bound at `N >= exp(1420)`,
71
+
72
+ - `0.0017754414 - 0.0014095427 ~= 0.0003658987`
73
+
74
+ So the currently visible room for
75
+ - the final `eta` choice
76
+ - and any remaining line-by-line bookkeeping losses
77
+
78
+ is about `3.66e-4`.
79
+
80
+ ## Honest reading
81
+
82
+ This does **not** yet prove an explicit threshold.
83
+
84
+ What it **does** show is:
85
+ - once `T` is allowed to move, the weakest branch no longer looks blocked by the two lemma
86
+ `N / p^2` tails themselves
87
+ - the discrete inclusion-exclusion losses are no longer the issue
88
+ - the Lemma 2.2 prime-count term also fits inside the branch budget at the public candidate
89
+ threshold scale
90
+ - the route now has a concrete surviving witness margin of about `3.66e-4` for final
91
+ `eta` and bookkeeping losses
92
+
93
+ So the live unresolved work is narrower than before:
94
+ - write the line-by-line full branch assembly with the larger `T`
95
+ - record the exact `eta` room that survives that assembly
96
+ - then turn that into a genuine explicit-threshold witness candidate
97
+
98
+ ## Route consequence
99
+
100
+ This means the current proof skeleton now looks plausibly explicitizable in the weakest
101
+ branch at the witness scale `N >= exp(1420)`, provided the remaining line-by-line assembly
102
+ does not consume more than about `3.66e-4` of density.
103
+
104
+ That is a materially stronger posture than the one the repo started with:
105
+ - the route is no longer waiting on a mystery bottleneck
106
+ - it has a concrete witness truncation value
107
+ - and it has a concrete surviving witness margin after all currently frozen lemma-level costs