018e879907
The Decoder took the capture I asked for and described it as the full mix, the
movie's WMA track plus the three XMA streams. It contains none of them.
Envelope cross-correlation, sliding with overhang, normalised over the overlap,
minimum 30 s of overlap so a short window cannot win on an edge. Against the ADV
bed, against each of the three voice streams, against BGM_103 and against S00A,
every pairing is a PLATEAU rather than a peak: best-to-runner-up margins of
0.001-0.016. The margin is the number that matters, not r.
Three controls, because a negative from an uncontrolled instrument is worthless:
the instrument finds matches on this data -- bed vs bed r=1.000 margin +0.115,
voice stream 2 vs stream 3 r=1.000 margin +0.300;
my reference really is the movie -- the .ogv transcode against the disc's own
ADV.wmv, r=1.000 margin +0.114, so a miss is not my transcode;
drift is excluded -- a stretched playback would still match locally with the
best lag climbing monotonically, and 5 s windows give 4.95, 15.30, 119.35,
50.75, 29.35, 83.95 s, scattered across the movie.
WHAT IT IS has been handed back rather than guessed. It is 70 s of something,
all six channels carrying signal at RMS about -27 dBFS, matching nothing this
port exports. Diagnosing it is the other side of the wall.
One measurement that may help: split as 5.1, channels 3 and 6 are BYTE-IDENTICAL
-- same MD5, not merely the same peak and RMS. An exact duplicate pair inside a
six-channel surround output is consistent with the Decoder's own warning that the
6-channel frame is Xenia's hardcoded kFrameChannelsDefault rather than the
guest's request, and weakens any reading of that file as evidence of a 5.1 mix.
THE VOICE EXPORT IS UNCHANGED: still one stream of three, still marked red in the
manifest, the console line and authored/audio.json. A failed measurement should
change nothing, and what would have been wrong is treating an expensive recording
as an oracle because it was expensive.
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
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.