58069e398d
sylpheed-port refined my ranking: rank silent instructions above loud ones. All of theirs were loud -- wrong paths that error out and announce themselves -- while mine was silent: an inert env var returning a clean, wrong result. Only the silent kind manufactures evidence. The silent surface is enumerable, so this is a sweep rather than a sample: every environment variable the docs name, checked against the code. SYLPHEED_KF_TIME_SHIFT was still live in FIVE doc files after I fixed one last iteration. Two of the five were genuine hits rather than historical quotes: ui-resting-pose.md -- a RESULTS TABLE ROW labelled "with SYLPHEED_KF_TIME_SHIFT=1". Re-running it sets an inert variable, produces the DEFAULT row, and lets a reader conclude the two readings agree. A stale instruction inside a results table is the purest form of the evidence- manufacturing class. HANDOFF.md -- "experiment reachable via SYLPHEED_KF_TIME_SHIFT=1", a live instruction in the delivery contract. And a live gate exists under a DIFFERENT NAME that the docs never pointed at: SYLPHEED_KF_TIME_LEGACY, verified read at ui_layout.rs:595 -- the parser itself, not only the tests, so it does reach screen info and screen render. Both hits now redirect there. Beware the proxy, which is the trap the port named about their own "parsed" check: absent-from-code also flags SYLPHEED_DISC, XENIA_SRC and SYLPH_ISO, which are container paths the brief sets and no code reads. Absent-from-code is necessary, not sufficient, and I checked each rather than reporting the seven raw hits. 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.