erdos-problems 0.3.3 → 0.3.5
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/package.json +1 -1
- package/packs/number-theory/problems/848/BOUNDED_VERIFICATION_PLAN.md +4 -0
- package/packs/number-theory/problems/848/EXACT_SMALL_N_1_3000_CERTIFICATE.md +55 -0
- package/packs/number-theory/problems/848/EXACT_SMALL_N_1_3000_RESULTS.json +213791 -0
- package/packs/number-theory/problems/848/FRONTIER_NOTE.md +2 -0
- package/packs/number-theory/problems/848/INTERVAL_WORK_QUEUE.yaml +43 -0
- package/packs/number-theory/problems/848/OPERATIONAL_THRESHOLD_POSTURE.md +38 -0
- package/packs/number-theory/problems/848/OPS_DETAILS.yaml +36 -8
- package/packs/number-theory/problems/848/ROUTE_HISTORY.md +5 -2
- package/packs/number-theory/problems/848/ROUTE_PACKET.yaml +1 -0
- package/packs/number-theory/problems/848/VERIFICATION_REGIMES.md +8 -3
- package/packs/number-theory/problems/848/compute/problem848_small_n_exact_scan.mjs +170 -0
- package/packs/number-theory/problems/848/context.yaml +8 -4
- package/problems/848/EVIDENCE.md +9 -1
- package/problems/848/ROUTES.md +5 -1
- package/problems/848/SHARE_READY_SUMMARY.md +1 -0
package/package.json
CHANGED
|
@@ -37,6 +37,10 @@ What success would look like:
|
|
|
37
37
|
- imported public verification work is either accepted with an audit note or left external
|
|
38
38
|
- the remaining uncovered range shrinks monotonically
|
|
39
39
|
|
|
40
|
+
Current progress:
|
|
41
|
+
- the repo now has an exact small-`N` certificate for `1..3000`
|
|
42
|
+
- a direct jump to `1..5000` no longer looks cheap enough to treat as the default next move
|
|
43
|
+
|
|
40
44
|
What this lane is not:
|
|
41
45
|
- not brute force to `2.64 x 10^17`
|
|
42
46
|
- not an automatic endorsement of every public verification claim
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
# Problem 848 Exact Small-`N` Certificate: `1..3000`
|
|
2
|
+
|
|
3
|
+
This is the first exact bounded-verification certificate frozen in the repo for Problem `848`.
|
|
4
|
+
|
|
5
|
+
## Claim
|
|
6
|
+
|
|
7
|
+
For every `N` with `1 <= N <= 3000`, the maximum size of a set `A subseteq [N]` such that
|
|
8
|
+
`ab + 1` is never squarefree for all `a, b in A` is equal to the size of the `7 mod 25`
|
|
9
|
+
or `18 mod 25` residue class in `[N]`.
|
|
10
|
+
|
|
11
|
+
This certificate only covers the interval `1..3000`.
|
|
12
|
+
|
|
13
|
+
## Method class
|
|
14
|
+
|
|
15
|
+
- `exact_small_n`
|
|
16
|
+
|
|
17
|
+
## Reproduction
|
|
18
|
+
|
|
19
|
+
Command used:
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
node packs/number-theory/problems/848/compute/problem848_small_n_exact_scan.mjs \
|
|
23
|
+
--min 1 \
|
|
24
|
+
--max 3000 \
|
|
25
|
+
--json-output packs/number-theory/problems/848/EXACT_SMALL_N_1_3000_RESULTS.json
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
The script:
|
|
29
|
+
- filters vertices by the loop condition `a^2 + 1` not squarefree
|
|
30
|
+
- builds the compatibility graph where `a` and `b` are adjacent exactly when `ab + 1` is not
|
|
31
|
+
squarefree
|
|
32
|
+
- computes an exact maximum clique for each `N`
|
|
33
|
+
- compares that maximum clique size against the `7 mod 25` class size
|
|
34
|
+
|
|
35
|
+
## Outcome
|
|
36
|
+
|
|
37
|
+
- interval: `1..3000`
|
|
38
|
+
- result: verified
|
|
39
|
+
- every scanned `N` satisfied:
|
|
40
|
+
- `max_clique_size = max(|{n in [N] : n equiv 7 mod 25}|, |{n in [N] : n equiv 18 mod 25}|)`
|
|
41
|
+
|
|
42
|
+
The machine-readable result packet is:
|
|
43
|
+
- `EXACT_SMALL_N_1_3000_RESULTS.json`
|
|
44
|
+
|
|
45
|
+
## Scope warning
|
|
46
|
+
|
|
47
|
+
This does **not** certify anything above `3000`.
|
|
48
|
+
It is a base interval certificate only.
|
|
49
|
+
|
|
50
|
+
## Why this interval matters
|
|
51
|
+
|
|
52
|
+
- it creates a real in-repo covered interval, not just a verification plan
|
|
53
|
+
- it is large enough to be a meaningful finite-check foothold
|
|
54
|
+
- it does not rely on disputed public computation
|
|
55
|
+
- it gives the bounded-verification lane a concrete certificate format and reproduction path
|