9540909a6f
TWO RESULTS, both correcting things I had written. THE NARROW SETTLE WINDOWS ARE NOT A GAP. Adopting the settle instant left main_menu and extras on per-element rest() -- windows of 12 units, below the 30-unit bar -- and I recorded that as something left behind. rest() is malformed only for a TRANSIENT, and the transients are precisely on the screens whose windows are wide: title (76) has ten, publisher_logo (190) and developer_logos (145) have one and three, and main_menu and extras have NONE. The discriminator is returning to dark far before the screen's own end -- ptlogo_back2eff1 is dark again at t=58 while the title runs to t=269 -- as against the ordinary fade-in-hold-fade-out every menu element has, where rest at 255 IS the settled pose. Not claimed as a rule: two screens having narrow windows and no transients could be coincidence, and n=2 is where I have gone wrong before. REFUTED, MINE: "the menu residual is localised on the ptloop sweeps", which I have written twice. It came from reading the BOUNDING BOX, which sat at (441,230) -- the sweep position. Sweeping the leaf's phase against the live-menu capture: 0.063% at t=60, 0.183% mid-screen at t=350, 0.061% parked at t>=600. With them parked the box is 834x358 at (445,167) -- the button column, where the focus signature lives. On extras the same test moves the box (398x295 at the sweep position, then 736x525 spread) while the magnitude barely changes, 0.192% against 0.200%. So the box moves with the sweeps and the residual does not. A bounding box over scattered pixels tells you where the outermost differing pixels are, not where the difference is -- and I had been quoting it as if it localised a cause. verify-capture prints that box, so this is a caution about reading my own tool. And a first piece of evidence on whether the sweeps loop: the disc gives one pass ending parked off-screen, ORACLE-CAPTURES says they "move continuously" which I had read as implying a loop, and the idle menu capture matches best with them OFF-SCREEN. One capture and a weak instrument for an absence, but it is the first evidence either way and it points against looping. 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.