bfd3efe111
sylpheed-port overturned their own phase-0 result using the identical-leaves fact I gave them: the same leaf minimises at phase 240 against a title capture and 0 against a main_menu capture, so the best-matching phase is a property of when the shutter fell rather than of the game's rest state. A continuously sweeping element has no canonical rest phase. They warned that any whole-frame score against a single capture carries a phase term of ~1.0 RMSE. Measured on my own two JP sessions, which certainly differ in sweep phase (44 025 px differ in the band the leaf crosses): whole frame 4.566 sweep band x721..1241 4.088 the adjudication box 0.3215 Their ~1.0 understates it for this screen: a whole-frame score against one capture of the JP title carries ~4.6. Theirs is the leaf-phase component isolated in a renderer; mine is everything that varies between sessions -- the plate pulse alone contributes ~2.8, measured separately on the EN peak/trough pair -- and includes theirs. My margins are unaffected and now for a measured reason rather than an assumed one. The era margin of 16.72 sits against an in-box term of 0.32, and settle-vs-rest at 1.48 is 4.6x that term while remaining non-decisive against the render-axis plateau of 1.2, exactly as stated. Scoring the 388x423 box rather than the frame drops the between-session term from 4.566 to 0.3215, a factor of 14, because the sweep contributes at x 721..1241 and the box is mostly clear of it. That was NOT why I cropped -- the crop was to stop a local difference being diluted across 92 % of an identical frame -- so the robustness is luck. The rule it earns: score inside a region that excludes the free-running elements, and measure the residual term there rather than estimating it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
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.