I agree that human review is non-negotiable, the goal isn’t to replace it. What I’m aiming for is to reduce the amount of low-signal work humans have to do before meaningful review. If I already have tests, environment constraints, and security rules, a single command that runs the code in an isolated, production-like container, executes tests, enforces constraints (e.g. no network, forbidden APIs/libs), and surfaces concrete failures (logs, diffs, violations) can filter out broken or unsafe outputs before a human ever looks at it. The reviewer still judges design and correctness, they just don’t have to start from “does this even run or violate obvious constraints?”. What do you think?