8dfa0ebac5
Answers the open half of the A-press diagnosis, and most of the answer was already in the tree. The faulting runs booted with logged_profile_slot_0_xuid = "" -- their own config dump -- while a profile existed (Found 1 Profiles). With nobody signed in, A takes the state-0 branch of sub_821D03A0 and calls XamShowSigninUI(1,1); Canary raises its Sign In dialog with a no-op close handler and nothing in an unattended run dismisses it. 85 instructions verified against the image, 0 mismatches; the state-3 branch is XamShowDeviceSelectorUI, already ruled out by storage_selection_dialog = false. The correlation runs through the tooling: boot_menu.sh passes the profile flag and Q4/Q5 pressed all five buttons; frame_clock.sh, which produced the faulting run, does not. So there is no blocker -- boot with boot_menu.sh. Flagged as retrodicted rather than A/B tested, since I have not myself booted both ways and pressed A. The uncomfortable half: canary-scripted-input-traps.md section 3 already named the sign-in dialog WITH a committed capture, and boot_menu.sh's header already carried the mechanism and the 8.4 million figure. The fault page searched for the cause it had hypothesised and never searched for its own symptom. Added to METHOD.md, along with the more expensive lesson -- a measurement whose only record is a script comment is invisible to the document that needs it. What this session did add is the join: that the known blackout is what drives an unbounded guest queue into a failed 128 MB allocation. 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.