d7e4a7167e
Two changes, both measured, neither invented.
1. LEAF CLOCK. authored/rendering.json leaf_clock.title = {start_units 40,
rate 0.514}, from the Decoder's f6-unit8, both numbers off ONE capture. The
title's own rate is measured rather than assumed there (ptcopyright ramps
0->255 over 22 declared units across 22 frames = 1.000 units/frame), which was
the assumption their unit 4 had flagged. Supersedes their earlier 0.463, which
divided by the end of MOTION -- the declared track is stationary from t=540 to
600, so that denominator was short; 0.514 anchors on the loop wrap.
Corroborated independently: the human reported the port looks FASTER than the
game, offered as an impression. 1.0x against 0.514x is exactly twice too fast.
2. A LEAF OUTLIVES ITS PARENT. _draw skipped any element whose PARENT posed
transparent, before _draw_leaf was reached, so ptloop01 expiring at t=250 took
the sweep with it -- while this file's own decode says the leaf runs on its own
timeline and the parent's alpha is not multiplied in. The two were inconsistent
and the silent gate won. The capture settles it: the game submits the sweep
across frames 746..1913 while the parent expires at 956, so it keeps drawing
~950 frames after the parent is gone.
VERIFIED by probing the running renderer at two PRE-REGISTERED instants:
title u=400 -> leaf t=185.0, pteff03 centre 301 (predicted 301),
pteff03a centre 1169 (predicted 1168)
title u=800 -> leaf t=390.6, pteff03 centre 1124 (predicted 1124),
pteff03a centre 333 (predicted 332)
All within 1 px.
Effect at the plate's arrival (title t=236): the sweep's centre moves from 505 --
halfway across the screen -- to -36, just entering at the left edge. The human's
report is that the game's glow begins when the plate appears.
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.