erdos-problems 0.3.4 → 0.3.5

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

@@ -47,4 +47,4 @@ Read next:
 - `VERIFICATION_CERTIFICATE_SPEC.md`
 - `EXTERNAL_VERIFICATION_LEDGER.md`
 - `INTERVAL_WORK_QUEUE.yaml`
-- `EXACT_SMALL_N_1_2000_CERTIFICATE.md`
+- `EXACT_SMALL_N_1_3000_CERTIFICATE.md`

package/packs/number-theory/problems/848/INTERVAL_WORK_QUEUE.yaml

@@ -7,22 +7,22 @@ operational_threshold:
 intervals:
   - interval_id: N848.V1
     label: exact_small_n_base_interval
-    range: "1..2000"
+    range: "1..3000"
     status: done
     method_class: exact_small_n
     claim_level: verified
-    certificate: EXACT_SMALL_N_1_2000_CERTIFICATE.md
-    data_packet: EXACT_SMALL_N_1_2000_RESULTS.json
-    next_move: Use this as the first trusted base interval and decide whether the next extension is another exact interval or an imported-computation audit.
+    certificate: EXACT_SMALL_N_1_3000_CERTIFICATE.md
+    data_packet: EXACT_SMALL_N_1_3000_RESULTS.json
+    next_move: Use this as the current trusted base interval and decide whether the next extension is another exact interval or an imported-computation audit.
   - interval_id: N848.V2
     label: exact_small_n_extension
-    range: "2001..?"
+    range: "3001..?"
     status: ready
     method_class: exact_small_n
     claim_level: target
     certificate: ""
     data_packet: ""
-    next_move: Decide how far the exact clique scan can be pushed before a different method class is needed.
+    next_move: Decide whether exact coverage should continue in smaller certified steps beyond `3000` or whether the next gain should come from a different method class.
   - interval_id: N848.V3
     label: imported_computation_audit
     range: "public_claimed_interval"

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

@@ -6,7 +6,7 @@ routes:
     status: active
     summary: Convert the sufficiently-large-N theorem into a complete all-N resolution without overstating what is already closed or confusing imported thresholds with repo-owned claims.
     why_now: The share package is already committed, the bounded-verification lane is now frozen, and the repo has a first verified interval.
-    next_move: Decide whether to extend exact verified coverage beyond `2000` or switch method class.
+    next_move: Decide whether to extend exact verified coverage beyond `3000` in smaller steps or switch method class.
   - route_id: external_threshold_tracking
     title: External Threshold Tracking
     status: support
@@ -18,7 +18,7 @@ routes:
     status: active_support
     summary: Reduce the finite remainder directly once a threshold is trusted enough to be operationally useful.
     why_now: Lowering `N0` matters because it reduces this lane, not because "smallest threshold" is the whole problem.
-    next_move: Build on the exact `1..2000` base interval and decide the next extension rule.
+    next_move: Build on the exact `1..3000` base interval and decide the next extension rule.
   - route_id: formalization_coverage_audit
     title: Formalization Coverage Audit
     status: support
@@ -30,9 +30,9 @@ tickets:
     title: Close the decidable gap without confusing imported threshold progress and repo-owned candidate work
     route_id: finite_check_gap_closure
     status: active
-    summary: The repo now has a committed review package for its audited `exp(1420)` candidate, a chosen bounded-verification lane, and an exact verified base interval `1..2000`. The live question is how to extend coverage from that foothold.
-    current_blocker: The repo has not yet chosen whether the next interval extension should stay in the exact clique-scan regime or switch to a different verification method.
-    next_move: Close `N848.G1.A21`.
+    summary: The repo now has a committed review package for its audited `exp(1420)` candidate, a chosen bounded-verification lane, and an exact verified base interval `1..3000`. The live question is how to extend coverage from that foothold without pretending brute-force still scales cheaply.
+    current_blocker: The repo has not yet chosen whether the next interval extension should stay in the exact clique-scan regime in smaller certified steps or switch to a different verification method.
+    next_move: Close `N848.G1.A22`.
   - ticket_id: N848F
     title: Audit public formalization coverage
     route_id: formalization_coverage_audit
