ee47b47440
Last iteration could say the shortfall scales with the background but not which curve. That is decidable with no RE: an element rendered over two different backgrounds gives two equations in a and aC, and the mod tree supplies the second background by suppressing pteff10/pteff12, which moves it by a mean of 26 levels. No placement, no coordinate transform, no texture decode assumed. The control is exact. Alpha-over rebuilt from the solved per-pixel a and aC reproduces the port's own render at RMSE 0.0000 on both screens, so the recovered values are right rather than a fit that lands nearby. RMSE against the capture, ptframe1 / ptframe3: additive 34.305 / 28.948 screen 50.052 / 50.368 alpha-over 65.046 / 71.299 <- what the port does not drawn 90.916 / 109.801 Same ordering on both. The frame is certainly drawn in the capture, and additive roughly halves the error of what the port currently does. What it is not: additive still leaves 28.9-34.3, so none of the three reproduces the capture. This ranks candidates, it does not identify the equation, and the absolutes are inflated by mapping the capture through the fitted LUT inverse -- the ranking is fair because all four go through the same mapping. Nothing adopted. The Decoder established no blend is on the disc for .t32, so any choice is authored, and the mission says propose rather than take. The renderer is unchanged. Refutation attempt, recorded as surviving: their kind-0 claim checked against my own exporter's independently decoded kind_raw. Every sprite decoration on both screens is 0x0, frames included, every button 0x3002. Two independent decodes agree, which is also what makes the blend question sharp -- the frames are declared identically to ptbase and pteff05, which the port draws at 1.31x and 0.92x.
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.