2bf93916bb
The Decoder raised it and could not test it: if the port ran both leaves on one
rate they would stay locked and drift ~118 units per cycle. The leaves declare
600 and 720.
Pre-registered, then measured on a real boot. At raw leaf clock 4873:
pteff03 span 600 -> measured 72.6 (fposmod 73)
pteff03a span 720 -> measured 552.6 (fposmod 553)
The port takes each span from that leaf's OWN keyframes, so they were never
locked. 17748 samples, title clock reaching 9745 -- the sweep loops 162 s in.
🔴 Two false alarms of mine on the way, both the same mistake:
- used --time (which sets frozen and bypasses the holding clamp BY DESIGN) to
ask about RUNNING behaviour, and nearly reported the whole title vanishing
past t=250. On a real boot settle_window [160,236,198] clamps to t=198 and a
filmed frame at view_units 6733 shows the complete title.
- read a probe going quiet as the feature stopping. Two runs ended at u~236;
that was the RUN ending, not the sweep. With a film attached the same probe
reaches 9745.
Both are the frozen-sweep lesson again: the diagnostic that pins the clock cannot
answer a question about the clock running, and an instrument going quiet is not
the subject going quiet -- the same shape as a count of zero meaning only that
nothing reached the reader.
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.