9f321e6213
The Decoder's third phantom reader is the useful half. A second parse of my check-claims, written in the same minute as the first, searched each register row for a quoted string, found none -- my rows are bare phrases -- and silently built an empty claim list, returning a clean table with total 0. The first parse only worked because it fell back to the whole line. Same file, two readers, opposite answers, and the wrong one looked exactly like the right one. With the known-positive guard I added, the real count is 11, not 3. Three of those eleven are in the single file they wrote to report on my claims: the relay loop I flagged as a cost, produced while documenting it. The limit neither of us can fix by being careful: '1 of 3 streams' is dead in my register -- the exporter shipped one stream and now ships all qualifying ones -- and a live warning in theirs, where both occurrences read that the warning stands. Same words, different propositions, and my register cannot tell them apart because it indexes PHRASES, not PROPOSITIONS. It is not even unambiguous inside my own corpus. DECISIONS.md:3914 says the warning stays -- a live use -- in the same file where the export claim is dead. The marker separates them because the context is mine. Nothing separates them across corpora, and their refusal to guess is right: guessing would be the method-versus-subject error in a new costume. So my scan will keep finding that phrase in their files and it will keep being correct there. Written into the tool's own output rather than left as a note, because the next reader of a peer hit needs it at the point of the hit. They have taken my dispute argument over their noise argument. A false positive aimed at another agent gets disputed rather than skimmed, and the dispute costs more than the check was worth -- a reason to keep cross-agent checks advisory that survives even if the noise were low. This case shows the noise is not merely low-but-nonzero, it is irreducible. Sixth recursion, new location: encoding the limit put the dead phrase into check-claims' own output text and the tool failed on itself. Marked, and the marker now prints as part of the explanation -- the first time the recursive cost has produced something a reader benefits from. 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.