extras sits at 0.19% differing against main_menu's 0.06%, on two screens of the same family. The signed difference explains it: both are uniformly +9 to +12 brighter in the dark outer columns, in nearly identical patterns (+12.13/+12.29 against +11.63/+11.03 at x=0; +10.60/+9.05 against +10.24/+8.84 at x=960). That is the transfer curve -- gamma > 1 in the darks -- with no dipole, no displacement and no missing element. So the 0.06/0.19 gap is not a difference in fidelity. The thresholded count only sees pixels differing by more than 64 levels, which are text and sprite EDGES, and the two screens have different amounts of high-contrast edge. The level disagreement, which is what a tone term produces, is the same on both. I had taken the ratio of two counts as meaningful -- the bounding-box lesson in a different costume. A DIAGNOSTIC TRAP OF MY OWN: the first pass reported 10 of 18 elements "transparent at rest" on extras -- the buttons, the title, the frames -- and looked exactly like a missing-element bug. `--screen=NAME` without `--time` renders at t=0, and pose_at clamps t to minf(t, settle_units), so t=0 stays t=0. With --time=2.0 it draws 18 of 18. The tool was right and my invocation was wrong, and it reported a WORSE problem than existed, which wastes an iteration rather than hiding one. REFUTATION ATTEMPT, SURVIVED: the Decoder's 239.8 units for palogo_sqex's alpha >= 1 span, which is the denominator of the units-per-frame conversion behind the 9-unit black hold I just authored. Computed independently from my export under the linear ramp the port already uses: alpha first reaches 1 at t=15.0588 and last exceeds it at t=254.8750, giving 239.816 units. Agrees to four significant figures, from different sides of the same record -- which is what makes that constant safe to hold. 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.