Turochamp EmulatorChess · History · Artificial intelligence
An idea from 1948.
A different way to play.

The reading room

History, with the working attached.

Follow the evidence, inspect the reconstruction and explore the original material.

How to read this site

Historical accounts, recorded game scores and our software’s behaviour are different kinds of evidence. Each feature links to its sources; the reconstruction page records software choices that should not be attributed to Turing.

The site uses original editorial text and links to archival documents rather than bundling scans. External reading requires an internet connection. The playable engine, replays, teaching console and page navigation work locally.

Bibliography

About this project

Turochamp Emulator is an independent educational project centred on an early chess algorithm. It is not affiliated with the Turing estate, King’s College, IBM, Interplay or any television franchise.

The interface uses a wooden-set palette and system chess glyphs. No archival photographs, commercial game artwork or source code from GPL chess engines is included.

Software credits

The chess-rules layer is Jeff Hlywa’s chess.js, pinned to v0.10.3, distributed under the BSD two-clause licence. Its notice is retained, with a local copy in chess-LICENSE.txt. A small documented adapter exposes its existing internal move operations for the search; it does not add an AI.

The site-specific engine, interface and articles are supplied as editable project files. See reconstruction notes for the scope and limits of the historical implementation.

Privacy and advertisements

This offline build has no analytics, accounts, tracking cookies or live advertising scripts. Each console reserves a labelled 320 × 50 space for a future advert. Calculations run on your device. Games remain in the current page until you save them as PGN; reloading starts a fresh game.

Publication details

The supplied canonical links and sitemap assume https://turochampemulator.com as the future address. They are configuration, not evidence that the domain has been registered or the site published. The included README explains what to change before going live.