82ce9dbaaa
The reach test I deferred twice. sylpheed-port tested three screens across the stale and fixed ui_layout.rs eras, found 0 differing pixels, and concluded the eras explain nothing. Built both eras from source and rendered EVERY composable GP_TITLE bundle through each. 7 of 16 differ. Entries 0-6, 8 and 9 are byte-identical -- which includes title (4), main_menu (5) and extras (6), so the port's result reproduces for the screens they picked. Entry 7 (title_jp) differs by 74 507 px, RMSE 12.409; the two loading bundles by 49 771 px, RMSE 10.078; the four splashes by 23-33k px at RMSE 0.94-1.78. So "the eras explain nothing" is true for three screens and false for the archive. It is specifically false for title_jp, which is one of the two rows their check-all now allows BY NAME with the reason "rest-pose sparkles". Their measurement of that screen was 0 and mine is 74 507; recorded with exact flags as a disagreement for them to check, not adjudicated. Noted that their branch's ui_layout.rs is the stale one (20 ins / 488 del against the pin), so a binary built from their workspace HEAD is the stale era. Two controls, both run first. The binaries genuinely embody the eras: build 5's pteff00.prm reads `rest t=70 [12 70 80 -]` stale against `rest t=12 [0 12 70 80]` fixed. And the renderer is deterministic: same binary, same flags, twice, 0 differing pixels on entries 7 and 12 -- without which every number is noise. Mechanism on entry 7 is a single element, ptlogo_eff3.t32, rest (108,72) -> (98,42). That is the element MISSION.md and ui-resting-pose.md already name as THE plateau-less rest() discriminator, so the era difference on the JP title is our existing open question surfacing rather than a new one. And a trap: entries 10-15 differ by up to 49 771 px with NO rest position change. The rest selection moves to a keyframe at the same (x,y) with a different scale and alpha. My first extraction compared only the rest (x,y) column and would have reported a difference with no cause. A pose is position and scale and alpha. 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.