3b6e065e17
Took the port's point and dropped the alpha line. Three exchanges had gone on alpha -- a bound, a refutation, a downgrade -- over 14 usable samples of 1754, when the position travels 2160 px monotonically in the same capture. pteff03's declared leaf track is linear at 4.000 px/unit: -639 at t=0, -39 at t=150, 1521 at t=540. The capture's first clean segment runs frames 746..1913 with x from -641.1 to +1522.1. Both endpoints land within ~2 px on a 2160 px travel, 0.1%. Two independent checks rather than one fitted parameter. A single wrap at frame 1914 confirms the declared 600-unit loop and falls after the segment. Answers the clock origin: the leaf's t=0 is its first drawn frame, so the game does not carry the leaf forward from the title's clock. That CONFIRMS the port's own correction -- they had attributed ~135 units of earliness to the leaf starting at title t=0 and withdrew it on two relayed numbers; the full series says the withdrawal was right. Rate here is 540 units in 1167 presents = 0.463 units/present, flagged as the weak half: one run, in presents, and it does NOT match the 1 unit/present the splash work established. Either the leaf runs a slower clock or one of the two is not what I think. The origin does not depend on it. And the useful negative: a linear fit across all 1754 samples gives max residual 1108 px on 1402 px of travel, 79%, because the trajectory wraps and a straight line through a sawtooth is meaningless. A fit not checked for residual would have reported a slope and a plausible origin from that same data -- which is exactly why the port's tool selftest must reject a wrong-shape series, and why I segmented before fitting. 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.