123cfc8561
I have been reading MISSION.md every iteration as instructed and never once audited it, while auditing headings, instructions, env vars and fallbacks everywhere else. It carried three false section headings, each superseded in HANDOFF.md and nowhere else: "🔴 Emulator-side questions are blocked -- the title is not reachable here" False. Twelve emulator runs on 2026-08-30 reached the settled title, gated on the plate pulse, and drove it into the menu, EXTRAS and out of the archive. The two items the section named -- the gamma control and separating 8AX from ptbase -- are UNBLOCKED, not answered, and neither has been attempted. That distinction is kept. "🟡 Needs one more run -- a Japanese-locale capture", describing "one capture we cannot take". Taken twice, both committed, via jp_title_session.sh. And both questions it blocked are closed, one of them confirmed against that very capture. ⚠️ I noticed this section was stale several iterations ago, said so in a message, and did not fix it. "🔵 Needs a human decision -- rotation". Decided and implemented the day it was raised: HANDOFF records "OPTION A IS DONE. The reference renderer rotates", and ui_layout.rs carries the rotated blit with a control test pinning 0° and 360° byte-identical to the unrotated path. The field is now confirmed from the ORACLE too -- +30/-45 predicting AABB heights of 1135.3 and 1301.1 against 1134 and 1303 measured, both under 0.2 %. All three corrected leading with the correction, originals quoted and demoted beneath. Only FACTS were changed; the questions and their gates are untouched, since keeping the document true is maintenance and changing what it asks would be overstepping. METHOD: audit the document that defines the objective, because it is the one nobody audits. A document read only for instructions is never read for review, and the more central it is the more often it is consulted and the less often checked. 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.