6f8211a560
Their closing point was the sharp one: the audit's blind spot fell exactly on values that were well-evidenced. The three SE cues had measured provenance, byte offsets and careful text, and nothing about them looked unfinished, which is why they never declared themselves. So 'not every why needs a kind' does not excuse the other 52. Split by whether the why sits beside an actual value: 39 are section prose, _ blocks and group explanations where a label would be mislabelling to satisfy a counter; 13 are provenance claims and all were unlabelled. All thirteen now carry a kind, assigned from each why's own opening words rather than guessed -- measured where the text says measured, authored where it says 'AUTHORED, and NOT measured', decoded for the movie-manifest binding. Coverage 16 to 30. Two failed the citation check the moment they became visible. bgm/main_menu/loop_why was measured with 1400 characters of prose and nothing openable; it described three watched wraps and cited no file, while the measurements sat in docs/re/data/menu-bgm-loop-measured.txt and -loop-start.txt the whole time. navigation/input_during_transition_why was authored and said 'ask the RE agent' without naming where the question is recorded -- a pointer with no destination. The second is worth a rule: an authored kind still needs a citation, and the thing to cite is the open question the choice stands in for. Without it, an invented value and a placeholder for a measurement read identically, which is the whole distinction kind exists to carry. The denominator is not a target and the tool now says so where the number is printed; 41 remain unlabelled on purpose. The mechanism generalises past this audit: a blind spot that correlates with quality is invisible by construction. The unlabelled entries were not the sloppy ones, they were the ones so well-evidenced nobody thought to mark them, and the audit was measuring self-declaration rather than grounding. Their register measured 83 of 86, 97%, with the identical omission -- never printed. Their three gaps are unregistrable by construction, bare identifiers that would match every live mention, the same limit as my own collision case. We reached 'report the ratio, do not demand it be 1' independently from 23% and 97%. 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.