f3d77d5fbf
A human says something is missing on the title. Something is: it plays BGM, and two different cues. Method with the control built in rather than bolted on. R4 wants a negative to show the method finding the menu's cue first; this method cannot produce a false negative for one screen because it does not look at one screen. It finds every call of the play function in the image and reads the cue each passes: 34 callers, cue ids 1103 x24, 1102 x3, 1107 x2, 1108, 1106, 1104, category 4 on every one. 1103 is the cue the corpus already attributes to the menu, and the method finds it 24 times. GamePart_Title's neighbourhood is 0x821C4xxx-0x821C7xxx per the registry page, and seven play sites fall inside it: 1103 at 0x821C52D0, 0x821C5620 (inside the phase handler sub_821C5580), 0x821C6188 and 0x821C6294; 1102 at 0x821C53B0, 0x821C5BA0 and 0x821C6DE0. So the title plays BGM_103 and BGM_102, and 1103 is the SAME cue as the menu's -- which is why a port playing nothing on the title sounds like something is missing rather than merely quieter. The sting is NOT answered and the page says exactly why: this play function carries ids in the 1102-1108 BGM range, the UI stings are SE_* cues with ids 1-322, and not one of the 34 sites passes an id in that range. SE goes through a different call and this method is blind to it by construction. That is a bounded negative about the instrument, not the game, and reading it as "no sting" would be the third time this corpus mistook a blind spot for a fact. Reach: exhaustive over every bl to 0x8217ACF8, so complete for that function. The GamePart attribution is by address neighbourhood and carries the registry page's own "by position and convention, not proven" caveat. 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.