befcb74780
h3 says 2 units per guest frame, units-per-second-measured says time-integrated at 56.8 units/s, and my own page says 1 unit per present. All three rest on real data and one mechanism explains all of them: the clock advances one unit per VBLANK, and presents can be dropped without the clock caring. That accounts for the corpus's steps of +17/+34/+51 (1, 2, 3 vblanks between two logged presents), for the same animation spanning 21 labels in one capture and 33 in another -- which a strict per-present clock cannot produce -- for h3's three plate steps of 23, and for my own 14 consecutive steps of 17 in a run that dropped almost nothing. My "1 unit per present" was nearly right and named the wrong clock. At --framerate_limit=30 Xenia vblanks at 30 Hz and the guest presents ~30/s, so presents and vblanks coincide and the test could not tell them apart. It correctly refuted time-integration; it could not locate the tick. Solid: the RATE follows the vblank rate. 255 declared units take 4.26/4.16 s at a 60 Hz vblank and 8.45 s at 30 Hz -- 59.8/61.3 against 30.2 units/s. A time-integrated clock predicts 4.25 s in both. So a console at 60 Hz gives 60 units/s, and the port's value stands on a third independent route. Not solid: per-vblank vs per-present. My step samples are ~12 per run, which cannot separate them, and I say so rather than reading 18% vs 0% of two events as support. The load-bearing observation for the mechanism is the corpus's 21-vs-33, not mine. The discriminating experiment is named and not run: log Xenia's D1MODE_V_COUNTER beside each present and check every step is exactly 17 x (vblanks elapsed). 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.