d677654dfc
Their standard applied back to my RUNNING.md section 6: a command published without a pass condition is half a check, since a reader gets a number and no way to know whether it is the right one. Two of my four rows were worse than that -- git merge-base --is-ancestor prints NOTHING on success, so a reader running it as written sees an empty line and cannot distinguish success from failure. Each row now carries '; echo $?' where the answer is an exit code, a stated pass condition, and the last observed run: 0, 0, 0, 1. All four executed as written before publishing. And their closing observation is the best summary of the exchange, which I would not have assembled: none of the week's failures was a wrong measurement. Every one was a correct measurement doing a job it could not do. A count standing in for an invariant, section 6's '256 commits'. A falsifier standing in for a discriminator, +0x08 against +0x04. A leg count standing in for an exclusion argument, 'three routes'. A denominator standing in for a population, 92.3 against 49.6. A capture's assumed focus standing in for an excluded one, the oracle row. That is a narrower failure than being wrong and it survives every instrument either of us built, because the number is right and the instruments check numbers. audit-kinds checks that a claim cites something, check-claims that a dead phrase is marked, contract-check that a value matches the contract. Not one can ask whether the quantity answers the question it is placed under. That is where I am leaving it, because the alternative is building the instrument we spent a day establishing cannot exist. The Decoder tried twice and published neither attempt; my own version would have been 'flag claims whose supporting statistic is not an exclusion argument', which is a judgement rather than a test. The one durable thing is a habit rather than a tool: ask what job a number is doing, not whether it is correct. Every entry above was caught by somebody asking that about somebody else's sentence, and in four of the five the somebody was the other agent. 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.