@@ -182,9 +182,16 @@ atoms:
     summary: The repo now has a reproducible exact certificate showing that the conjectured extremal size is correct for every `N` in `1..2000`.
     next_move: Decide whether to extend the exact clique scan beyond `2000` or change method class.
   - atom_id: N848.G1.A21
-    title: Choose the next verified interval extension beyond `2000`
+    title: Extend the exact verified base interval beyond `2000`
+    route_id: finite_check_gap_closure
+    ticket_id: N848
+    status: done
+    summary: The repo now has a second exact certificate extending the bounded-verification base interval from `1..2000` to `1..3000`, while also showing that a blind jump to `1..5000` is no longer cheap enough to count as the default next move.
+    next_move: Choose the post-`3000` extension policy.
+  - atom_id: N848.G1.A22
+    title: Choose the post-`3000` verified interval policy
     route_id: finite_check_gap_closure
     ticket_id: N848
     status: ready
-    summary: The bounded-verification lane now starts from a real certified base interval `1..2000`. The next choice is whether the exact clique scan still has enough headroom to extend that base efficiently, or whether the next gain should come from breakpoint or audit methods.
-    next_move: Decide whether to extend exact verified coverage beyond `2000` or switch method class.
+    summary: The bounded-verification lane now starts from a real certified base interval `1..3000`. The next choice is whether exact coverage should continue in smaller certified steps, or whether the next gain should come from breakpoint or audit methods.
+    next_move: Decide whether to extend exact verified coverage beyond `3000` in smaller steps or switch method class.

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

@@ -22,5 +22,6 @@
 - Nineteenth refinement: choose bounded finite verification as the next closure lane and freeze the first repo artifacts for regimes, certificates, and external verification audit.
 - Twentieth refinement: freeze the operational threshold posture so imported `N0` claims can size the finite remainder without being silently promoted to canonical repo theorem truth.
 - Twenty-first refinement: certify the exact interval `1..2000` by a reproducible maximum-clique scan, giving the bounded-verification lane its first genuine covered interval.
-- Current public pack posture: active route `finite_check_gap_closure`, with asymptotic theorem already in hand, a committed audited candidate package in the repo, and a real exact base interval `1..2000` now covered in the bounded-verification lane.
-- Next maturity threshold: extend verified interval coverage beyond `2000` in the most efficient trustworthy way.
+- Twenty-second refinement: extend the exact certificate to `1..3000`, and record that a direct jump to `1..5000` no longer looks cheap enough to treat as the obvious default next move.
+- Current public pack posture: active route `finite_check_gap_closure`, with asymptotic theorem already in hand, a committed audited candidate package in the repo, and a real exact base interval `1..3000` now covered in the bounded-verification lane.
+- Next maturity threshold: choose the post-`3000` extension policy in the most efficient trustworthy way.

package/packs/number-theory/problems/848/VERIFICATION_REGIMES.md

@@ -76,8 +76,10 @@ Desired certificate:
 
 ## Current honest posture
 
-- Regime A: first exact interval `1..2000` is now frozen in the repo with a reproducible
+- Regime A: first exact interval `1..3000` is now frozen in the repo with a reproducible
   maximum-clique certificate
+- Regime A warning: a direct jump to `1..5000` did not finish cheaply enough to treat blind
+  brute-force extension as the only serious next move
 - Regime B: not frozen in this repo
 - Regime C: public attempts exist, but some were explicitly criticized on the forum as
   difficult to verify or likely incorrect
@@ -85,5 +87,6 @@ Desired certificate:
   yet repo-audited
 
 So the next honest move is to decide whether exact-small-`N` coverage should be extended
-directly beyond `2000`, or whether the next gain comes from auditing imported computation or
+directly beyond `3000` in smaller certified steps, or whether the next gain comes from
+auditing imported computation or
 switching method class.

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

@@ -3,11 +3,11 @@ family_role: finite_check_number_theory_workspace
 harness_profile: decidable_gap_workspace
 default_active_route: finite_check_gap_closure
 bootstrap_focus: Treat Problem 848 as a finite-gap closure problem and freeze the certificate surface before claiming bounded verification progress.
