be09966870
The port has no gain anywhere and confirm sits 3 dB above the music. Asked the disc rather than choosing a number. Five audio-bearing objects in tables.pak, zero tokens matching VOL GAIN LEVEL DB ATTEN AMP MIX LOUD. Control passes: the same matcher finds 38 SE_UI hits, so "0 hits" is not a broken matcher. The negative is stronger than a name search usually is, and I expected it not to be. Dumping the schema shows the token stream is value-then-key pairs -- "40, LINE_PITCH", "0, Y_OFFSET_ANALOG_STICK" -- so NUMBERS ARE TOKENS AND THEY CARRY NAMES. A gain in this format would have a name, and the name search covers exactly the space where it would live. That turns "I did not find one" into "one is not there in this file". Reach, and it is why this is undecodable rather than decoded: I did not check the .slb bank headers, which is the other conventional home for a per-wave gain beside a wave index -- and is where the play-test's own framing points. No .slb exists as a loose file on the extracted disc, so it costs a pak extraction I did not have budget for; it is the first thing the next attempt should do. Nor did I check the executable, where a mix could be immediates in the sound-play path around sub_821C5580. So this is not "the mix is not on the disc". It is "the mix is not in the table where a cue's fields live". Pointer, not a finding: object #15 lists po_sound_scr.prt -> SOUND among GP_OPTIONS' screens, so a user-facing sound options screen exists and at least one volume is runtime state. Port keeps authoring nothing yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t
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.