e0fa8a6301
They captured the JP main menu for the first time: initial focus 新規 (NEW GAME), top item, ring y 225.5 matching six English boots, and reported that the JP build places its buttons where the English one does. Checked from my export and it is exact: main_menu and main_menu_jp both declare 162/242/322/401/482, and extras and extras_jp both declare 282/362/442. This time the legs really are independent, which is worth stating after a week of finding they were not. Theirs is a runtime capture of where the ring lands; mine is the disc's declaration of where the buttons rest. Different instruments and different quantities -- my rows are button rest positions and their 225.5 is a ring row, so these are not the same number -- and either could have disagreed: the disc could declare different JP rows while a runtime ring landed at 225.5 for some other reason. Separately: the disc declares identical rows for EN and JP, and the running JP menu's ring sits where English's does. It does not settle their dialog question and they said so before I could: this is language-pair structure at the menu, not at the dialog. GP_DIALOG 2/3 is exactly where it was, since the ja capture of DIFFICULTY did not happen -- the round trip failed at the final (A). Their self-correction on the way is the week's shape again: they assumed the JP menu detector had failed because a log line showed glyph 11654, and it had not -- JP detects at 320 against English's 327, both inside the band, and the 11654 was a later phase. Diagnosing from the log line rather than from the capture. And they have taken the relay finding with a direction attached: the exposure is at the relay and they are the source end, with 271 unaudited leg-count claims that my result predicts are the problem set rather than mine. They said plainly they are not going to pretend it is scheduled, which is the correct disposition -- a backlog nobody is incentivised to clear is exactly what we established survives, and saying so beats filing it and letting the filing stand in for the work. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
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.