1ef6896f8e
sylpheed-port ran my two-half decomposition on their side and found the thing that passes every check by being absent -- an authored value with no `why` at all. Their first pass flagged 35 of 131; ancestor-aware, the real number was 0. The analogue here is a page citing NO reference data, which my previous gate audit would score "0 missing" and pass. 42 pages carry a measured/decoded/CONFIRMED status; 3 cite no data/ or captures/ path. INSPECTED BEFORE PUBLISHING, per their rule, and all three are false positives, each verified rather than waved through: slb-bank-header-not-a-wave.md cites tests/slb_leading_segment_disc.rs, and that file exists in crates/sylpheed-formats/tests/ -- its evidence is a disc-wide check over 9 519 sound.pak entries plus regression tests. ui-screen-runtime.md carries 26 rows of inline evidence, live guest-memory reads matched field by field against the file. five-screens-acceptance.md is a consolidation page; its evidence is the six pages it links and the numbers it tabulates. 3 -> 0. The real finding is about the EARLIER audit. This corpus carries evidence in at least three forms -- committed data files, inline tables, committed disc tests -- and both checks look for exactly one. "48 citations, 0 missing" is a statement about the data-file form, not about whether the gates are evidenced. The gates are evidenced; the audit was narrower than its wording suggested. METHOD gains their formulation with all four instances -- a first count from a new detector is a measurement of the detector, and all four were caught by inspecting the flagged items before publishing the number -- and the corollary that an audit is narrower than its wording: name the form you checked, not the property you hope it stands for. 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.