5a4428ec67
The port asked whether a blend field exists and whether _eff layers draw additively, naming it as their largest remaining oracle gap. Both answers are no and the cause is already decoded. Additive blending is refuted specifically: T8aD +0x04 bit 0x02 as an additive selector was tested and every measure worsens against the capture. The export carries no blend field because none has been found -- the per-draw capture records primitive type, index count, shader hashes, texture bindings and vertex attribute 0, but no RB_BLENDCONTROL, and reading real blend state needs a Canary change that is blocked here. One of their three eliminations is overturned. They ruled out the ptloop sweeps as 399x180 at (441,270) with keyframes holding position constant -- that is the unscaled, unrotated geometry. Measured off a GPU draw capture, the live title submits two rotated quads: ptloop01 at 400x1076 rotated +30.26 degrees centred (992,359), and ptloop02 at 400x1444 rotated -45.28 degrees centred (467,360), the scales being 600 and 800 percent. Two quads at x about 467 and 992, leaning opposite ways, is exactly their signature of darker centre-left and brighter right nearly cancelling. Our own renderer shows the same residual from the same cause, tiles running -38.6 then +33.8 across the band, so it is a shared decode gap rather than a defect in their compositor. The rotation itself is decoded: keyframe block +12, degrees, clockwise-positive, confirmed against a framebuffer capture. So their biggest oracle gap and the rotation question they raised for the human are the same item. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QsEPXWVaEpyfudtR6re1Pd
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.