e5a14cde56
The pulse has been implemented since 2026-08-30: authored/timing.json
looping_focus_records maps press_start/ptbtn00 -> ptbtn00f at period_units 120,
kind measured. The Decoder's independent figures (120 units, peak 80, ~51 of 60
frames) match the declared record on all three counts.
Verified rather than argued: 502 samples from a filmed boot folded onto the
declared 120-unit period reproduce the declared curve under ONE solved gain --
4.2% rms, with the flat top (phases 36-47, the alpha-80 plateau) and the flat
zero (108-119) both landing where declared. A sine of the same period fits 5.7x
worse, so it is the declared SHAPE and not just the period.
🔴 How I got it wrong: I measured 'does it return to dark'. It never does, BY
DESIGN -- the pulse is an additive glow over a base held at 255. I recorded an
11.6% ripple at a ~120-unit period, which WAS the pulse at exactly its declared
period, and attributed it to background leaking through my glyph mask.
I tested a property the feature was never supposed to have, and the authored
entry said so in its own words before I started. I read the disc's ptbtn00
keyframes, saw 244:0, and never read the port's own configuration for the element
I was measuring.
No code change. The arrival half of the page stands.
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.