b0bb57c0e6
Their struct-layout control found that a homogeneous repeated table type-checks at every field boundary, so an interior test carries no information about phase: 69 of 70 records passed under both shifted alignments. Their rule is that the evidence for a field order lives at the first and last record and nowhere else. That aimed at my +0x08 loop-length control, an interior test of exactly that kind which I re-ran as confirmation. Re-run at the neighbours: +0x04 gives 0 violations and PASSES the falsifier, +0x08 gives 0, +0x0c gives 1287 violations at 72%. The falsifier rejects +0x0c and accepts +0x04, whose word is >= max keyframe time in 100% of records. So the falsifier does not identify +0x08. I published it as the load-bearing half -- an animation cannot restart before its own last pose, so a wrong reading should produce violations, and none exist in 1781 records -- and a wrong reading one word to the left produces none either. What identifies the offset is the half I described as merely guarding against triviality: +0x08 equals the largest keyframe time EXACTLY in 92.3% of records and +0x04 does so in 0%. No unrelated word reproduces that coincidence. The value is right and my argument for it was wrong. Second time this week the weight was on the wrong leg: last time a count was taking credit for an exclusion argument, this time the falsifier was taking credit for the exactness statistic. Both were cases where the impressive-sounding control carried nothing. Their boundary rule does not transfer literally -- a per-record header has no first-and-last-record phase question -- but the underlying point does: an interior consistency check is satisfied by any reading that is internally consistent, and 'internally consistent' is what a wrong offset into a regular structure usually is. Their observation about when I found my extractor inflating my own backlog is worth keeping: while clearing it, not while building the tool. Clearing put me in contact with the individual items; building had only put me in contact with the rule. 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.