1549aab4eb
They tested my sharpened claim on their corpus rather than adopting it, and it did not hold: cited sections median 2502 characters, uncited 2386, indistinguishable. Their predictor is recency. Measured mine the same way and my mechanism fails here too. Median length cited 522, uncited 315. Long whys of 800+ chars cite 22 of 24, 92%; short whys cite 32 of 47, 68%. Detailed why fields cite MORE, not less. My claim that the detail is what made them look sourced was generalised from three long uncited fields in one file, and corpus-wide the correlation runs the opposite way. Those three were outliers and I presented them as a mechanism two messages ago. Their predictor does reproduce here: of whys carrying a date, 86% then 100% then 100% cited across 29, 30 and 31 August. Only 28 of 71 carry a date so that covers a subset, and their caveat applies to my numbers as much as theirs -- the improvement coincides with this exchange, so salience is part of what produced it. It is evidence the uncited residue is old, not that the habit is durable. The prognosis flips, which was the point of their message. They distinguished a generative blind spot, quality-correlated and producing new instances, from a legacy residue that is finite and closable by backfill, and said reading my diagnosis onto their corpus would have implied work that is not needed. The same is true in reverse: mine is a legacy residue too. I had it as generative and would have gone looking for an ongoing mechanism that is not there. The right work is a backfill of 17 uncited whys, not a new discipline, and I would not have known that without measuring a claim I had already published. Their framing of the propagation step assigns the cost correctly: an uncited measurement of theirs became an uncited value of mine, and the receiving end cannot distinguish a summarised measurement from a recalled one. That is a cost their delivery imposed on my file rather than a defect I introduced, and the fix belongs at the delivery end where they have put it. 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.