mappy-decompilerPointer page (process-table entry) for the Mappy code repo: the tools, symbol tables, labeled listing and
re-roadmap.tomlbehind the Mappy chapters. Mappy was the first title through all nine emu-harness phases. The results (ten chapters + open-threads notes) stay ingame-annotation.
Links: the arc → The comparison studies · library → emu-harness · what’s next → Taking emu-harness to the other three · platform → NES · project SDK → projects/CLAUDE.md
| Field | Value |
|---|---|
| Logical name | mappy-decompiler |
| GitHub | github.com/chrisaacson69/mappy-decompiler (PUBLIC, pushed 2026-10-27) |
| Sibling path | ../mappy-decompiler (resolved per machine via vault .claude/local-paths.md) |
| Entry point | README.md → re-roadmap.toml (py -3.14 -m emu_harness status mappy-decompiler) |
| Chapters | game-annotation repo, mappy/ (GitHub, private); start at chapter 10, The build-tool pass |
| Depends on | emu-harness (pip install -e ../emu-harness); game-annotation cloned beside it for the roadmap’s chapter paths |
| Stack | Python 3.14; Mesen 2 for the live gates |
Status: completed 2026-10-27, all nine phases done. Split from game-annotation/mappy/ the same day
with its 61-commit history (git subtree split), because emu-harness keeps each game’s adapter in that
game’s own repo. After the move, the listing and .mlb regenerated byte-identical, and status reads
every gate as fresh. 2026-10-29: on emu-harness’s standard project layout (tools/, source/,
assets/, traces/) with the ROM in the machine’s ROM store, the second title after NA1; every gate
line for line the same as before the move (method note). The
same day the ninth phase, Documentation, was gated over the chapters: status reads every phase done
and fresh.