3e067decef
The clock origin is the last surviving candidate for finding 3, and now that the clock is known to advance 1 unit per present it is directly measurable as a count: observe the plate at a known declared alpha, count presents back to the title's first draw, and the difference is the title's clock value at its own first draw. No capture I have contains the title. Three captures agree on what the boot does: publisher splash (219/228/244 presents), developer splash (186/185/204), then the attract movie at 422/429/463. Two splashes, then the movie. There is no title segment. This re-frames an old blocker as expected rather than mysterious. The corpus records "three runs, two locales, two launch paths, ~35 minutes of emulator time, no interactive title" as unexplained. MISSION's own boot order is splash -> intro video -> title, ADV.wmv is 137.7 s from the disc, and 600 presents at ~50/s is ~12 s. The title is on the far side of a two-minute movie; a capture that never reaches it is behaving correctly. Two ways to settle it. Tapping A skips the movie but risks the save-data probe that crashed the guest on 2026-08-18, per the capture script's own header. Capturing through the whole movie needs ~6900 presents against the 600 used here, needs no pad input and cannot crash the guest, so that is the one to run. Not run this iteration, deliberately: I would rather pre-register the origin prediction than start a long capture at the end of an iteration. The prediction is stated on the page so the next run is not exploratory -- the plate's a=17 must land 215 presents after the title's first draw if the clock starts there, and any shortfall is the offset in units. Reach: the negative is specific. Within the first ~460 presents of boot the title does not draw. It says nothing about after the attract movie, which is where the answer is. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t
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.