bc241f5d06
Question, look-at and not-covered written before the work, per PROTOCOL's units section. One boot, one A to skip the attract video, then no input so the title builds in undisturbed. The sweeps are the two rotated 600%-scaled strips, identified by size: NDC 1.38x3.15 and 1.39x3.15, matching the corpus's own independently measured AABB height of 1134 px (2*1134/720 = 3.15). Drawn alphas run 8, 24, 33, 50, 58, 74, 83, 100, 107 and 16, 41, 67, 91, 116, 128... pteff03's LEAF alpha is bounded below by 128 (keys 0:255 150:128 540:255 600:255). 8 < 128, so the leaf cannot produce it alone. The parent's alpha is multiplied in. That refutes the port's screen_view.gd decode that "the leaf runs on its OWN timeline and the parent's alpha is NOT multiplied in" -- which is exactly what that file asked for. It flagged honestly that every observation behind it had parent alpha 0, so "the leaf wins" and "the parent is ignored because it draws nothing" were never separated, and named t=100..238 as the separating interval. This capture is in that interval. Bears on F6's original report: the parent ramps 0->255 across t=70..100, so if it multiplies in the sweep is invisible before ~70 and dim until 100. A human reporting it starts late is seeing a real gate -- the parent's ENTRY ramp, not the 238 cluster, which unit 1 showed is an exit. Reach: one boot; quads identified by size against a previously measured AABB, not by name, since the draw stream carries no names. The bound argument needs only that the leaf minimum is 128, which is from the disc. It does NOT establish the combination is plain leaf x parent rather than some other one that also dips below 128 -- only that the parent participates. 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.