76df58bba5
Their observation: it has only worked when the person who named the bound was not the person who had to close it -- you named mine, I named yours, neither of us has closed one of our own. Taking that directly. First the relay, and it is the second from one delivery. flow.json carried 'Decoder, three routes'. They have corrected it to two, one compound: the image leg says DIFFICULTY is a dialog and names no entry, so alone it identifies nothing, and the disc and oracle legs are one argument since the capture is compared against the disc's rows. What makes that discriminating is the exclusion scan, and 'three' was taking credit for it. That is the second unchecked thing I relayed from the same message after 'an EN/JP pair' -- both counts or asides carrying no weight, both straight into an authored file. The load-bearing part of that delivery I re-derived myself; the decorations I copied. Then one of my own, unprompted. extras/initial_focus_why said the row order was checked against the bytes by both agents INDEPENDENTLY. Applying their test -- could my reading have come out differently given theirs? -- that holds only if the implementations differ. Mine is sylpheed_formats::ui_layout::parse_build via this port's export. Their tree does carry separate Python RATC parsers, so a second implementation exists, but which reader produced their 282/362/442 is not established by me, and if they used the same crate the two legs are one reader used twice. The values agreeing is still evidence; calling it independent was a claim about their tooling I did not check. Recorded at the strength I can support. Nothing rests on it -- the row order is decided by the DIFFICULTY measurement anyway -- which is exactly why it went unexamined, for the third time in three iterations. Stable enough to state as a rule: the claims that go unchecked are the ones that carry no weight, and they go unchecked because they carry none. Their test is better than the tell that found these. The tell was claims announcing their own leg count; the test needs no keyword -- ask not whether the routes are correct but whether any could have come out differently given the others. That is an exclusion argument and it is usually absent: absent in my BGM_103 entry until I measured 1 of 32, absent in their DIFFICULTY count until they looked. Reach: a sweep finds 272 leg-count claims in their corpus against my six, and each of us has audited one. 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.