Release source references

Source revisions for the website examples and public Demo Disc v0.40, with source-availability checks and their limits.

On this page

Checked on 30 September 2026; the PSoXide Arcade row was added on 8 October 2026 after its repository became public. These references come from the public Demo Disc v0.40 component receipt, matched to BIN SHA-256 d1e16f5deca68351b8361ab61bc7db90298497dc93817e72f8d7fe5be6657940. They identify recorded source revisions. They don’t certify that every release package satisfies every licence requirement.

Demo Disc v0.40

ComponentRecorded source
Disc builda8cf0a8244
Launcher editor component6eebb2d866
Build-time emulator component035bf6f31f
Launcher SDK component6da88d92de
PSoXide Arcade4fd3daa7c8
Celeste Classic Collection76bb26b877
Cortex Ignition1bb7a44c2c
NitroXide4eaf4c0f37
PSXcelc08096c14d
Quake portc58e2dfdfe
VoXidea5d408b6d4

The disc build recipe records the individual program builds. The launcher’s component pins and a game’s own pins can differ; use the recipe and that program’s build instructions together.

The table above is not a complete source package for the disc.

Website example players

The six interactive SDK examples are built from pinned public sources by the website workflow. Their build manifest records the SDK revision, emulator revision, Rust toolchain and executable hashes. The player build record records its source, locked SDK dependency, build tools and bundle hashes. Build instructions live beside the pinned emulator source; the website repository contains the staging script and workflow. Licence texts and third-party notices are served with the player.

itch.io browser player and other downloads

The demo-disc browser player on itch.io is deployed separately. Its current WebAssembly artifact has not been matched to an exact source revision in this website review. The emulator revision above belongs to the disc’s build receipt; it isn’t the revision of the live browser player. Standalone game downloads also need their own release-to-source mapping.

Use the release’s matching source and build instructions, not an arbitrary current branch. Report a missing source reference with the download URL and version. See Legal & licensing for the distinction between source availability and third-party content rights.