SanderGi/Ultimate-Fish-Tablebases

Ultimate Fish endgame tablebases

This gated dataset is the authenticated tablebase catalog used by the Ultimate Fish engine and its local tablebase manager. The tables contain exact win/draw/loss and distance-to-win results for certified Chess Ultimate endgames.

File roles

• tablebases/*.uftb are the ordinary runtime tables probed by the engine.
• tablebases/kdevilk-{a1..d3}.ufds are the twelve logical fixed-square partitions of the certified stateful King+Devil+causally-spawned-Minions vs King class. Partitions below the hosting service's 50 GB object limit are stored directly. Larger partitions use an authenticated .ufdsm manifest plus ordered .ufdsp transport shards. The manager verifies every shard, reconstructs and verifies the certificate-bound canonical .ufds, removes the transport shards, and only then installs it. All twelve canonical partitions are one logical runtime table and must be installed together.
• Files such as .ufiw, .ufgd, and the other uf* sidecars are authenticated proof/dependency data. The manager installs sidecars with their table; they are not substitutes for a runtime .uftb or .ufds file.
• certificates/ultimate-devil-stateful-class-certificate.json binds the exact twelve Devil partitions, their sizes, SHA-256 hashes, outcome censuses, and aggregate conservation result.
• manifests/tablebases-sha256.json is the machine-readable, revision-bound catalog of every managed artifact.

Every managed artifact is stored with a Hugging Face LFS SHA-256. The Ultimate Fish manager refuses catalog entries without that digest, validates shard manifests and byte conservation, verifies the complete logical download, and only then atomically installs it.

Install and probe

Request access to this dataset and authenticate the Hugging Face CLI. Start the local engine bridge with ULTIMATE_TABLEBASE_PATH set to the desired tablebase directory, then use the Tablebases panel in the Ultimate Fish UI to install or remove endgames. For example:

cd ui
ULTIMATE_TABLEBASE_PATH=/absolute/path/to/tablebases npm run engine

The engine scans tablebases/ by default and accepts a colon-separated ULTIMATE_TABLEBASE_PATH. It probes only codec-compatible, structurally valid files and fails closed on malformed headers, extents, ordering, or stateful Devil records. Files installed while the local bridge is running are picked up by a clean engine reload before the next queued operation.

See the repository's tablebases/README.md for the authoritative class ledger, model exclusions, and certification notes.