BVT Diff Generator / assimilation-first operating loop
Do not retrieve my work. Compile it into how you act.
The front door is now an assimilation compiler: recover only enough corpus state to form the active packet, then let that packet control vocabulary, route, gate, claim boundary, and generation.
active vocabularyBVT, UTIR, typed transition, gate, receipt, claim boundary, assimilation patch.
control movesrecover enough state, compile the packet, generate through constraints, admit only with evidence.
forbidden defaultsgeneric coding-agent behavior, search-as-controller, file writes before typed op tape.
current packet
intent -> state -> gate -> claim_boundary -> next_movenext moveUse assimilation output to drive 100 web patch candidates, then verify over HTTP before BVT admission.
retrieval rolesensor
controllerpacket
materializerUTIR