-route_story: Problem 848 is already asymptotically resolved in public, but not yet closed here for all N. The honest job is to shrink the finite remainder with audited threshold tracking and reproducible bounded verification, beginning from the verified base interval `1..2000`.
+route_story: Problem 848 is already asymptotically resolved in public, but not yet closed here for all N. The honest job is to shrink the finite remainder with audited threshold tracking and reproducible bounded verification, beginning from the verified base interval `1..3000`.
 frontier_label: finite_check_gap_closure
-frontier_detail: The repo now has a verified exact interval `1..2000`; the next question is whether to extend that exact scan further or change method class.
+frontier_detail: The repo now has a verified exact interval `1..3000`; an attempted jump to `5000` did not clear quickly enough to count as cheap progress, so the next question is whether to extend exact coverage in smaller steps or change method class.
 checkpoint_focus: Preserve the distinction between existential N0, explicit N0, sample finite checks, and full closure.
-next_honest_move: Decide whether to extend the exact clique scan beyond `2000` or pivot to a different bounded-verification method.
+next_honest_move: Decide whether to extend the exact clique scan beyond `3000` in smaller certified steps or pivot to a different bounded-verification method.
 related_core_problems:
   - "844"
 literature_focus:
@@ -27,7 +27,7 @@ artifact_focus:
   - VERIFICATION_CERTIFICATE_SPEC.md
   - EXTERNAL_VERIFICATION_LEDGER.md
   - INTERVAL_WORK_QUEUE.yaml
-  - EXACT_SMALL_N_1_2000_CERTIFICATE.md
+  - EXACT_SMALL_N_1_3000_CERTIFICATE.md
 question_ledger:
   open_questions:
     - Which imported threshold value is trusted enough to size the finite remainder operationally?
@@ -44,5 +44,5 @@ question_ledger:
     - The threshold ledger separating existential and explicit claims is now frozen.
     - The repo now has an audited explicit candidate package distinct from the imported public threshold timeline.
     - The repo has now chosen bounded finite verification as the next closure lane.
-    - The repo now has an exact verified base interval `1..2000`.
+    - The repo now has an exact verified base interval `1..3000`.
   problem_solved: []

package/problems/848/EVIDENCE.md

@@ -74,7 +74,9 @@ Current public evidence captured locally:
   values to size the finite remainder without being silently promoted to canonical theorem
   truth.
 - A reproducible exact maximum-clique scan now verifies the expected extremal size for every
-  `N` in `1..2000`, giving the bounded-verification lane its first trusted covered interval.
+  `N` in `1..3000`, giving the bounded-verification lane a larger trusted covered interval.
+- An exploratory jump to `1..5000` no longer looks cheap enough to treat blind brute-force
+  extension as the default next move.
 
 Claim-safe local posture:
 - Exact: the public status is `decidable`, not `open` and not fully `solved`.
@@ -114,5 +116,5 @@ Next maintainer step:
 - preserve the current claim-safe package as a clean review unit
 - treat imported threshold improvements as external progress markers unless they are
   re-audited inside the repo
-- decide whether exact verified coverage should be extended beyond `2000` or whether the
-  next gain now needs a different method class
+- decide whether exact verified coverage should be extended beyond `3000` in smaller steps
+  or whether the next gain now needs a different method class

package/problems/848/ROUTES.md

@@ -74,8 +74,9 @@
   - a regime split for the finite remainder
   - a certificate format for bounded interval claims
   - an audit ledger for imported verification work
-  - an exact verified base interval `1..2000`
+  - an exact verified base interval `1..3000`
 - The next concrete task is to decide whether the exact clique scan should be extended
-  directly beyond `2000` or whether the next gain now needs a different method class.
+  directly beyond `3000` in smaller steps or whether the next gain now needs a different
+  method class.
 - The right optimization target remains the size of the remaining finite gap, not the
   threshold race in isolation.

package/problems/848/SHARE_READY_SUMMARY.md

@@ -23,7 +23,7 @@ What is ready now:
 - supporting explicit ledgers for the branch bounds and numerical witness
 - a bounded finite-verification lane with regimes, certificate requirements, and external
   audit notes
-- an exact verified base interval `1..2000`
+- an exact verified base interval `1..3000`
 
 What is not being claimed:
 - not full all-`N` closure in the repo