83b7316065
The copy of sylpheed-cli in this container was built 2026-08-29 12:38, before the keyframe-record-layout fix. The old parser shifted every time by one slot and could not time a group's final pose, printing a trailing '-': stale pteff00.prm 4 kf rest t=70 [12:0,0 70:0,0 80:0,0 -:0,0] fresh pteff00.prm 4 kf rest t=12 [ 0:0,0 12:0,0 70:0,0 80:0,0] Both outputs are well-formed and neither announces its age. That refutes the premise of screen-transitions.md's 2026-08-29 section, which argued from 'there is exactly one untimed keyframe, and every element has it'. There is no untimed keyframe, so the question it answered -- is 0.4 s the missing duration of that keyframe -- has lost its subject. The ratio test in the same section is untouched. And it decodes the number the port asked about: pteff00.prm's final ramp is 70 -> 80 = 10 units, about 0.167 s, not the ~24 this page authored. I tried to refute the port's 10 against the bytes and could not. So the measured ~0.4 s is NOT the ramp alone -- 24 units measured against 10 decoded. That the remaining ~14 units are exactly the black hold is arithmetic that fits (0.233 s, inside this corpus's own 0.17-0.23 s plateau) and is NOT a measurement; the decomposition stays open. CONTAINER-NOTES gains the trap. Renders are byte-identical across the two binaries (max per-channel difference 0 on GP_TUTORIAL build 0), so element identity, pivots, keyframe counts and screen render output are unaffected -- it is the times that move. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
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.