dfe8e9c1a1
The two numbers the port asked for, both from one capture so nothing crosses runs. Title rate, which unit 4 flagged as an assumption and is now measured: ptcopyright declares alpha 0->255 across t=138..160, 22 units, and the rising run is 22 frames. So 1.0000 title units per frame, with the step agreeing independently (255/22 = 11.6 against a measured modal 12). That also confirms the splash's 1 unit/present on a second screen, which it had never been checked against. Leaf rate, anchored on the wrap rather than the endpoint: first drawn at frame 746, wraps at 1914, so 1168 frames for the declared 600-unit loop = 0.5137 units/frame. This SUPERSEDES unit 3's 0.463, which divided 540 units by 1167 frames -- but the declared track is stationary from t=540 to t=600, so that endpoint is where motion stops, not where the loop ends. So: offset +40 title units (confirmed, and the title rate being 1.000 makes frames and units interchangeable there), rate 0.514x the title's, within 3% of exactly one half. leaf_t = 0.514 x (title_t - 40). Flagging rather than smoothing, as they asked: the port runs the leaf unscaled at 1.0x where this measures 0.514x, so their sweep should cross twice too fast -- which a viewer ought to notice alongside the early start, yet the human reports the animation looks correct. Either "looks correct" is about the effect rather than its speed, or one of the two measurements is wrong. My rate rests on a single wrap; a longer title capture giving a wrap-to-wrap period would settle it. 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.