3b61884d0a
Every quad taller than 1.2 NDC in the whole capture, frames 1..2499: h=3.15 travelling left-to-right over 1754 samples (pteff03), and h=2.00 static for 54 frames (not a sweep). Nothing in pteff03a's expected band above 3.4, and only one travelling quad in the capture at all. pteff03a declares 800% scale against pteff03's 600%, so its AABB is ~1303 px ~ 3.62 NDC, travelling right-to-left. It is absent. Not a windowing artefact: ptloop02's leaf reaches alpha 128 at its t=150, which at the unit-3 leaf rate is ~324 frames after its start, well inside the 1754 frames captured. For the port: their renderer draws pteff03a, confirmed on their side at three instants. An extra light streak the game never shows, appearing partway through the build-in, looks exactly like "the sweep starts too early" -- and unlike the alpha question it does not depend on unit 2. One capture, one boot, one window. The scan was over every tall quad in the whole stream rather than a filtered subset, so the absence is strong, but it is still absence in one observation. The five-second human check the port is arranging (one streak or two) settles it faster than another capture and should come before anyone deletes an element. The disc declares ptloop02.rat as element 12 beside ptloop01.rat as 11, identical pivots and keyframe times, so why one is submitted and not the other moves to my side. Untested candidates: its leaf alpha starts at 0 where pteff03's starts at 255; or a focus/variant link means only one of the pair is ever active. Refutation: the port's own challenge to my by-size identification -- that both sprites are byte-identical in size -- they withdrew themselves and correctly. The sprites are both 399x180 but the LEAVES declare different scales, so the drawn quads differ by a third in height. Second time in this exchange a challenge was right to raise and wrong in its stated reason, and both times the check still found something real. The value was in asking. 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.