I saw three processes interaction over Binder:
A small, trusted kernel: a few thousand lines of code that check every step of every proof mechanically. Everything else (the AI, the automation, the human guidance) is outside the trust boundary. Independent reimplementations of that kernel, in different languages (Lean, Rust), serve as cross-checks. You do not need to trust a complex AI or solver; you verify the proof independently with a kernel small enough to audit completely. The verification layer must be separate from the AI that generates the code. In a world where AI writes critical software, the verifier is the last line of defense. If the same vendor provides both the AI and the verification, there is a conflict of interest. Independent verification is not a philosophical preference. It is a security architecture requirement. The platform must be open source and controlled by no single vendor.
，详情可参考下载安装 谷歌浏览器 开启极速安全的 上网之旅。
В МОК высказались об отстранении израильских и американских спортсменов20:59
Have multiple agents review the output. Multiple specialized reviewers examine the code in parallel.
ОАЭ задумались об атаке на Иран20:55