7fd958f50e
Last iteration I hypothesised that the game might not draw pteff03/pteff03a on a settled title, which would have explained three things at once: the flat --at plateau, the 0.32 between-session in-box term, and part of the ~40 residual. The oracle says no. A draw capture of the settled EN title -- gated on the plate pulse, fired at 325.3 s, with exactly ONE emulator verified by count -- shows two quads taller than the 720 px screen present in every one of 132 frames and sweeping in OPPOSITE directions: strip A h=1134 ROT x -109 -> +518 step +6..7 px/frame strip B h=1303 ROT x +486 -> -154 step -6..7 px/frame The rate matches the disc: the declared x track is -639..1521 = 2160 px over a 600-unit cycle = 3.6 px/unit, and at 2 units per rendered frame that predicts 7.2 px/frame against 6-7 measured. Both quads are flagged ROT, which is why their axis-aligned bounding boxes are ~885 and ~1300 px wide where the declared quad is 400 -- consistent with rotation living in leaf records and with `screen render` being axis-aligned only. So the leaves ARE drawn and DO free-run on a settled title. My hypothesis is refuted and sylpheed-port's reading of their `title` curve -- sweep present in a title capture -- is confirmed by the oracle rather than by a render. What this does NOT settle is the tension that prompted it. Both strips cross the adjudication box in x and cover it in y, so two JP captures at different phases should differ there, and they differ by 0.32. Two candidates, neither tested: the two JP shutters happened to fall at similar phases (a ~1 % coincidence for a 600-unit cycle), or build 7's denser logo stack -- the katakana plus the crystalline burst that jp-title-at-rest.txt records as absent from the English title -- occludes the sweep inside that box. A draw capture of the JP title distinguishes them. 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.