Reference

Lookup material — no narrative, come here when you need a specific name.

• Glossary — one line per term, for the words the docs use without stopping to define: flat, cricket, shop, stance, guard, golden.
• Builtin commands — every engine command the interpreter registers, by family, including the deliberate no-ops and stubs.
• Tools — the CLI utilities under tools/: dumpers, disassembly helpers, and the flow-map generator. (The browser editors have their own section: the browser editors.)
• Tests — which suite covers what, and the command to run each one. The argument those suites make — what the playthrough is for and what it has caught — is narrative and lives in How we know it's right.
• Continuous integration — which suites can run on GitHub's machines and which need the self-hosted runner that has the CD rip, how that runner is set up, and what changes when the repository goes public.
• Releasing and deploying — a release is a tag; where the version number lives, and the four things on the host a deploy must never write over.
• The route — the twenty-seven segments and what each crosses, how much of the suite to run while you work, what driving each minigame costs, and the conventions a new segment will trip on.

Back to the documentation home.