5fb64f3d31
The 5.1 reading of a voice cue s three concurrent streams was recorded here as a hypothesis with counter-evidence attached. It is now answered, by the port fitting the disc s decoded streams against a clean capture of the game s own 6-channel output, with the instrument controlled first (known-present margin +0.248, known-absent +0.005). Speech-band margins put streams 2 and 3 at +0.305 and +0.307 on FC, r = 0.989, above the known-present control, while stream 1 sits in the noise on every channel. The low band mirrors it exactly: the movie bed at 0.76 to 0.84 on the four corners against 0.32 on FC. Dialogue in the centre, bed in the corners. The hypothesis was right for a reason the file could never have supplied. ChannelMask reads 0x0002 on all three streams, so the header is not merely unhelpful, it is actively misleading -- refusing to call it 5.1 from the header was correct, and the oracle answered what the header could not. Three limits recorded as the measurer stated them: streams 2 and 3 are indistinguishable to this instrument, so no rule for choosing between them is vindicated; the one-of-three-streams warning stands, since nothing says what streams 1 and 3 contribute; and the reach is 59.7 s of a 137 s movie, one run, one asset. Also records the capture that would strengthen it most and why it is not taken: S00A rather than a longer ADV, because its second full-length stream is digital silence where ADV s is a 0.60x copy, so a structurally different movie would agree. Reaching it needs a driven rendered run -- S00A starts about 4.5 s after A on the save slot -- so it cannot use --gpu=null and will carry the additive padding. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QsEPXWVaEpyfudtR6re1Pd
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.