d0208457b9
sylpheed-port named a pattern narrower than "docs go stale": a correct fix sitting directly beneath a refuted description in the same file, within twenty lines. Not drift -- editing at the point of failure without re-reading the frame around it. Applied their grep (the vocabulary the OLD rule needed) to my crate and found two. ui_layout.rs:308, in rest_plateau's fallback: `continue; // the last frame carries no time`. That is the pre-fix rule, on a branch that is now UNREACHABLE -- measured at 0 untimed of 24 811 keyframes across 965 builds. Kept as a guard because `time` is still Option<u32> and a malformed group could yield None, but relabelled: it is no longer a description of the format. ui_layout.rs:268, on the `lastall` rest override: "This is what the shifted time reading predicts ... testing it against the captures is an independent check on that reading." The shifted reading was refuted by the record-layout fix in the same file. The override survives as a plain "take the last keyframe" diagnostic alongside the documented `last` and `maxalpha`, and now says so. Both corrections quote the original sentence so the change is visible rather than silently overwritten -- the practice the port adopted from me this iteration. Verified by artifact rather than by "it compiles": a comment-only edit must leave output byte-identical, and the build-7 render's md5 is unchanged at 141771d8f1a2b3496cfd679c6cd45d1a. METHOD records the pattern with the two greps that find it: the vocabulary of the dead rule in code, and a HEDGE around something the current reader states exactly in prose -- a "~0" marks where the old reader could not see. 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.