2dfc20bc0f
sylpheed-port said the port plays the full group (255 and 210 units) rather than my 240/195, and they are right for a reason sharper than either of us first had. The _eff elements ramp alpha 0 -> 255 over t=0..15 while the main logo is still fully transparent: palogo_sqex.t32 0:a=0 15:a=0 30:a=255 ... 255:a=0 palogo_sqex_eff.t32 0:a=0 15:a=255 30:a=212 45:a=0 So the SCREEN is visible from within t=0..15 and its visible span is the full group. My "240 units visible" was ONE ELEMENT's visible span, computed while another element of the same build was already on screen -- which is exactly the error class I was writing up when I made it. Recomputed against the screen: publisher 1.011/1.083/1.028, developer 1.002/1.001/0.962, mean 1.0146 with one measurement BELOW unity, against my 1.085 with none below. That is not a clock at 54 u/s. The systematic is gone and Q1 stands unqualified. The consequence was wrong too: "a port playing 240 units at 60 shows the splash 0.42 s less" -- it plays 255, so the gap is 0.174 s, and on the developer splash the port runs longer than my mean. No direction to correct in. What survives weakly: against the full group the publisher runs long in all three boots while the developer sits at unity. Three boots per screen is thin and it is not a systematic. METHOD: state the number, and state what it is a number OF. Four instances of this family now -- pivot anchor as extent, centre track as bounding box, cycle length as motion duration, one element's visible span as the screen's -- and two of the four arose because the PUBLISHER of the number never said what it spanned. The reader reasoned correctly from the only definition available each time. Publishing a quantity's extent in the same breath is cheaper than every check in that file. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
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.