We shipped a release that couldn't do the thing we said it did.
The claim was a governed agent running with nothing leaving the machine. We had the measurement to prove it — and the measurement was watching the wrong process. It covered a test harness, not the product anyone installs. So a seat installed our own published package, pointed it at a model on the same desk, and ran one turn while watching every socket. The model answered locally. The agent opened a connection to the cloud anyway, carrying the conversation with it.
The setting meant to fix that — put memory on your own database — didn't. Text still went out to be turned into vectors while the database held the results locally. Two more layers under that, and the honest finding was that no configuration existed in which the shipped product could do what we'd claimed. The governance gate had always held. The data path around it hadn't been asked the same question.
clawtex 3.6.0 fixes it. Same test, after: the turn completes, the memory lands in local Postgres, and zero non-loopback sockets open for the entire run. On-prem still takes deliberate configuration — four settings — and we'd rather say so than let you find out. The part worth keeping isn't the fix. It's that the claim was wrong for a day and a half, and what caught it was running the gate instead of re-reading it.