case-study 2026-10-09 gamereconstructioncommunity

TH04: another Evidence → reconstruction loop from the community

TH04 continues the community habit of publishing reconstructions beside REA-assisted inspection notes. rea.run highlights the **loop**, not a play-by-play clone of anyone else’s page.

Source meta

16 GitHub stars (snapshot)

Language: Python

License: MIT

Updated: 2026-10-10

GitHub source ↗

rea.run rating

4/5 — Historical reconstruction loop

Quality. Same healthy Evidence→rebuild pattern as DX-Ball.

Evidence. MIT historical PC-98 reconstruction.

Limits. Not a modern DRM-strip guide.

For. Touhou / historical RE builders.

Reuse the checklist. Inventory systems (input, entities, staging), demand Evidence for each claim, then map those claims onto the reconstruction’s modules.

Diff mindset. When agent prose and repo code disagree, believe the runnable code until new Evidence appears.

Scope discipline. Stick to mechanics you are documenting. Avoid shipping ripped assets or DRM-stripped builds as “teaching material.”

For teams. This loop is a template for internal postmortems on your own games: agent gathers, humans decide what enters the design doc.

Takeaways

Loops beat one-off screenshots.
Runnable reconstructions arbitrate disputes.
Keep assets and DRM out of the teaching pack.