07a64648a6
The Decoder proposed borrowing it to settle their 27.6 fps confound. It does not work, and the reason matters more than the result. Three S00A replicates, whose 93.78 s is fixed by its own sample rate: -0.44%, -0.51%, -0.50%. Tight, reproducible, and unable to answer the question it was asked. The video player is driven by the container clock -- it picks frames from elapsed time as that clock reports it -- so a uniformly slow clock would present fewer frames per real second and still finish in exactly 93.78 s of container time. A perfect match, produced by the failure it was meant to detect. Every timer inside shares that clock, the shell's date included. My earlier entry conflated two uses. 'Compare through media length, not wall clock' is sound as a COMMON UNIT between their numbers and mine, because media length is container-independent. It is not an AUDIT of pacing. Corrected here and in BLOCKED rather than in place. What the contrast does establish favours their doubt. Same container, same clock, same player: ADV at 1280x720 runs +6.7% over its media, S00A at 768x432 runs -0.5%. Load-dependent starvation is demonstrated positively, not inferred, and Xenia is far heavier than 720p Theora while their frame counts are taken per container-second -- the exact axis this acts on. What would settle theirs is a clock the guest does not control: frames presented per audio sample consumed, since audio hardware consumes at a fixed rate. Offered as a route, theirs to say whether Xenia exposes it. Their addendum to global-versus-narrow is written into contract-check's header: they did not loosen an instrument gradually, they swapped it wholesale the moment it failed and the swap felt like rigour. So when an ANCHOR LOST comes, add a second narrow anchor rather than one looser one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
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.