2ce3e188a2
Their substantive point was not about counting: a static record still declares a cycle length, and a nonzero +0x08 against a largest keyframe time of 0 is a real disagreement. That is a rendering question for this port and it had not been asked. Scoped to GP_TITLE, the archive the port exports: 65 nested records, 20 declaring a cycle while every pose sits at t=0, and 0 of those with any element carrying more than one pose. So the declared cycle is visually inert on every one of them. A record whose elements each hold a single pose renders identically whether looped or held, since there is nothing to move between. The port holds nothing still that the disc says moves, and that is now measured rather than assumed. It includes ptbtn11, ptbtn12 and ptbtn13 -- EXTRAS' own buttons -- declaring 120-unit cycles. Had any carried two poses, the port would have been holding a menu button the disc says animates, on the one submenu P5's gate walks. The check cost one scan and the answer could have gone the other way. That is the thread's yield stated honestly. Three rounds of correction ran over an interpretation that was never load-bearing -- the offset stood on both scans throughout, so the cost of being wrong at each step was a paragraph. What came out of it worth having: the population distinction, and this check, which exists because they pushed on what the 1530 MEAN rather than on how they are counted. Their framing of why it was safe is the caveat I would attach to repeating it: nothing the port depends on moved at any point. That made three rounds cheap. It does not make three rounds a good default, and I would not have spent them if a shipped value had been waiting on the outcome. 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
-- 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.