aa570b106a
The port measures four elements as rendering too dark against the capture -- ptframe1/2 on the main menu, ptframe3/4 on EXTRAS -- with the shortfall correlating +0.77/+0.80 with the BACKGROUND and only +0.24 with the element's own contribution. That is the signature of a blend that scales what is already there. It asked whether the disc selects one. Three examples, one negative, wider than the one I gave last iteration: * frame_alpha_census -- every T8aD sprite on builds 5 and 6 by alpha. It REFUTES the port's own sharpener: 'neither frame has a single fully-opaque pixel, against ptbase's 99.1 %' is true, and pteff10 (max alpha 130, 100 % partial, no opaque pixel) is measured by the port as NEARLY EXACT. So being wholly semi-transparent is not what makes the frames special. * frame_vs_accurate_words -- all 12 T8aD header words for both screens, plus a per-BIT sweep of +0x04 and +0x08. NO word and NO bit puts the four frames on one side and pteff10 on the other. It also kills my own remaining candidate a second time: +0x08 = 0x8050 is shared with pteff21/22/23 on EXTRAS. * frame_keyframe_unknowns -- the keyframe record's fade, tint, rotation and its two unexplained signed words. unknown_4 and unknown_8 are ZERO on every keyframe of both screens, so they carry nothing here; no frame takes a value of any field that another element does not. Reach: the 60-byte declaration entry, the T8aD header word-wise and bit-wise, and the keyframe record. Four elements, two screens. Not the executable's draw path, which is the next commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
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.