c184f8a783
sylpheed-port diagnosed their four instances of fixed-code-under-unfixed- description as a habit rather than inattention: corrections are ADDITIVE. They append a correction block and leave the original standing above it -- right for a record, wrong for a statement, because a reader takes the first assertion. Their fix is to keep the quote but demote it grammatically. Applied their diagnosis here and found a worse instance than theirs. screen-transitions.md carried the heading "### ❔ The fade-OUT duration is not in this field", with a section beneath it that is false in every sentence: "The fourth block has no time -- a group's last block stops 4 bytes short and that word is already the next group's element index. So the disc gives the ramp's target (black) and not its length. That duration is measured below, and the port is authoring it." All pre-fix. The record-layout fix times a group's final pose, so block 4 carries t=80 (menu), 74 (EXTRAS) and 269 (title), and the fade-out ramp is DECODED at 70->80 = 10 units, 64->74 = 10, 261->269 = 8. The section told the port to author a value that is decoded, and its correction sat 78 lines below. It also carried the dead rule's exact vocabulary -- "stops 4 bytes short" -- which is the grep I built for code last iteration and never ran against docs. Rewritten leading with the correction, the original quoted and demoted beneath it. METHOD: corrections are additive by default and that is wrong for a statement; the worst form is a HEADING, which asserts with maximum reach and minimum context, and a reader scanning headings never reaches the retraction. Audit headings first. 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.