Where does the code go next?
Function pointers, jump tables, and relocated overlays hide control flow. A ROM only counts as closed when every indirect site is resolved, and each solver scope names the assumptions it rests on.
The Cartridge Forge / Research ongoing · SM64 runs natively
A research tool that analyzes an untouched Nintendo 64 ROM into a closed program, lowers it to C, and links it into a native x86-64 or ARM64 build with no emulator inside.
* 99.03% of Super Mario 64 functions discovered automatically.
PROOF SIGNAL
99.03%of Super Mario 64 functions discovered automaticallyThe mission
A research tool that analyzes an untouched Nintendo 64 ROM into a closed program, lowers it to C, and links it into a native x86-64 or ARM64 build with no emulator inside.
Engineering log
What the system handles, and why it works this way.
Function pointers, jump tables, and relocated overlays hide control flow. A ROM only counts as closed when every indirect site is resolved, and each solver scope names the assumptions it rests on.
Lowered instructions are checked against a pinned reference interpreter, so the native build is measured against ares instead of trusted because it boots.
System map
A plain technical view. The map still works without hovering.
Untouched cartridge image
Finds code, loads, and overlays
Accounts for every jump
CPU and RSP code to portable C
Native graphics, audio, and input
LOG ENTRY / WHAT I LEARNED
“A result with its assumptions written down is worth more than a bigger number without them.”
Source signal