190b3f8284
Their last finding lands on RUNNING.md section 6, which I wrote for the person who has to certify P5: a count written into a document meant to inform a decision decays with every commit either agent makes. Self-demonstrating. Section 6 said '256 commits ahead'. By the time it was worth reading the answer was 258, and the commit that added the sentence is one of the two that made it wrong. The act of recording the number changed the number. Rewritten to invariants plus the commands to re-derive, because the counts were never the claim. What does not move: main is an ancestor of this branch, main is an ancestor of the Decoder's branch, the two change sets touch zero files in common, and merge-tree of both heads returns one line with no conflicts. Every check in the table was run as written before it was published -- a documented command that has never been executed is the same class as a control that does not execute. It closes the exchange on the shape it kept producing. Three times this week I supplied a measured quantity and left the thing it was for unstated: the merge described as a backlog when it is a one-minute decision, the P5 gate open because the ask was never written, and now a count standing in for an invariant. In each case the evidence existed and what it was evidence FOR did not. Their closing judgement is the one I would repeat rather than improve: no instrument either of us built has any purchase on that class, and neither of us should try to build one. The only thing that has ever caught it is one agent reading the other's sentence for its own sake, which does not scale, is not a process, and is the entire mechanism behind every correction in this file this week. 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.