Checked progress
Specialists propose deductions with evidence. The checker authorizes changes to the Sudoku state. A promising prediction never becomes a truth rule.
CURRENT VERIFIED STATUS · 12 SEP 2026 · FINAL BOUNDED CUT
Master 5/5 PASS · selftest 444/444 with 3 allowed SKIP · smoke 4/4 PASS · P1/P2/P3 PASS. The final extract contains 467 unique runtime task IDs: 335 SOLVED and 132 LIMIT.
The arena is now STANDBY. Protected/long scientific campaign executions remain 0; scientific_final=false and semantic proof replay remains NOT_RUN. This is bounded engineering acceptance, not a scientific-superiority claim. Final bounded evidence →
The Python arena now runs the experiment: choose a representation, fund a specialist, check its result and retain reusable proof. The next question is measurable: when do MDL predictions, DCC allocation and learned experience reduce the total work needed to solve?
R6 brings multiple representations and a proof-checking runtime into one arena. HF3 adds matched causal controls, reliable recovery and terminal learning. The HF1 hotfix delivers the new long-campaign orchestration, Windows launch fixes and a compact local program package.
Specialists propose deductions with evidence. The checker authorizes changes to the Sudoku state. A promising prediction never becomes a truth rule.
Compact checkpoints preserve progress. Resume and completed-run no-op checks protect the learning record from duplicate terminal updates.
One status line shows the time, stage, completed work and approximate ETA. FAST LIVE exports a verifiable snapshot while the experiment continues.
The program distribution is about 2.8 MB and contains 214 files: code, launchers, tests and required local data. Historical campaign archives are excluded.
The HF3 pilot confirmed that strong classical strategies remain serious competitors. R6 gives the controller a richer choice: change the mathematical view, select a specialist or use ordinary search. The arena records the cost of that choice so a more elaborate method has to earn its place.
Evaluate method × representation × scale × state regime, not a single scalar leaderboard.
MDL is attached to an actually encoded proof or choice stream with a decoder and verification cost.
Convert expensive verified discovery into a compact macro plus a cheap matcher that can be reused later.
Choose whether to continue, switch view, change scale, fund a specialist, or do nothing beyond baseline work.
Evaluate actual player actions using verifiable explanations and a frozen reference proof language.
The Python arena tests mechanisms before browser integration. The playable web app keeps its own Logic/Trace engine; HF3 is not silently substituted into the game.
R6 explicitly charges representation construction, feature extraction, failed proposals, checking, learning and persistence. Views are not built for free before selection.
MDL models predict which work may pay off. DCC adjusts allocation using feedback. Both operate within a declared work budget.
A specialist supplies a proof or an exact search result. Independent checks validate deductions and completed grids; an exhausted budget remains an explicit limit.
Verified proof patterns can enter the Atlas. Learning updates are recorded once, with the cost of matching, checking and persistence included.
Compile bounded count and linear relations into exact certificates, then distil recurring relations into Atlas matchers.
Lift Sudoku into a 9×9×9 candidate cube with cell, row–digit, column–digit and box–digit projections.
Use exact single-digit path structure, PATH_DAG queries, joint GLOBAL9 models and paid branch-ranking experiments.
The new long experiment includes strong classical search strategies. The arena also implements an Algorithm X exact-cover reference using copied sets. Dancing-links DLX and certified SAT/CDCL remain reference targets from the earlier architecture, not delivered long-study arms.
Connecting equal digits across rows first looked like a picture. R6 turns that picture into a concrete family of representations with explicit codecs, exact queries and causal branch-ordering tests.
Pattern → Path → Exact queries → Joint codec → Predictive signal → Causal search
G_coupling = L_independent(Y | D) − L_joint(Y | D), with model/codebook/library/framing costs charged on both sides.
Shorter path description is not a truth rule. It becomes useful only if it predicts or causally improves verified search under matched cost and information.
Reference proof bits are meaningful only inside a frozen proof language and codebook. Runtime, library cost and decoder work remain visible.
A beautiful macro that is expensive to recognize may compress storage without reducing solving work. R6 measures both.
Atlas entries are canonicalized across declared Sudoku symmetries so the library does not fill with equivalent positional copies.
Store verified forbidden combinations separately from completed “nothing found” scans; both retain exact scope and dependency conditions.
Representation/program search, compilation, canonicalization, failed candidates and maintenance are included in the system account.
Measure value with ablation and replacement-aware contribution, not just isolated leaderboard rank or editorial enthusiasm.
The HF3 HF1 long launcher runs a frozen causal design with fresh development seeds.
It compares the same puzzles and declared checkpoint/service contract, then asks separately whether
training helps on unseen evaluation puzzles. This is a development experiment with protected=false.
Combined MDL + DCC; DCC with the same actuator; a constant predictor with the matched actuator; MDL with a fixed schedule; Sticky; Structural; seeded MRV; and Luby restarts.
Train sequentially with ONLINE_PREQUENTIAL, then freeze learning. Compare fresh and trained states on the same EVAL puzzles. Training and evaluation are separated under the declared identity and symmetry checks.
UNIQUE_28 and UNIQUE_24 use 28 and 24 givens. Main comparisons share the 24-million-WU budget and compact checkpoint/service settings. Fewer givens alone do not certify greater human difficulty.
Context UCB runs on every fourth qualified evaluation puzzle. Its earlier service-finalization limits can be investigated without making it half the experiment.
MDL_DCC, DCC_ONLY_SAME_ACTUATOR, CONST_PRED_MATCHED_ACTUATOR, MDL_ONLY_FIXED_SCHEDULE, STICKY, STRUCTURAL, SEEDED_MRV, LUBY_RESTART.
The design requests 64 TRAIN and 64 EVAL puzzles in each profile: 256 generation requests, 36 study cells and at most 2,208 solving tasks after qualification. Failed generation requests are recorded without replacement. The 48-hour cumulative admission ceiling is a limit, not an ETA.
The main long study uses the CORE action set. Deliberate AIS, PATH, Cube and Atlas activation is tested separately in specialist screens; their presence in the arena does not imply activation in every long-run task.
Checked deductions, proof replay, Atlas mechanisms, compact checkpoints, FAST LIVE and bounded specialist tests are executable.
Windows path and quoting fixes, a new causal launcher, status, stop, resume and verified live extracts. The old two-arm night launcher is labeled as a legacy engineering soak.
The local Windows run has started. The first reviewed extract covers puzzle qualification; comparative solving results remain pending.
Promote mechanisms only after measured value, browser parity and acceptable size/runtime cost. Human learning benefit requires its own evaluation.
The current browser game lets you play, request hints and compare strategies. R6 runs as a separate Python research arena. The product direction is a compact browser experience with checked explanations, review of actual moves and useful next exercises. This page update documents the new arena; it does not install the Python specialists into the browser game.
The grid stays central. Proof and research machinery surface only when the player asks for help or review.
Expose proof bits, work units, representations, DCC decisions and replay for research and advanced users.
The bounded HF4 acceptance chain is complete and internally consistent. It validates the arena, proofs and pilot orchestration; it does not substitute for the separate long scientific campaign, which was not started.
| Evidence | Observed result | Scope |
|---|---|---|
| HF4 bounded master | 5/5 PASS | Package, Windows/preflight, selftest, smoke and bounded pilot stages completed successfully. |
| Selftest + smoke | 444/444 assertions; 3 allowed SKIP · smoke 4/4 PASS | Engineering acceptance of the delivered arena; allowed skips are retained explicitly rather than hidden. |
| P1 / P2 / P3 pilots | PASS · 467 unique runtime tasks = 335 SOLVED + 132 LIMIT | One bounded development experiment. These counts are not an independent scientific replication. |
| Scientific status | Long campaign executions 0 · scientific_final=false | Semantic proof replay is NOT_RUN; no representation, MDL or DCC superiority is promoted from this cut. |
The earlier main P1 comparison remains an important negative control: MDL_DCC solved no more puzzles than the matched constant-predictor actuator and cost about 37.8% more WU; Seeded MRV and Luby restarts were cheaper. The final bounded acceptance does not reverse that result.
Final bounded live extract: HF3_ALL_LIVE_1789236581472973300.zip · 13,722,495 bytes · 3,021 members.
Final extract SHA-256:e1c5b282beaa0ef14a7ff15cc166852ca5e05c9ef459f9521243ca99f42a2b5f
The included verifier returned VERIFIED; its manifest SHA3-256 is 722125503ce7c1e918eab328082c2d7088ae9dd7d947667db4dba58955fb0ace.
Release receipt retained for lineage: AI8_Sudoku_R6_Program_v0_2_0_R1_HF3_HF1.zip · 2,765,694 bytes · 214 members.
Earlier qualification snapshot retained for history: HF3_LONG_FAST_LIVE_1789073761629256000.zip. The final bounded extract above supersedes it for current status.
Final bounded public evidence receipt ↗
Earlier R3L1 evidence, preserved under its original version ↗
Bits, WU, CPU, solved rate, proof coverage and human learning are different quantities. They are not merged post hoc.
Seeded MRV, Luby restarts, fixed and structural policies, matched predictor/actuator controls and bounded Context UCB diagnostics make the comparisons explicit.
Any “10% better” claim must name the task profile, comparator, quality gate, total account and uncertainty rule beforehand.