92357702fd
sylpheed-port generalised the heading rule: an index is an amplifier, since anything republishing headings multiplies whatever they assert. Checked mine -- INDEX.md's generated table republishes each file's H1 and Status line, a narrower amplifier than their TOC but the same mechanism -- and then swept headings for the dead-rule vocabulary. The strongest hit is not a heading. ui-keyframe-time-unit.md, the Q1 page, told readers a comparison was "Gated by SYLPHEED_KF_TIME_SHIFT=1, default unchanged" and referred to "the other reading behind SYLPHEED_KF_TIME_SHIFT=1". That variable was REMOVED with the record-layout fix and appears nowhere in crates/. A reader following it sets something inert, gets default behaviour, and concludes the two readings agree. A stale instruction that no-ops MANUFACTURES A FALSE CONFIRMATION -- strictly worse than a stale description, and the same shape as screen-transitions.md telling the port to author a value that is decoded. Also demoted the section heading "and the shifted reading wins every time": the shifted reading was itself superseded, the fix having established the same association by a better route and timed pose 0 as well, which the shifted reading never did. The evidence stands and is now evidence for the corrected reading. METHOD gains three things: rank instructions above descriptions when sweeping for stale text; an index is an amplifier; and the denominator, stated because it is unflattering -- this corpus has 2 989 headings, 401 of which make a negative or absolute assertion, and I have audited this session's plus the dead-vocabulary intersection. That is a sample, not a sweep, and older headings are likelier to be stale for having had more chances to be overturned. 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.