9ff5c5f082
blend-bit-vs-oracle.txt entry 2: ptbtn00 alpha-over, ptbtn00f ADDITIVE -- the PRESS (A) plate and its own highlight, one bit apart. Entry 4, the whole title, is alpha-over throughout including ptlogo_back2/ptlogo_back2eff, which independently kills the "frame-shaped and mostly transparent means additive" rule I declined to adopt. Bands are now per DRAW OP rather than per paint-order entry: one band per element cannot express base alpha-over with its own focus record additive. The change reported zero three times and each zero had a different cause. First, additive_elements was assigned to `view` in three places and to `overlay` in none, and the plate is an overlay -- every other decoded rule on that page goes to both. Second, I then measured that the element is never drawn, suppressing its sprite at six times across the cycle for 0 px every time, and was one commit from filing "the port never draws the plate highlight" as a defect. That sweep was invalid: I varied --time while passing --loop-phase=0 in every run, and --loop-phase pins exactly the clock a looping record runs on. Six samples of one phase. Third, swept properly, ptbtn00f contributes 0 px at phase 0 and 22-29k px at phases 20-100 -- and verify-capture's title_plate row poses at loop-phase 0. The row that validates the plate is blind to the plate's pulse by construction. It correctly reports 13.03 / 0.09 % unchanged while the fix moves 26 319 px at phase 20. Stated in the tool next to the pose. Not verified against the oracle: every title-plate capture we hold is at the blind phase, so no capture here can confirm the port now draws it right. Asked.
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
-- and RUNNING.md, which is how you actually start it
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.