Repository navigation
Prove finite-board Snaky and explain one checked strategy branch - #18
Merged
Merged
Conversation
# Conflicts: # WORK_LOG.md
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
The atlas can now explain one complete Snaky play while linking it to a separately checked strategy guarantee. A sibling Lean project formalizes the paper's existing result on the exact 251-cell envelope and its containing 17×17 board: Maker can force a Snaky within 21 claims from the empty position.
Finite game semantics require fresh on-board claims, count replacement claims, and require a legal Breaker reply when play continues. Immediate wins need no reply. The pinned upstream files are preserved; generated finite-card proofs use the exact 728-card certificate.
The existing
explain/checkinterface acceptscontext:family-187:snaky:finite-board-21:v1. A separate adapter and independent checker save one eight-claim example. The responsive viewer shows ownership, replies, surviving envelopes, move budgets and the complete winning target. Its JSON, offline script and evidence links share one generated packet anchored to committed inputs.Validation and CI repair
c3af350005f413554aea03db8cbf2c4c2d09e31b: build, kernel replay of exactly 179 local modules, allowed-axiom audit of 19 declarations, and seven mathematical rejection controls. The receipt covers 194 source inputs and 20 artifacts.3bd96caa445c459371128e882fe420479084924e./proc/<pid>/statwas being read. The helper now accepts the preciseProcessLookupErroralongsideFileNotFoundError, while still rejecting unreadable or live children. Two deterministic regressions were added; all 14 runner tests pass on Linux and Windows passes its 11 applicable tests. Independent review approved this delta; it changes no proof source, production runner or pinned receipt. Fresh hosted checks run the expanded 90-test Snaky suite.Scope and reproduction
Fresh checkout:
python scripts/snaky_proof.py run --out runs/snaky-fresh, followed bypython scripts/snaky_proof.py replay --out runs/snaky-fresh. Prerequisites and walkthrough:docs/SNAKY_FINITE_BOARD.mdanddocs/SNAKY_PLAY.md.The renewed local run reused dependency/build caches and completed in 24 minutes 11 seconds; kernel replay took 1,303.713 seconds. This is a local measurement, not a controlled speedup study or fresh hosted timing. An earlier local bulk replay reached roughly 14.3 GiB RSS; hosted memory, disk and runtime remain reproduction concerns measured by CI.
The source paper already states the finite-board result. This work supplies its checked formalization and inspectable evidence. The displayed eight-claim play is one execution, not an improved universal bound or a formally extracted executable policy. The 616-card comparator remains a different certificate. Model benchmarks, reserved tasks and training remain paused.