Two warnings. The first does not reach me: nothing is authored from screen-transitions.md's 0.87/0.97/4.08 s spans, and nothing in this port reads keyframe times outside the crate -- their stale fade_quads.py failure mode cannot occur here by construction. The second is about black_hold_units: 9. Testing their structural claim on my export: pteff00 on main_menu is [0:a255 12:a0 70:a0 80:a255], rising to black over 70->80, while content fade-outs start at 58-60. That is 12 units of lead, exactly six frames at 30 Hz, matching their measurement off the running game -- disc and capture agreeing by independent routes. They say the two overlap; mine has a 2-unit gap, one frame, inside their stated resolution. The arithmetic: quad ramp 10 units + my authored 9 = 19 units = 0.317 s against their measured blackout of 18 units = 0.30 s. One unit apart, inside their own resolution. The measurement that withdrew the 14 supports my 9. It survived because I declined to author the 14 when the arithmetic was available and fit -- I wrote that it was arithmetic rather than a measurement and left the value where it had been measured. Had I adopted the composition I would now carry 24 units against a measured 18, which is the dead black they are warning about. Not adjusting 9; one transition, one run, +/-1 frame. 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.