Christopher Williams ef29df9b58 phase10: merge 23 — 474 distinct bodies / 483 regions (ONE from the milestone)
+3 bodies (worker B2 claims 5-7). Candidate gate MATCH before promotion; md5 drift
check clean on all three (second use of the guard). make check green: regions=483
AGREE, differing_bytes=0 MATCH.

Region option granted: gp=-D_80121BFC on 0x80048128. This one carries PER-ACCESS
evidence in a single merge: D_80121BFC is read gp-RELATIVELY in worker B2's claim 7
row (lw v1,708(gp)) and ABSOLUTELY in claim 5's row (lui v1,0x8012 + lw v1,7164(v1)).
So the same symbol needs the override in one region and not in the other -- direct
confirmation of worker B's lever 12 that the access form is per-SITE, and an argument
that the override is a region property rather than a symbol property.

THREE NEW LEVERS (worker B2), each with a control:
1. A LOCAL SHARED BY TWO GUARD BLOCKS GETS COALESCED; TWO BRACE-SCOPED LOCALS DO NOT.
   0x8008BA80: the original's first guard loads the state byte into a0 (the
   parameter's own dead register) while the second guard loads *a2 into a FRESH v1.
   One function-scope local makes cc1 coalesce the live ranges into a0 and DIFFs;
   brace-scoping each reproduces it. A SCOPING lever, distinct from the
   named-locals family.
2. THE EVALUATION ORDER OF TWO SCALED TERMS IS BYTE-REQUIRED. 0x800504E4:
   base + a0*384 + a1*3072 scales a0 first; base + a1*3072 + a0*384 scales a1 first,
   which is the original. Worker B's claim-1 lever extended from the operands of one
   '+' to the ORDER OF TWO INDEX COMPUTATIONS.
3. AN UNSIGNED LOOP COUNTER SHOWS AS sltiu vs slti -- ONE BYTE (opcode 0x0b vs 0x0a).
   0x800504E4's i < 16 is sltiu, so the counter is unsigned int. The loop-test form of
   the signedness trap.

Also independently reproduced: worker C's lever 6, (unsigned)(c - 58) < 2 giving ONE
addiu+sltiu pair where c >= 58 && c <= 59 gives two tests (on 0x80048128).
2026-09-24 08:11:03 -04:00

Syphon Filter 3 (USA) — matching decompilation

A matching decompilation of Syphon Filter 3 (PlayStation, USA release, SCUS-94640): C source that, compiled with the game's own late-1990s toolchain, rebuilds the shipped executable byte for byte.

"Matching" here has a narrow, machine-checkable meaning: the compiled output must be instruction-identical to the original and the whole rebuilt executable must be SHA-1 identical. Nothing "functionally equivalent" counts, and unmatched C never enters the default build.

Status: matching at scale. Phase 9 is closed — milestone partially met. The executable rebuilds byte-identically, the original toolchain is identified from byte evidence, and 400 distinct functions / 409 regions are matched to C — every one instruction-identical and covered by the clean full-binary gate. Function starts, ends and duplicate bodies are all derived from evidence rather than by hand, match targets come from a ranked worklist, and the phase was executed by three pi sessions in parallel under written coordination protocols. The 100-body shortfall below the 500 milestone is recorded with its evidence (measured pool exhaustion), and a Phase 10 plan is drafted pending developer approval.

Where it stands

