4d1d5a1f2e
No emulator-requiring state/approved item was open this iteration (issues #1, #3, #5 all landed and moved to state/needs-human; #25 still awaits approval). Used the gap for corpus consistency instead of idling, per the same "a correction that never reaches the row someone reads" failure this project keeps naming. 1. menu-navigation-semantics.md's own Q4 table still said NEW GAME was "not tested" and its own prose said it was "deliberately not pressed" and hangs the emulator -- both refuted BY THIS SAME PAGE on 2026-08-28, 34 lines further down ("NEW GAME -- measured ... it is not a hang. It opens DIFFICULTY then SELECT DATA"). The correction never propagated backward into the table or the status line above it, so a reader stopping at either would come away with the wrong (and already-refuted) answer. Fixed in place, struck rather than deleted, with the actual destination and an honest note that DIFFICULTY has no id-table name match (already refuted separately) while SELECT DATA plausibly matches GP_SELECT_STORAGE as a fresh, low-confidence guess. 2. Found the identical failure mode in my own recent work: HANDOFF.md's original Q1-Q10 summary table (near the top of a 6600+ line file) still quoted the 2026-08-30 "no auto-repeat" finding as current, three commits after this same session measured 12 frames delay / 4 frames interval through a repeat-capable driver and explained why the earlier negative was a driver limitation, not a game fact. A reader who only sees the summary table -- which is exactly what a long file trains a reader to rely on -- would get the withdrawn answer. Fixed with an explicit note pointing at the current entries rather than silently editing the number in place, so the correction itself stays visible. Refutation-shaped either way: two claims ("NEW GAME untested", "no auto-repeat") checked against this corpus's own newer evidence and found not to survive, recorded rather than left to be rediscovered.
Sylpheed
A clean-room reverse engineering and port project for Project Sylpheed: Arc of Deception (Xbox 360, 2007).
Three things live here, in one repository so that a change spanning them lands as one commit:
| The decoders | crates/sylpheed-formats — the disc's formats, read and verified disc-wide |
| The port | port/ — a Godot 4 project, plus crates/sylpheed-export which converts a disc into the open asset tree it reads |
| The corpus | docs/re/ — what has been reverse engineered, with its evidence, its retractions and its dead ends |
You need your own copy of the game. No game content is in this repository and none ever will be. The exporter reads the disc you supply.
The oracle is the real game
sylpheed-cliand the Explorer are tools for verifying our decoding. They are hypotheses under test and they have been wrong. When something must be checked against the truth, the truth is the game running in Xenia Canary, captured — not any renderer of ours.
This is stated first because getting it backwards is the most expensive mistake this project has made.
Layout
crates/
sylpheed-formats/ the decoders. Disc-wide verified; the corpus is its spec
sylpheed-cli/ headless tools -- render a screen, dump a table, probe audio
sylpheed-viewer/ the Explorer: a human's window onto the disc. STATIC data only
sylpheed-export/ disc -> the open, moddable asset tree
port/ the Godot 4 project. Reads open formats ONLY
authored/ decisions that are NOT on the disc, each with its reason
data/
base/ generated by the exporter. Gitignored, never hand-edited
mods/ drop-in overrides. Yours
docs/
re/ the corpus: findings, refutations, method traps
game/ how the game is navigated -- menus, modals, flight
port/ the port's mission, its handoff contract, modding rules
-- and RUNNING.md, which is how you actually start it
agents/ how the agent team works together
tools/ capture harnesses, probes, the share tool
exchange/ transient inter-agent files. NOT in git
docker/ the agent containers
Where to start
docs/re/INDEX.md— what is decodeddocs/re/REFUTED.md— what has been tested and dieddocs/re/METHOD.md— traps this project has already paid fordocs/game/navigation.md— how the game is navigateddocs/port/MODDING.md— why the asset tree looks the way it does
Xenia Canary is a separate repository: it is a fork tracking upstream, and it carries our instrumentation.
Conventions
Confidence is per claim, never per document: ✅ CONFIRMED · 🟡 PROBABLE ·
❔ HYPOTHESIS · ❌ REFUTED. A withdrawn result is kept with its reasoning
rather than deleted — that is why the numbers here can be trusted.