94d761ebff
Measured by the Decoder with the full-quad reader: at the snap frame both sweeps enter at their DECLARED OPENING alphas -- pteff03 at 255, pteff03a at 0 rising 1,2,3,4,6,11,17 from x=1721. Those are the leaves' own t=0 poses. My implementation advanced the shared clock and left the leaf phase untouched, so the sweeps would have sat mid-travel at the right clock value and the wrong position. A defect visible only in a film -- no still and no clock reading would show it, because the clock was correct. The field already existed (leaf_start_units, from the F6 work); it simply was not being set at the snap. VERIFIED, pre-registered, via --probe-leaf on a real boot with a real press: snap frame -> leaf_t 0.0, pteff03 x=-639, pteff03a x=1721 (declared t=0) next frame -> leaf_t 0.5, both advanced by 2 px Their separate note on my snap target: 236.0 survives their challenge -- at the snap the sweeps are at alpha 255, putting the title clock in [100,238) -- but their data cannot separate 236 from 200. Recorded as surviving, not confirmed; the bound in the code comment already says so.
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
-- and RUNNING.md, which is how you actually start it
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.