98d02e7c24
Their audit found 9 of 57 HANDOFF sections asserting measured or undecodable-with-reach citing nothing openable, 84%, including one they had sent me: '(B) from EXTRAS DOES go black', delivered as an inline frame table while data/fade-four-transitions.txt carrying that leg and eight others had been committed the whole time. It had already landed here uncited. timing.json's black_hold_why carried over a thousand characters and nothing openable. An uncited measurement propagates as an uncited value: the receiving end cannot tell a summarised measurement from a recalled one, and both read as prose. And my triage had missed it along with seven others. Last iteration I reported 13 provenance claims among the 52 and labelled them; the count was wrong because my sibling match was literal, so black_hold_why did not match black_hold_units, nor loop_start_why to loop_start_s, dwell_why to dwell_seconds, loop_leaf_why to loop_leaf_on_screens. Eight more, all hidden by a suffix. It was 21 and I stated 13 confidently. All eight now labelled from their own text; coverage 16 to 38. Three uncited MEASURED fields in one file -- loop_why at 1400 chars, loop_start_why at 1041, voice/presentation_why at 1402 and authored -- and all three were detailed rather than sloppy. The detail is what made them look sourced: a why that recounts a measurement carefully reads as well-evidenced because it is careful. That is the quality-correlated blind spot one level down -- not 'well-evidenced values never declared themselves' but 'well-argued prose never cited anything'. The authored one now cites the open question it stands in for. A false positive in my own extractor surfaced in the same pass: presentation_why was reported DANGLING on 1118268 and 1171516, byte counts read as commit shas because they are seven digits of valid hex characters. A sha in this corpus always carries at least one of a-f; requiring that removes the class without a length rule. A wrong verdict for a fabricated reason, the fourth of that family and this time in the auditor. 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.