The governance-first platform had four human gates that did not bind
Inside the vendor whose product is human-in-the-loop control: 0.21.0 guaranteed a delegation tree could never outspend its root budget, and 0.27.1 fixed a path where declining a child let the parent retry that child against a fresh quota share, fifteen days later. 0.26.1 made the developer interface show rejected tool approvals as denied instead of successful. 0.25.0 states that a stale approval never authorizes an earlier call, which means it previously could. 0.24.2 fixed approvals that left the tool unrun.
What this changes for operators
- Platform-hosted governance is not a substitute for testing the gate. If you chose a managed runtime specifically for its approval and budget controls, verify each one behaves as documented on the version you run, including what a denial actually does.
Featured in
- Assume the Rule Does Not Bind / 2026-07-27
Run: 2026-07-27-weekly-digest-2026-07-02_2026-07-27-frontier-v0
Schema: bitter.frontier_signals.v0 / ID: 2026-07-27-eve-governance-gates-failed-open-and-closed
Research evidence and publication history are open in the repository.