f6d49da612
Refutation attempt, per the adversarial duty. Target: this page's own row "B on the main menu goes to the title". Chosen because it is one of only two Q5 rows with an empty evidence cell, and because it is the only exit from the main menu, so the port will build on it. Whole-frame colour test for the pad-glyph discs. The main menu carries ZERO red-B pixels anywhere in the frame, on two independent captures, while the same unchanged detector finds 514 on EXTRAS and 518 on DIFFICULTY. The control passes twice: the A glyph reads 438/438/440/438 across all four screens, so it is one asset at one size and a B of that family could not have slipped under a threshold. The main menu's legend is "Select / OK"; every submenu adds "Back". The claim SURVIVES -- a legend is not behaviour, and an absent glyph cannot refute an observed press -- but it is downgraded to amber. The observation is uncited and single, it is now the only Q5 row the game's own text contradicts, and there is a named confound: the title-side screens auto-return after ~8-10 s idle, which looks exactly like what was described. Reading 0x828A690C while pressing B would separate them in one run; that run needs a disc this container does not have. Second finding, same method. MISSION SELECT's "sixteen d-pad presses never left Stage 01" was a LOCKED stage list, not a broken one. The labels have three brightnesses, not two -- locked 104, unlocked 183, focused 254 -- and the all-story-unlocked capture is the control that separates the lower two while holding row 1 at an identical 254. On that save the cursor reaches Stage16 at the bottom of a scrolled list. The list is 16 long and shows 8 at a time. Regenerator committed beside the finding; it reads only files already in git. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013UxPvE5cz7zekXBKi7Xw2r
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
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.