a9b6e78c8f
Applied my own log-line rule to my own instrument first, which is the "rule written down is not a rule applied" failure I have on record three times. Every branch of fade_decompose.sh now announces its EFFECTIVE configuration -- derived from the variables in force, not from $WHERE, per sylpheed-port's sharpening -- and the run REFUSES if no branch announced itself. That is the guard that would have caught last iteration's silent fall-through at a glance. With it in place, took the measurement that failed last time: menu -> EXTRAS, the reverse of the pair measured at a 2-frame gap. Navigation verified both ways (extras margin 11.23, back on menu 11.60) and the config block confirmed the right branch. Result: outgoing quad rises across 5 frames matching build 5's declared 10-unit close, then ONE logged empty frame. Quoted as 1 with an upward uncertainty, since its two neighbours carry no frame header at all. Five transitions now order by the screen being LEFT: menu -> title (B) 0 outgoing menu menu -> EXTRAS (A) 1 outgoing menu EXTRAS -> menu (B) 2 outgoing EXTRAS title -> menu (A) x3 3,3,3 outgoing title Direction is ruled out: EXTRAS->menu (2) and menu->EXTRAS (1) are the same pair both ways and differ. Button is ruled out: (B) gives 0 and 2, (A) gives 1 and 3. Incoming screen is ruled out: an incoming menu takes 3 from the title and 2 from EXTRAS. NOT a rule, and recorded as such. Three outgoing screens with one value each means "each outgoing screen has its own gap" restates the data rather than predicting, and nothing declared predicts it -- outgoing closes are 5,5,5,4 frames against gaps 0/1,2,3, inverted if anything, on three points. What it changes for the port: a UNIFORM black_hold_units is now positively excluded rather than merely unsupported. 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.