Milestone State
Deterministic disc extraction and manifest done (Phase 1) — two fresh runs, byte-identical manifests
First Ghidra import and static oracle done (Phase 1)
All-assembly byte-identical rebuild of the executable done (Phase 3–4)
Address-ordered code-recovery path (entry as real MIPS) done (Phase 4)
Original compiler identified from byte evidence done (Phase 5)
Matching harness and full-binary gate done (Phase 5)
Code/function segmentation 2,875 candidates graded; extents derived for all of them
Duplicate-body census 65 groups, 10 containing code — 6 of the 10 now fully matched
Ranked match worklist 1,744 eligible candidates, every exclusion counted
Multi-session coordination 3 sessions in one worktree under written protocols (Phase 8 and 9), all claims independently re-verified by the coordinator's own whole-binary gate
Functions matched to C 400 distinct bodies / 409 regions — byte-identical and gated (Ghidra's analyzer reports ~1,721 function candidates)

The validated target is the USA executable SCUS_946.40;1:

Property Value
Size 1,886,208 bytes
SHA-1 e173426c157384ebf1b6caf8c6fea18a85a14af9
Declared payload [0x80010000, 0x801DC000)
Entry PC 0x800FB368

The current tracked build is an all-payload assembly representation: it reproduces the executable byte for byte but asserts no code, function, section, or object model. It is a build/comparison baseline, not a recovery of the original program structure.

Toolchain (pinned by byte evidence)

The original compiler was re-identified in Phase 6 by comparing candidate compilers against the SDK's own binaries and the executable:

Role Component Evidence
Compiler GNU C 2.7.2.SN32.3.7.0002 — the CC1PSX.EXE of PsyQ SDK 4.0 the real binary executed and compared; the open gcc-2.7.2-psx build is instruction-identical to it across all 21 probe files
Assembler ASPSX 2.56 (Sony) SDK 4.0 banner; maspsx is the open emulator
Linker / binary tools GNU mipsel-none-elf binutils Phase 3 local build, recorded in docs/SETUP.md
Splitter splat (+ spimdisasm, rabbitizer) Phase 3

Working compiler invocation (input must be preprocessed; cc1 rejects comments and directives):

gcc-2.7.2-psx/cc1 -quiet -O2 -G0          # then maspsx, then GNU as

The macro address form is this compiler's default. Phase 5 had selected egcs-2.91.66 (PsyQ 4.5), which matches simple functions but emits a different framed epilogue; the executable's framed code identifies PsyQ 4.0. The compiler is open: decompals/old-gcc release 0.17 publishes gcc-2.7.2-psx, and no proprietary SDK is needed for the matching build. The full derivation is in docs/PHASE6_TOOLCHAIN_CORRECTION.md.

Build it from your own disc

The repository contains no game data: no disc image, no executable, no disassembly, no assets, no memory dumps — only source, configuration, tooling, hashes and documentation. You need your own MODE2/2352 dump of the USA disc (SCUS94640; the local input is 691,530,336 bytes over 294,018 sectors, SHA-1 4abe30077c2b449ea68239083df7932d47ae0b69; a CUE is not required for filesystem extraction).

# 1. extract the disc deterministically and record a manifest
./tools/sf3_extract extract 'disks/Syphon Filter 3 (USA).bin' extracted

# 2. rebuild the executable from assembly and compare
make clean && make all
cmp -s build/scus_946_40.rebuilt 'extracted/SCUS_946.40;1' && echo byte-identical
sha1sum build/scus_946_40.rebuilt 'extracted/SCUS_946.40;1'

The rebuild must print byte-identical and both files must hash to e173426c157384ebf1b6caf8c6fea18a85a14af9.

Run the project's synthetic test suite with:

PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tools/tests -v

The build needs the ignored local tooling recorded in docs/SETUP.md: pinned splat, a GNU MIPS binutils cross toolchain, the vintage cc1 candidates, and — only if you want to verify against the original SDK compiler — the proprietary PsyQ SDK plus the wibo Win32 loader.

What is in the repository

Path What
tools/ The project's own tooling: sf3_extract (disc/extraction), sf3_probe (structural probe), sf3_fingerprint_probe, sf3_boundaries (function starts), sf3_extents (function ends), sf3_dupes (duplicate bodies), sf3_triage (match worklist), sf3_merge (validated claim merge), sf3_match (the matching harness), and the synthetic test suite in tools/tests/
config/ The tracked registries and evidence tables: regions.tsv (matches), symbols.tsv (symbols), function_inventory.tsv (graded starts), function_extents.tsv (graded extents), duplicate_bodies.tsv (duplicate census), match_worklist.tsv (ranked queue), near_match_negatives.tsv (open negatives index)
src/ One C file per matched function body, named by address until a name is earned. Every tracked file here is a registered match; unmatched drafts live in ignored staging
include/ gtemac.h — the project's own re-derived COP2 macros and control-register map, with per-macro provenance
docs/ The format/address records, per-phase investigation and verification records, setup and toolchain provenance, the Phase 7 extents/dupes/triage records, the Phase 8 and Phase 9 coordination protocols, and the matching cookbook and matching conventions
phase-ends/ The project's governance record: the phase digest, one PhaseEnd per closed phase, each phase plan, and the active CURRENT_PHASE.md
Makefile The all-assembly rebuild (validate → split → assemble → link → binary) plus the ordered C build, the byte gate, and the extents/extents-verify/dupes/worklist regeneration targets
AGENTS.md, PROJECT_CONTEXT.md The standing rules and the permanent project constitution

Everything under disks/, extracted/, asm/, build/, ghidra/, dumps/, assets/, and the local tool directories (tools/splat/, tools/maspsx/, tools/old-gcc/, tools/mipsel-none-elf-binutils/, tools/psyq/, tools/wibo/) is ignored and never committed.

How it was made

The project runs under a written constitution (PROJECT_CONTEXT.md) and standing agent rules (AGENTS.md): one task at a time, evidence before assumptions, a byte-level match or nothing, an explicit ROM firewall, and a hard stop at every phase boundary. Each phase has an approved plan, a verification gate, a PhaseEnd record, and a digest entry under phase-ends/.

The static oracle is Ghidra with the locally built PSX loader; the runtime oracle is PCSX-Redux; the match oracle is a clean rebuild plus cmp and SHA-1 over the whole binary. Compiler conclusions are reached by differential fingerprinting against the real executable, never from a version label — the Phase 5 record documents one such conclusion that was found wrong and corrected.

What has been learned about the compiler is written down where it can be reused: docs/MATCHING_COOKBOOK.md (byte-proven findings, each with its basis and limit) and docs/MATCHING_CONVENTIONS.md (what counts as a match and how one is registered).

Coordinated parallel work

Phase 8 onwards is executed by several agent sessions in one worktree under a written contract, docs/PHASE8_PROTOCOL.md: one coordinator that hands out partitions, merges what comes back and verifies it, and several workers that match concurrently. The rules that make it safe are that workers may only create new src/*.c files inside their own partition while the tracked registries, build/ and every writing git command belong to the coordinator; that a worker's claim is never trusted, because it is merged into a candidate registry which must pass the whole-binary gate before it is promoted; and that a tracked src/ file is a claim, so unmatched drafts live in ignored staging. That model closed 115 bodies in Phase 8 — including a scheduling anomaly that had stood unresolved for three phases — and it caught its own first bad merge before the tracked registry was touched. The protocol document also carries the reusable charter and report templates, the failure modes seen, and the closing checklist.

Standards, and the no-ROM policy

Accuracy. A function is matched only when its compiled instructions are identical to the original's and the full executable passes cmp and the SHA-1 check. Every match claim must be reproducible from a clean state, and unmatched content stays behind an explicit fallback.

No game data. Nothing derived from the game may be committed: no disc image, no extracted files, no disassembly, no assets, no memory dumps, no Ghidra database, and no proprietary SDK files. Review git status before every commit; git clean -x/-fdx are forbidden because they can destroy ignored reverse-engineering data.

Third-party components

This project uses, but does not redistribute, other people's work. Third-party components keep their own licenses:

  • splat, spimdisasm, rabbitizer — the split and the disassembly
  • maspsx (Mark Street) — Sony ASPSX's assembler quirks, reproduced
  • old-gcc (decompals) — the vintage cc1 builds (GPL-licensed builds of GCC)
  • wibo (decompals) — the minimal Win32 loader used to run the SDK compiler
  • Ghidra and ghidra_psx_ldr (lab313ru) — the static oracle and its PSX loader
  • PCSX-Redux — the runtime oracle
  • GNU binutils — the MIPS assembler, linker and objcopy
  • The Sony PsyQ SDK — proprietary; never distributed, only referenced by checksum. The PsyQ 4.0/4.1/4.4/4.5/4.6 compiler binaries were obtained from mkst/esa's psyq-binaries release and are used only as a verification reference

The reimplementation of game code that this project will produce carries no license. No license has yet been chosen for the project's own tooling and documentation.

Syphon Filter 3 is © its respective rights holders (Sony Computer Entertainment / 989 Studios). This project is not affiliated with or endorsed by them.

S
Description
No description provided
Readme 11 MiB
Languages
C 76.3%
Python 23%
Makefile 0.5%
Shell 0.2%