Play your Steam library's Windows games on a jailbroken PS5.
prospero-win runtime kits
A kit is the Windows runtime Playden installs on the console: Wine and its PS5 libraries, DXVK, the template bottle every game's bottle is copied from, the PS5 title shell and the shipped recipes. Kits are built outside this repository and uploaded to the console separately; Playden builds never build Wine or download a kit.
What Playden pins
third_party/prospero-win: the prospero-win source the kit was packaged from.dependencies.lock.json(prospero_win.revision) records the exact commit, and builds refuse another revision or a dirty checkout. Initialize it withgit submodule update --init third_party/prospero-win.src/runtime/kit_trust.h: the kit this build was tested with (its id and manifest SHA-256), shown next to the installed kit in Settings › About.dependencies.lock.json(prospero_kit) records the same kit with its runtime revision and how it was built; a host test checks the two agree.
Playden uses the kit installed at /data/playden/kits/<kit id> (playden-kit since kit 0.13) as long as it is
complete and its files match its own manifest; an incomplete or changed kit is refused at start-up.
Building and packaging
The scripts that built the current kit are in tools/kit-h. They build Wine and the
PS5 libraries on a Linux machine, stage the inputs and write a kit spec. The kit is then packaged with prospero-win's
packager:
python3 third_party/prospero-win/tools/package_playden_kit.py package --spec /absolute/path/kit-spec.json \
--out /absolute/path/kit
Kits with host build paths in their runtime files (development kits) need --development-build-paths.
tools/console_kit_upload.py uploads a packaged kit to the console.
Packaging checks every input against the spec and the source pins; a pinned source does not by itself certify the
runtime. prospero_kit_producer_consumer checks that a manifest written by the packager is accepted by Playden's
verifier and that changed or extra files are refused.