THIS IS A PURE F*CKING GOLDMINE

the best REA trick almost nobody runs yet.

The idea: REA takes the app apart, Jev keeps only what's proven, and a fresh Opus 5.5 rebuilds the feature from that alone.

Nothing gets copied and no guess makes it into the code, because the builder , only the spec Jev signed off on.

You just connect REA like this:

npx rea-agents setup

here's the split:

→ REA reads the feature down to the binary and writes every rule into SPEC.md
→ Jev checks each rule against REA's evidence and sends back anything unproven
→ a fresh Opus 5.5 session gets only SPEC.md and rebuilds the feature
→ Haiku 5.5 runs the tests against 3 intentionally broken versions

Opus only shows up at three moments:

→ rebuilding from the approved spec
→ the checks Jev marks as unclear
→ signing off before anything ships

REA reads. Jev judges. Opus rebuilds.

That's the clean-room rule in one line: the model that saw the original never writes the code, and the model that writes the code never sees the original.

the full tree
> REA reads the app and writes SPEC.md with evidence for every rule
> Jev approves or returns each rule
> Opus 5.5 rebuilds from the approved SPEC.md in a fresh session
> Haiku 5.5 runs the tests and the 3 broken versions
> Jev routes unclear checks back to Opus
> /goal keeps going until all 3 broken versions fail

paste the tree and this prompt into Claude Code ↓

"Set up a clean-room rebuild around this tree:
1. Use REA to investigate [FEATURE] in [APP]. Write every behavior and rule into SPEC.md, each with the evidence REA found.
2. Send each rule to Jev. Any rule without evidence goes back to REA.
3. Start a fresh session with only SPEC.md. Rebuild the feature on Opus 5.5 without opening the original.
4. Write tests on Haiku 5.5 plus 3 intentionally broken versions. Use /goal until the rebuild passes and all 3 broken versions fail.
Show me SPEC.md first. Nothing gets built until I say go."

↳ github.com/morluto/rea

save it, it'll come in handy.