ba3f490c67
Three things this iteration, and the middle one is the human's doing. P7 -- GATE MET, with an artifact. The path had been wired for some time (then_video S00A, skipped_chain, after_video -> title, and S00A.ogv in the export) and NOBODY HAD RUN IT. A milestone is done when its artifact exists, not when the wiring reads correctly. Pre-registered: unskipped, S00A is 93.78 s of media, so it should end on its own at ~94 s and hand off to title. Measured: video ended at 94.13 s -- +0.35 s, 0.4 % -- then -> title, plate raised, script complete at 96.83 s. Both predictions held. docs/port/p7-gate.md. And it genuinely decodes, checked because "ends at the right time" does not prove it: 45 frames in a 2.03 s window, 244 in an 18.91 s one. Scales with the window, sub-linearly, at the software fill ceiling -- those two runs predate the GPU. The counts are upper bounds and the port says so itself. Free corroboration of the fill-rate finding, from a direction it was not designed for: the unskipped run reports main_menu at 60.3 fps for 94 s, because the screen never changes during a movie. Same process, same container, same screen: 60.3 fps with one full-screen video texture on top, 9.7 fps drawing the menu's five additive full-screen quads. ❌ THE FINDING-4 FRAME-RATE CANDIDATE IS DEAD, tested rather than argued away. The human activated a hardware GPU in both containers; Godot takes it with no change on our side (NVIDIA GTX 1070 Ti, Vulkan 1.4.312, Forward+): publisher_logo 17.3-25.0 -> 69.4 fps developer_logos 16.7-22.8 -> 69.1 title 12.7-17.2 -> 61.1 main_menu 9.7 -> 59.6 Pre-registered that 5-7 full-screen textured quads at 720p is trivial for that card and the fade would get its full 45 steps. At 69 fps the 45-unit build-in gets 52 drawn steps and the companion glow's 15-unit rise gets 17 -- MORE frames than declared units, so every declared alpha is drawn and the quantisation is absent rather than reduced. So every candidate for finding 4 is now dead: keyframes vindicated against the vertex stream, companion quads drawn, blend space matching, settled pose at 0.01 %, no post-process pass, and the frame rate drawing every declared step. The port has nothing left that is KNOWN to be wrong about the splashes -- which is a statement about our knowledge, not about the port. The human saw something and nothing we can measure reproduces it. The next play-test is now the highest-value thing on this focus, and the rate line will say 60-something. One figure did not improve: main_menu's worst gap is 117 ms on the GPU against 150 ms on llvmpipe, essentially unchanged while the mean improved 6x. A hitch that survives a 6x fill speed-up is not fill. Likely first-frame cost, STATED AS UNTESTED, recorded rather than chased. check-all now asserts the display before any Godot step. Xvfb does not survive a container restart and LEAVES ITS SOCKET BEHIND, so Godot reports "X11 Display is not available", falls back to Wayland, fails that too, and exits non-zero -- and every Godot-backed step would have gone red for that one reason. Cost me one run before I noticed. Checked with xdpyinfo rather than by looking for the socket, because the stale socket is what makes it confusing. Also recorded from the P7 run, neither chased: Godot reports 4 leaked ObjectDB instances at exit on that path, and the menu bed keeps playing under the movie (already an open ask -- does the menu music duck?). Not settled: the 117 ms menu hitch; H6's +0x04 exposure; H1 (with the Decoder); the four red verify-screen rows; and what the human actually saw. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018AHUQvXGyNcKonSEWsgWcX
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
-- and RUNNING.md, which is how you actually start it
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.