a30761f128
Same capture, counts only. Title's first drawn element is frame 706; the sweep is first submitted at 746 and first ON SCREEN at 747, so +41 frames. For scale, the plate's declared t=236 is frame ~942 at 1 unit/present -- 195 frames after the sweep is already visible geometrically. Named rather than folded in: that comparison assumes the title's first drawn frame is its t=0 and that its clock runs at 1 unit/present. The 41 is a raw frame count and carries neither. What it settles: POSITION does not gate the sweep late. So if a human sees it start when the plate appears, the gate cannot be where the quad is -- it has to be how opaque it is. That puts the whole of F6 on unit 2, which is amber: does the parent's alpha multiply into the leaf? The parent ramps 0->255 across t=70..100, so if it multiplies the sweep is invisible until ~70 and dim to 100 (a real early gate); if it does not, the sweep is fully lit from +41 frames and the human's report has no mechanism yet. The disagreement has narrowed usefully: before this unit "starts when the plate appears" had two candidate mechanisms, position or alpha. Position is now excluded by measurement. Refutes my own unit 1 framing. I wrote that a quad can be "fully opaque and entirely off-screen" and offered the travel as the likely explanation. It is not -- the sweep is on screen at +41 frames, nowhere near the plate. The travel explanation is dead, and I record it because I proposed it and it steered the port's reading of their own renderer. 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.