dee6c495ad
The Decoder caught the title's build-in on the console and found ptlogo_back2eff3 never drawn -- not a miss, but phase: a flash's peak is 2 keyframe units, 0.85 of a presented frame at that pacing, so the console shows a SUBSET on any given play. The warning was that drawing all five would read heavier than the real thing. Checked rather than reasoned about. Sweeping the build-in with --no-hold, the port draws them sequentially -- eff1 at t54-56, eff2 at 58-60, eff3 at 60-62, eff4 at 62-64, eff5 at 64-68 -- never more than two at once, and those only where their declared windows abut. That is the stagger the disc declares. The pile-up was the rest() bug and it is fixed. SO THE DIFFERENCE FROM THE CONSOLE IS PRESENTATION RATE, NOT CONTENT. At 60 fps each 2-unit flash gets ~2 frames; at the console's pacing it gets 0.85, so some are skipped. A frame-by-frame comparison of the build-in against a console capture will show flashes the console missed -- a fact to know rather than a bug to fix. The settled comparison verify-capture makes is unaffected: at t=198 none of the five is drawn. Also recorded: my top-level restriction on the settle window was verified by them rather than merely accepted ([160,236] width 76 against [269,540] width 271 with the leaves in, which is an instant after every top-level element has exited); the 120-unit loop is confirmed from the guest's own vertex colour alpha, observed range 0..80 against a decoded peak of 80, with the decoded ramp fitting at RMS 13.16 against 38.18 reversed; and a trap for any future draw-stream tooling here -- a 2D draw's identity is its vertex geometry, not its bound texture, because these sprites sample large shared pages. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
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.