2b802e06b6
Measured by the Decoder: the plate reaches alpha 255 in a single frame against ~11 frames of ramp with no input, and the sweep enters at 255 with no ramp where an untouched run obeys its parent's declared t=70..100 gate. A cut, not an acceleration. It advances the ONE SHARED CLOCK, so authored/flow.json's clock: 'shared' stands. 🔴 I IMPLEMENTED THE OPPOSITE FIRST AND REVERTED IT. Their initial report had the artwork animating across the press, which would mean two clocks and an overlay-only jump; I built that (_plate_offset). It rested on a 5-frame window that sat entirely inside the 11-12 frame lag between a scripted press and its effect -- it compared frames where the input had not been acted on yet. A wider pre-registered test refuted it: three elements mid-fade vanish in one frame. 🔴 AND MY FIRST VERSION NEVER FIRED, SILENTLY. It gated on overlay.settle_instant, which is -1 for press_start: that screen declares a 22-unit settle window against SETTLE_WINDOW_MIN=30. The boot has always printed 'settles at t=236' from settle_time(), a DIFFERENT quantity, and I took the printed number as evidence for the field I was testing. Caught only by filming and seeing overlay-view stay flat at 0.0 across the press. ⚠️ The target is BOUNDED, not pinned: the capture puts it inside [100,238] -- past the sweep's gate at 100, not past 250 or ptloop01's exit ramp would return the sweep to alpha 0. settle_time()=236 sits inside that and is where the plate reaches full alpha. New diagnostic --press-at=S[,S...] presses (A) at wall-clock moments anywhere in a boot; --skip-at lives inside the movie branch and fires once, so it cannot reach the title. Marked fragile by construction. VERIFIED on a filmed boot: shared clock jumps 109.4 -> 236.0 and view_units and overlay_units move together across the press.
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
-- and RUNNING.md, which is how you actually start it
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.