06aa031980
sylpheed-port confirmed "nothing declared predicts the gap" from their export independently, and deliberately declined to search combinations: four pairs against many candidate two-screen functions fits by construction. Right call, and it applies to me unchanged. So this iteration adds a PAIR rather than a fit. menu -> a second screen outside GP_TITLE, reached by stepping the cursor two items before arming. The button is not controlled -- there is no focus readout -- so the destination is identified afterwards by its draw signature: incoming primitive [255] at 7-9 draws/frame, against the first run's [127] at 12-13. Different screens. Outgoing quad rises 25, 51, 102, 229, 255 across frames 37-42, then at frame 44 the new screen is already drawing. NO empty frame anywhere. GAP = 0. So the menu as origin gives four values across four destinations: title 0, EXTRAS 1, other-1 1, other-2 0. The same origin yields both 0 and 1 depending on where it goes, while the two repeated pairs stay internally identical (3,3,3 and 2,2). Further evidence for the ordered pair over the origin. Recorded as an observation with its counter-example rather than fitted: the incoming screen's own full-screen primitive is [255] where the gap is 0 and [127] where it is 1, which suggests a screen beginning from opaque black needs no blank frame. That FAILS on menu -> EXTRAS, which declares a black backdrop and still gives 1. Nine transitions against many candidate functions is the construction the port declined to search, and I am not searching it either. 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.