Binary reverse engineering with Jev: clone, map, rebuild
A Jev-driven Opus 5.5 reverse engineering rig clones a target, maps 18,039 call edges, traces frames in parallel and rebuilds modules at mean distance 0.020.
WHOEVER LEAKED THIS JEV REVERSE ENGINEERING RIG DESERVES THE DEF CON SLOT I thought reverse engineering a binary meant Ghidra, three monitors, and a bottle of something strong by hour four. Apparently not. This rig's setup is much more interesting: → CLONE pulls the full target into one bounded workspace (2,048 files, 18,039 call edges), no reach outside the clone, no "fetch what's missing on the fly" → MAP builds the call graph across 96 modules, every function tagged with one entry and one owner, no shared globals surviving the pass → TRACE runs through 1,133 of 2,048 frames in parallel, each trace committed to the module ledger before any decompile fires → DECOMPILE converts each sub to rebuilt, stub or merged based on the trace (24 traced in module 14, 11 rebuilt), nothing marked done without a reason → REBUILD closes the loop with mean distance 0.020 from the original, 50 subs stayed in place, 17 moved once, flags 7 subs the author expected would merge but didn't so you get: Targets cloned. Calls mapped. Traces committed. Modules rebuilt. the interesting part isn't decompiling faster. it's giving every sub one owner the next pass can't argue with. Instead of three days in a disassembler guessing which function owns what, you clone the target, map 18,039 calls, and let Opus 5.5 rebuild 1,568 modules at mean distance 0.020 from the original. Clone the target. Map the calls. Rebuild the module.
This post quotes another post: “Long read: how to build a Jev-powered agent stack”