ffde5abd94
The port raised a real caveat: my earlier scans filtered on height (>1.2 NDC) and sample count (>=20), so a population of many small lights would have been invisible to both by construction. Dropping both filters, over the whole title era: 59 distinct shapes, 2 moving, 57 static, and ZERO small moving shapes. The two moving keys are the rounding-split halves of one element, pteff03. So there is exactly one moving quad on the title, 883x1134 px. That answers the human's actual uncertainty -- whether the game renders one light per line or one light covering several close lines. It is the second: the multiple lights are painted INTO the texture of a single large sweeping sprite, not drawn as separate moving objects. A port reproducing "several lights" as several elements would be modelling the wrong thing. The port's caveat was right to raise and the check excludes the population it warned about -- third time in this exchange that asking was worth it even when the specific worry did not apply. What I have NOT done, and it was the literal ask: the human asked for screenshots and I have taken none. I answered the counting question from the draw stream because it is the stronger instrument for how-many and how-big -- it reads the guest's vertex buffer rather than pixels and cannot miss a faint light. But "what do the lights look like" is a question about an image and the draw stream cannot answer it. That remains open. Reach: one boot, one window, every quad in the stream. Static elements are not counted as lights -- 57 exist and some may pulse in place; this unit counts motion, not brightness. 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.