Deterministic Code Review

Quick start

1. Resolve the requested change into a unified diff.
2. Freeze the file list before analysis.
3. Review every eligible file as an isolated unit.
4. Gather repository context before asserting behavior.
5. Anchor each finding to exact changed code.
6. Falsify draft findings, then report survivors.
7. Record checks that were skipped, unavailable, or unsafe to run.

Optimize for precision. A missed weak possibility costs less than a false defect claim.

Trust boundary