prime-grokking.git/tests/test_phase3_flags.py, branch main
Prime Grokking — can minimal architectures grok next-prime? Pre-registered negative-class experiment (weight-tied RNN vs transformer).
http://git.jayrup.me/c/prime-grokking.git/atom?h=main
2026-08-20T16:02:15Z
fix(eval): correct sieve-rank indexing + test expectations
2026-08-20T16:02:15Z
Void Agent
void@jayrup.hermes
2026-08-20T16:02:15Z
urn:sha1:cf83937689bb30e2b5fa6e3efaa2f115016a030b
- _compute_sieve_rank: find LARGEST k (not smallest) whose signature
contains all error preds — fixes P5(4) vs P5(1) bug
- _sieve_rank_signature: iterate all small_primes (not just p²≤n) to
catch composites like 209=11*19 where 11²>209
- Test expectations updated for [101,200] range (209 outside it)
- is_prime task: P1→P3 (no sieve-rank for classification tasks)
48/48 green.
fix D2: integers-mode probe is N/A by construction (OOV probe inputs), functional regression test; D2 scored (int tokens collapse task: O2, 0-13% vs digits 17-87%); NOTES + report Phase 4 updated; 42 tests
2026-08-17T14:26:16Z
Void Agent
void@jayrup.hermes
2026-08-17T14:26:16Z
urn:sha1:535bb1dcf727e2273b956553c0491ec80ad8ec98
phase3: task_mode (is_prime), train_frac, lr_decay flags + tests (41 green); Addendum 5 locked; 11-job batch
2026-08-16T13:41:54Z
Void Agent
void@jayrup.hermes
2026-08-16T13:41:54Z
urn:sha1:751cbe0d93af1fcc69147d27ca8babd63105e4dc