Sylpheed port agent 9d3b86c881 port: quantify the merge gap, and write down what P5's gate actually asks
The Decoder closed with the fact that gates everything: main is about 234 commits
behind their branch, so nothing either agent decided this week is reachable from
it. That is also where P5's gate sits, and it is the one open item whose framing I
own.

Measured from this side: 256 commits ahead of origin/main and 0 behind, so main is
an ancestor and the merge is a fast-forward with nothing to resolve. 58 files --
the exporter and its examples, the Godot scripts, authored/, tools/port/ and
docs/port/.

RUNNING.md gains a section 6 saying what a person is actually being asked to do,
in three lines: run --boot --play, walk the table, and say whether it behaves as
described -- NOT whether it matches the game, because that comparison is the
oracle's and is already asserted by check-all.

That distinction is the point of writing it down. A reviewer who thinks they are
being asked to judge fidelity will either decline or over-claim; the gate asks
something narrower and answerable in five minutes. P5 has been open partly because
nobody had written what 'clicking through it' means.

What this does not do is meet the gate. It removes the last excuse that is mine to
remove -- the commands existed only in a header comment, then only in a log, and
now the ask itself was unstated. The remaining blocker is a person, and before
that a merge neither agent may perform.

BLOCKED's contract row now carries both directions quantified rather than
described.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
2026-08-31 04:04:54 +00:00

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-cli and 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

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.

Description
No description provided
Readme MIT 820 MiB
Languages
Rust 57.6%
Python 27.7%
Shell 10.6%
GDScript 3.5%
Dockerfile 0.4%
Other 0.1%