cce31cb592
The Decoder named the elements under my hot tiles and had to test both coordinate
readings, because design space and the comparison frame differ by the capture
transform. I did not need the transform: the port has a mod tree, so shadowing a
sprite with a transparent PNG and diffing my own two renders measures the
element's footprint directly, in the comparison frame, assuming no convention.
Ranked by residual density on each element's own visible pixels: ptframe1 22.72
(9.47x the frame mean), ptframe2 13.09, ptmsg 8.46, pteff12 4.98, ptbase 3.34.
That refutes the hypothesis I came in with. I predicted the EFFECT element, since
blend mode is recorded as undecoded in screen.rs and a miscomposited effect would
be tonal and displace nothing. It is the frames; pteff12's ratio is largely
inherited from containing ptframe1. The mechanism may still be right, the element
was wrong, and only ranking rather than confirming showed it.
And it is not an edge effect: ptframe1 and ptframe2 are the only elements whose
residual is higher on FLAT pixels (25.41, 16.54) than on edges (19.85, 9.82).
Signed, ptframe1 renders 88.4 against the capture's 129.1 with 0.1 % of pixels
render-brighter. Body intensity, one direction, after a global tone LUT.
Filed in BLOCKED.md against HANDOFF 5a7f34d as an ask for the blend/alpha bits. I
am not brightening them to match.
Also: suppressing the FOCUSED button changed zero pixels, opaque magenta included,
while ptbtn02/03 change thousands. That looked like a defect and is not --
screen_view.gd:746 documents that a focused button draws its record instead of its
base, covering it at 100.0 %. The null re-derives that claim at a stricter
standard than the measurement behind it.
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.