33a6b4ea6f
The port observed that the justification for 60 has changed three times while the number never moved, and that three routes sharing an upstream assumption are weaker than they look. Checked. They do share one. Route B needs "the guest presents 60x/s", which comes from the vblank histogram UNDER XENIA'S 60 HZ LIMITER. Route C needs "the vblank is 60 Hz", which is that limiter's cvar directly. Route D is a wall-clock duration that lands on 60 only because the vblank is 60 Hz and Canary roughly keeps up. All three reduce to one fact: the display refreshes 60 times per second on this emulator. I presented them as corroboration and that was wrong. What is actually established, by manipulation rather than agreement: units/second EQUALS the display refresh rate. Forcing 30 Hz gave 30.2 units/s; at 60 Hz it is 59.8/61.3. One factor changed, the output tracked it. It becomes "60 units/s" only via an external fact this corpus has not measured -- that an Xbox 360 outputs 60 Hz. That is a hardware specification and it is solid, but it belongs outside the measurement rather than laundered into a third agreeing route. The conditional form is more useful anyway: it says what to do on hardware that is not 60 Hz, which is exactly why the port's time-based clock at a fixed 60 units/s is the right construction rather than a coincidence. And it keeps the port's `authored` classification correct -- nothing here promotes it. Also sizes the clock-origin capture properly. FRAMES=9000 ran to completion still in the movie at 8999, so the cap really fired this time. Content hashes show 3967 distinct decoded frames against ADV.wmv's declared 4131 -- 96% complete -- at 1.79 presents per decoded frame, not the 2.00 I assumed, which is why the estimate was short. Needs ~294 more presents to clear the movie plus >=236 for the plate, so FRAMES=11000. Free on the way past: 3967 decoded frames over 7091 presents at ~52 presents/host-s is 29.1 movie frames/s against the disc's declared 30.000, a 3% match that ties the present rate to a disc fact rather than a clock. 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.