3e525756bf
Set out to measure menu -> EXTRAS, the reverse of the pair measured at a 2-frame gap, to test whether the black gap is a property of the screen pair or of the direction. The run did not do that. A three-part patch to fade_decompose.sh asserted two of its three replacements and left the third -- the branch condition -- unchecked. It silently failed, so WHERE=menu2extras fell through to the `title` branch. The capture is well-formed and is of a different transition than intended, which is the build-ordinal error's shape again: right-looking output for the wrong object. What caught it was the log LACKING the navigation lines the intended branch prints; the data itself looked entirely fine. Salvaged, because the accidental transition is one already measured twice: run outgoing ramp black incoming decay 1 67-70: 63,127,191,255 3 73-77 2 64-67: 63,127,191,255 3 70-74 3 92-95: 63,127,191,255 3 98-103 Three independent runs, gap = 3 frames every time, outgoing ramp byte-identical in all three. That takes "the black gap is not a load" from two replicates to three, and makes the 4-frame outgoing ramp as solid as anything measured here. menu -> EXTRAS remains open; the condition is fixed (with an assertion this time) and the run has not been taken. METHOD gains two entries. Assert every edit, not most of them -- and have each branch announce itself in the log, so a run that took the wrong path says so before its numbers are read. And: "appears nowhere in crates/" is a claim about a TREE. sylpheed-port found SYLPHEED_KF_TIME_SHIFT live at ui_layout.rs:497 on their branch, which carries the stale era; both statements are true of different trees. With main 145 commits behind and each agent on a topic branch, any claim about what the code contains needs its ref attached. 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.