b8f939cc4c
The Decoder made this the gate on S00A and that was the right order: ADV plays itself on boot and can be captured with --gpu=null at 0.96x real time, but S00A starts ~4.5 s after (A) on a save slot, which needs a driven run, which needs screens, which rules out --gpu=null. So S00A is necessarily the 0.70x rendered route with ~10% additive padding, and is only worth a boot if stripping is exact. It is. A real music+SFX bed -- 137.37 s, carrying 454 genuine zero runs of its own -- had 1149 holes inserted at 8.37/s to +9.9% length, matching the observed ALSA profile, then was stripped and correlated in the low band: original vs itself r 1.000 lag 0.0 s margin +0.141 ceiling PADDED vs original r 0.436 lag -12.2 s margin +0.006 destroyed STRIPPED vs original r 1.000 lag 0.0 s margin +0.142 recovered stripped vs orig-also-stripped r 1.000 margin +0.143 Two things worth reading off that. Padding at that profile destroys correlation completely -- r 0.436 in the known-absent regime -- which independently confirms on a file whose contents I control that the earlier captures were unusable for the reason claimed and not for some other one. And recovery does NOT require stripping both sides: the stripped capture matches the UNSTRIPPED source at the ceiling, so the port's reference assets never need touching. `tools/port/strip-padding` implements it, and its header leads with when the operation is vandalism rather than with what it does: PulseAudio's monitor SUBSTITUTES silence and deleting those holes repairs nothing, while Xenia's ALSA writer PADS and removing that is exact. Running it on the wrong artefact would look like it worked. Its output is byte-identical to the control's own stripping, so the tool and the experiment are one operation rather than two implementations that agree. Not licensed by this: stripping removes genuine silence too and cannot tell them apart. Here the genuine runs total 0.71 s in 137 s and cost nothing measurable; on material that is mostly silence they would. 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.