9b25fd8233
sylpheed-port audited the documents their brief names and found two stale blockers in a table they are instructed to consult, having audited everything else. Mine names eight documents; I had audited MISSION.md and never PROTOCOL, REFUTED, INDEX or CONTAINER-NOTES. REFUTED.md is the dangerous one, because a wrongly-dead entry stops someone re-investigating something live. Checked the keyframe cluster first for the opposite failure -- entries refuted USING the stale time association, which would make their deaths unsound. They are sound: the additive-blend and pivot entries rest on scale values and capture measurements that the association does not move, and the one entry that did depend on it is already struck through. The real gap is the other direction. EIGHT claims died this session -- the fade-out duration "not in the file", the ~14 units as a black hold, the black interval as a load, "(B) has no black interval", ptloop01/02 not free-running, the splash dwells running 8.5 % long, EXTRAS's "structural" n=1, and the gap being determined by the outgoing screen. Every one was recorded in its own page at the time. NONE of them reached REFUTED.md, the file the brief says to grep before proposing anything. Added as a dated section with the true answer after each arrow, following the file's stated format, and each carrying what made it wrong rather than only that it was. METHOD: a refutation that lives only where it was made is not reachable by the person about to repeat it. The pages are where a refutation is argued; the index is where it is found -- the same split as docs versus tool, and only the second one saves anyone. The check is mechanical: after withdrawing a claim, grep REFUTED.md for its noun. 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.