c7a4378d37
The end state the human set: Sylpheed holds the port, the corpus and every tool; the Canary fork holds the emulator and oracle. Four repos retire. Eight phases, each with a gate. What matters more than the sequence is the ledger: every absorption claim here was RUN, not reasoned. Reborn's 21 remote + 8 local branch tips -> all ancestors of Sylpheed/main Sylpheed-Godot's 2 tips + the root graft -> all ancestors agent-backups/, 23 refs across 4 bundles -> all present in Sylpheed 3 unpushed pi/* branches, by patch-id -> all 4 patches already on main issues / PRs / releases / wikis, 6 repos -> zero outside Sylpheed Three things the check found that a plan built on the obvious reading would have destroyed: 1. The F1 instrument -- Canary's --pad_file_repeat patch, the one behind the repeat rate now shipped in the port -- is UNCOMMITTED, alongside 4 unpushed commits and a branch contained in no remote. Phase 0 exists for this. 2. xenia-rs has 4 unpushed branches of JIT/multicore/native-threads work. Dropping the emulator is a decision; dropping work that was never pushed is a different act, done by accident. 3. The DuckDB tool is not on master, which last moved 2026-06-15. It is on iterate-4A/apu-xma-stage1, +22 commits, 2026-09-10. On the captures question the measurement contradicted the premise: 193 of 257 files are cited by a page or opened by a tool, and two are fixtures that cargo test opens. 64 are orphans. Phase 4 builds docs/re/ the citation check docs/port/ has had all along -- it already finds 10 dangling citations -- and fixes those BEFORE deleting orphans, so the deletion cannot ratify them. Deleting reclaims nothing anyway: the 118 MB is in history, and the build depends on this repo by tag (formats-pin-2026-09-01, pinned in Cargo.lock). That is Phase 5's explicit fork rather than a default. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.