59a613c71f
The port asked whether the PRESS (A) plate pulses and with what period, framing it as "does the timeline loop at 244 or does something else drive it". Both halves of that disjunction are wrong about ptbtn00. ptbtn00 ramps, holds, extinguishes at t=244 and stays out. The pulse is ptbtn00f -- the plate's focus/glow variant, reached through focus_link and carrying no top-level element of its own -- which declares a 120-unit loop from the disc. A reader looking only at ptbtn00 sees a one-shot because the looping element is the one a declaration-order walk never reaches. Same element that needed the by-name accessor in ui_layout, for the same reason. Cross-check that makes it more than a stopwatch reading: 120 declared units at the rate law is 2.000 s at 60 Hz, against a measured mean of 2.24 s over four intervals -- 12% long, the direction and roughly the size Canary's pacing produces. Stated plainly as what it is not: the port asked for a per-frame series and this is not one. The four intervals come from the screenshot probe, the weaker instrument, carrying a wall-clock duration off an emulator with load-dependent pacing -- the class that has cost this corpus four withdrawn timing claims. The strong instrument has never reached this screen: five attempts, blocked by wall-clock timeout, frame cap, a self-matching pkill, and the title sitting past the 137.7 s attract movie. So the fact and the period are answerable now; the trajectory within a cycle is not, and I am not inferring its shape from declared keyframes when the whole point of the splash exercise was that only a capture confirms shape. 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.