73f5f57966
My fourth position today, and it returns to the port's. Splash B's logo quads in this capture step +17 per present, 14 gap-free steps, four quads agreeing. h3-units-per-frame-measured.md measured the SAME elements at +34 and concluded 2 units per frame. Both are right. With the declared T=15, dA/present = 255*(units/present)/T: h3 capture 27.2 presents/s +34 2.0 units/present 54.4 units/s this capture 51.4 presents/s +17 1.0 units/present 51.4 units/s Units per present halved when the presentation rate doubled. Units per second did not move. The UI clock advances by ELAPSED TIME, not by frame count, and "2 units per frame" was a property of a capture that ran at 27 fps, never of the game. So my 120 units/s is withdrawn: it was 2 units/present x 60 presents/s, and the first factor is not a constant. The movie result is re-explained rather than refuted. 2 presents per decoded movie frame at 51.4 presents/s is a movie decoding at 25.7 fps -- a 30 fps movie at 86% under a slow emulator. The measurement held; the inference assumed the movie decoded at 30/s in real time, which it does not when the emulator is slow. Same shape as the first withdrawal. 60 is now positively supported rather than merely undefended. A time-based clock is immune to dropped frames, which predicts the dwell in seconds is stable across runs at different frame rates -- and it is, across four runs whose present rates differ by 1.9x: 255/4.27 = 59.7 and 210/3.46 = 60.7, both within 1% of 60. h3-units-per-frame-measured.md's conclusion needs demoting: its measurement stands, its law is a single-capture artefact, and it is the origin of the constant this question has thrashed on. Finding 3 is open again with no surviving named cause. 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.