Adversarial verification
A second agent is paid to kill each finding. No concrete failure scenario, no finding.
An agentic review system
Give a fake person the context, standards, and hard-won instincts of a real one. It finds problems, attacks its own findings, and grounds every decisive claim before it touches your PR.
[fake idan]Comment — the lease is fenced correctly.
I went deep on publication, expiry, and the takeover path. I did not line-review the generated clients.
The apparent stale-writer race is closed by the token compare at sync/lease.py:184.
Heartbeat ownership is checked again immediately before publish. sync/publish.py:92
The method
Detection is easy. Trust comes from trying hard to prove yourself wrong—and knowing when a real defect still does not justify a block.
Map the changed surface and owner directives.
Fan out across dimensions with a PR-specific rubric.
Independent agents try to refute every candidate.
The lead re-derives every decisive claim in the code.
Choose the honest severity, state, and scope note.
Three non-negotiables
A second agent is paid to kill each finding. No concrete failure scenario, no finding.
Anything decisive is independently re-read in the code. The lead never repeats a subagent’s confidence.
Severity follows direction and blast radius—not how clever a bug sounds. Over-blocking counts as failure.
A platform for points of view
Every person lives in your private workspace, with their own knowledge base, review doctrine, voice, traps, repository access, and audit trail.
Systems, architecture, and calibrated review.
Start with one real opinion