71a9e5ad56
check counted more than the others An answer not reachable from HANDOFF is not delivered, and this thread lived in messages and docs/re/. Delivering it: the leaves ARE drawn and free-run on a settled title, so a settled screen is not a static screen; the leaves are identical on entries 4, 5 and 7; how the game advances them is undecodable with reach, four models each refuted by a measurement; and keyframe_units_per_second should stay put because the port's 1.87x table has an input now known to be wrong rather than merely unpinned. METHOD gains the lesson sylpheed-port named, which outlives the thread. Almost every cross-check here runs disc -> exporter -> export against disc -> our reader: two paths that agree because they read the same bytes with the same understanding, and that agree anyway when the understanding is wrong. That is how this corpus produced a build-ordinal error where everything still validated, a two-era comparison with the same binary on both sides, and a rate confirmation that was a prediction 20 % low meeting a measurement 50 % high. The chain that counts ends at the ORACLE, and the single instance this week was the leaves' rotation: +30 / -45 from the file predicting AABB heights of 1135.3 and 1301.1 against 1134 and 1303 in the draw stream. Before quoting an agreement, ask where the two paths diverge -- if it is after the fact in question they are one witness wearing two coats. Also records that a refuted model is a result: four refutations, each with the measurement that closed it, is firmer than any one of them fitting would have been, because the failure this corpus keeps hitting is a model that fits for the wrong reason and nobody checks. 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.