Files
Alex Vanderveen c9eafaeb7c docs: plan multi-disc titles
Records the design proposal for shipping a title like FF7 as one launcher
entry, one binary, N discs. Nothing is implemented.

The problem splits along two axes: which image is mounted (a lid/shell state
machine cdrom.c has never had) and which program is running (each disc has its
own boot EXE and serial, so one binary must link and select between N
recompiled programs). Eight dependency-ordered phases, each with a gate; P4 is
conditional on what P0 observes and gets deleted if the swap turns out not to
re-execute a boot EXE.

Every file:line in the ground-truth section was verified against this commit.
Three corrections fall out of that pass and are made here:

- config_schema.md listed the `discs` field under "What's NOT in the schema
  yet" while also documenting it as a live key. It is parsed today
  (config_loader.cpp:1217), so the stale entry is removed and the field row now
  says the runtime still mounts only discs.front().
- ACCURACY_BURNDOWN.md already owns shell/lid under the CDROM item; it now
  points at P3 rather than letting a parallel record start.
- recomp-ui is not a submodule of this repo, so the launcher phase is marked as
  landing there and its ABI references as unverifiable from this tree.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017AwqKPQFnK3x7xQbK4PQKj
2026-08-28 02:32:57 -04:00
..
2026-08-07 01:43:04 -04:00

Internal dev-logs & design notes

These are the working design documents and burn-down logs the project was built from. They are historical/working notes, not contributor onboarding docs — they capture decisions, phased plans, and deep subsystem investigations in the order they happened, and some sections are superseded by later ones.

If you're new here, start with the top-level README.md, then docs/ARCHITECTURE.md, docs/EXECUTION_MODEL.md, docs/BUILDING.md, and CONTRIBUTING.md. Come here when you need the why behind a specific subsystem.

Plans & roadmap

Cycle accuracy & timing

BIOS / scheduler

Renderer / widescreen

Overlay cache internals

  • SLJIT_PERSIST_CACHE.md — removed. It described the persisted shard cache of the sljit Tier-2 backend, which was deleted in 5b7e69b4 (2026-07-15). For the current model see runtime/src/overlay_loader.c (per-entry candidate validity), tools/compile_overlays.py (shard formation and the .ranges manifest), and ../COMPILING_OVERLAYS.md.