OpenClaw: Platform Harness & Trust Architecture
The breadth play — 40+ channels and the trust gap that birthed two governance forks
Breadth compounds the trust problem. Every channel added raises Module 2 (tool breadth) and simultaneously raises the injection surface that depresses Module 6. Breadth without a trust architecture means each new channel is a new untrusted input source with no isolation. The 35/60 is the structural cost of this tradeoff.
The trust gap is the defining vulnerability. Channel messages enter the model's context with the same trust status as operator instructions. No tags, no boundary. The attacker does not need to compromise the operator — only to send a message in a monitored channel. Cross-channel injection (ASI01). 40+ channels = 40+ injection surfaces.
Two governance forks are the evidence. NemoClaw (NVIDIA) and Scout (Microsoft) are independent forks addressing the same deficiency. Two large vendors independently concluding the trust gap is unfixable in-place is the strongest possible signal that the architecture, not the implementation, is the problem.