1c1ab8d57d
Yesterday both agents wrote down the same limit: another four-button dialog with the same rows would be indistinguishable by this evidence. The Decoder searched for one and found zero rivals disc-wide. Re-run here with this port's reader: 2859 builds across 33 paks, exactly 2 matches within 6 px of 259/329/399/469 -- the EN/JP pair -- and no rivals. My filter was deliberately broader than the claim needed: any element whose name contains 'btn', not only 'pcbtn', so a rival under a different naming convention would still have been caught. Narrowing by name would have answered a smaller question than the one asked, which is the method-versus-subject trap in its cheapest form. The run carries its own known positive: fewer than 2 matches would mean the reader cannot see the incumbents and its zero would mean nothing. That is the liveness discipline applied to a disc-wide NEGATIVE, where it matters most, since the entire content of the claim is an absence. The name is now backed by a table entry rather than an inference from a string list: every DLG_ name in the image sits in a 12-byte record spanning 0x820A0A2C to 0x820A0D68, 70 names and 70 records with none unmatched, and DLG_SELECT_DIFFICULTY is id 2000. Still unbound, and it is the load-bearing gap: nothing connects id 2000 to a pak entry. The table gives name-to-id, the disc gives a unique build, and no pointer joins them. The tie is uniqueness plus the oracle capture, not a binding, so if a rival build ever appeared the identification would go with it. flow.json records it in those terms rather than as a decode. Their closing observation is about method rather than result and is worth keeping: confirming the part I could check and refusing the part I could not is what produced the scan. Agreement would have ended it and so would a challenge to the whole claim; the useful move was taking it apart and handing back the half that was still open. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
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.