8bb9238632
`title` is the port's largest disagreement with the oracle at 1.82%, and last iteration I attributed it to the moving ptloop sweeps without checking. Wrong, and so were the two hypotheses I formed after it. NOT THE SWEEPS. ptloop01/02 are 399x180 at (441,270) -- small and central -- and their exported keyframes hold pos, scale and rotation constant. The difference peaks at x~1088. NOT AN OVER-HELD ELEMENT. Added `--no-hold` to render the alternative: playing the title's groups past rest fades the screen to black by t=5.2 s, 30.97% differing against 1.82% held. Holding at rest is right. NOT A TIMING OFFSET. Sweeping the build-in gives 24.05% at t=1.6 falling monotonically to 1.68% at t=4.18 and 1.82% settled. The capture is at the settled end. WHAT IT IS: a horizontal redistribution. Signed difference by cell shows the port DARKER centre-left (-13.1, -8.3, -6.6) and BRIGHTER right (+16.0, +9.9), nearly cancelling -- whole-frame means 63.8 against 62.5. Brightness in the wrong place, not a level error or a tone ramp. It falls in the rows spanned by the two wide elements ptlogo_back2 (1118x262) and ptlogo_back2eff (1133x280), with the column profile falling off past x~1152 against their right edges at 1189 and 1197. AND THE EXPORT CARRIES NO BLEND MODE. ptlogo_back2eff's keys are declared, id, index, keyframes, kind_raw, layer, layer_source, pivot, rest, role, sprite -- there is no blend field, in this element or in FORMAT.md at all, and the port composites everything with normal alpha. If the game draws `_eff` layers additively, a wide gradient sprite would produce exactly this signature and nothing in the export would reveal it. Asked, not assumed; I have not tested it, and I am recording it because the three I could test are dead. Recorded and NOT acted on: pteff02's rest.t is 46, where its fade is 25% black, while its own group reaches 0x00000000 at t=236 -- so the port holds a black veil the timeline removes. Third instance of rest.t naming a hold that is not the settled state. It does not explain the residual: removing a darkening veil would make the port brighter still, and it is already brighter where it disagrees. `--no-hold`'s first version set the flag thirty lines before `view` exists and silently rendered nothing, caught because the loop found no files rather than because anything reported an error. 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.