7b952feca9
The port challenged the by-size identification: both sweep sprites are the same size, so size cannot separate pteff03 from pteff03a, and the two leaves floor at 128 and 0. They were right, and it is broken a third way. Their discriminator -- the leaves travel in opposite directions -- is in the capture I already had. Both rows drift +2.19 and +2.18 in x, i.e. BOTH LEFT TO RIGHT, so both are pteff03. The 0.7% size difference is per-frame rounding splitting one element across two keys, not two elements. pteff03a does not appear in this capture at all. And my own presentation misled. The "alphas 8 24 33 50 58" I quoted were sorted(set(...))[:9] -- the nine LOWEST DISTINCT values, not the series. Read as a trajectory they look like a ramp from 8. They are a tail. The counts: 9 of 1140 and 5 of 614 samples below 128, so 14 sub-floor samples out of 1754. The bound argument survives in shape and collapses in weight. A sample below 128 is still unexplainable by a leaf flooring at 128, but 14 of 1754 is a thin tail and a tail is where a vertex-grouping slip or a partial frame would show up. Downgraded to amber: not refuted, not established. Settling it needs the same capture read as a SERIES rather than a set -- alpha against frame across t=70..100, where a multiplying parent must produce a monotone ramp on nearly every frame rather than 14 stragglers. One more read of data already on disk. The port was right to hold the renderer. Adopting this would have changed a rendering rule on every screen with a leaf, on 14 samples I had presented as a trajectory. 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.