348e5d8281
Four models for how the game advances the sweep leaf, four refutations. Frame-locked predicts px/frame unchanged under --framerate_limit; measured -4.348 -> -2.032. Wall-clock predicts px/frame LARGER at a lower limit; it got smaller. sylpheed-port's alternative -- that my samples might be at a fixed wall-clock rate while guest time slows, which would reproduce the direction -- checked rather than assumed: every capture reports 150 frames spanning 1..149, so the capture is indexed by guest VdSwap submissions. And per UI-drawing frame, which matters because at limit 15 only 99 of 150 frames carry draws against 131 at default, gives -5.773 vs -3.687, ratio 1.57, not invariant either. Three measures of one slowdown -- 3.58x on the boot, 2.14x per submitted frame, 1.57x per appearance -- and no two agree. The clock is none of the four and the absolute rate stays unpinned. Recorded as undecodable with the reach stated. Two things the same data does establish. The rotation is confirmed FROM THE ORACLE. The port's export carries rotation_deg +30 on pteff03 and -45 on pteff03a, read from the file. The AABB height of a rotated quad predicts from the declared scale alone: 400x1080 at +30deg -> 1135.3 against 1134 observed (0.12 %), and 400x1440 at -45deg -> 1301.1 against 1303 (0.15 %). Two angles, two scales, both under 0.2 %. Which makes their inversion real. Height 1134 IS pteff03 -- the leaf whose declared track is perfectly linear at +4.0000 px/unit across both segments -- and that is the strip my sign-change gate FAILS. Height 1303 is pteff03a, the slightly non-uniform one, and it passes. The curvature is in the strip whose source is exactly straight, so it is not in the disc: it is in the measurement or in how the game advances the record. 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.