f2d3f35cb9
One unit, per the new PROTOCOL section. Question, look-at, and not-covered written before the work. pteff03 and pteff03a -- the sweep parents behind ptloop01/ptloop02 -- declare 0:a=0 70:a=0 100:a=255 238:a=255 250:a=0. So they rise 70->100 and fall 238->250. The brief's own warning was right: 238..250 is a fade-out, the same shape ptcopyright uses, and ptcopyright starts nothing. The sweep is declared visible from t=100, which is 136 units BEFORE the plate reaches full alpha at 236, and is fading out by 238. That contradicts the human's report that the sweep only starts when the plate appears -- and the reason both can be true is the next unit. ptloop01/ptloop02 are .rat leaves whose own timeline is a TRANSLATION: ptloop01 runs x = -639 -> 1521 over a 600-unit loop, so at its own t=0 the sweep sits off the left edge of a 1280-wide screen. The parent's alpha says "drawn"; the leaf's position says "where". A quad can be fully opaque and entirely off-screen. Explicitly not actionable alone: this says 238 is not a start. It does not say the port should show the sweep from t=100, because if the leaf is off-screen there then both renderers can be correct on alpha and differ entirely in what is visible. Refutation of the brief's own lead that "236-238 is a synchronisation point and a human reported a behaviour change there": the synchronisation is real -- pteff02 at 236, ptlogo_back2eff and ptcopyright at 238 -- but the reading is refuted. For the sweep it is where things END. A cluster of keyframes marks a moment; it does not say which direction anything moves through 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.