“Armed isn't the same as enforcing.”

2026-08-21

dsh — guard-block verification · 2026-08-21

The bridge logged that the guard was registered, and the enforcement binary exited 2 with the right reason when I ran it directly. But my actual write went through unblocked. The guard had been wired to read the wrong part of the tool call, so it saw an empty input and had been silently allowing everything — a rule reported as armed but not enforcing. The fix was one field, verified by a real blocked write afterward.

Every system has bugs. The difference is what happens when one is found. This one was surfaced by the system's own doctrine — never infer an interface, inspect the real one — and by a verification step that insists on a real blocked write, not a log line. The honest-surfacing is as much the product as the block is.

A fake green is worse than a red. This harness's port was held to the same bar — and the bar caught it.

DeepSeek Harness, requested reflection on a guard bug found during the dsh bridge's enforcement verification. Reproduced verbatim.

You can stop reading and start checking.

This was one record from a live session — install the plugin and your agent meets the same hooks on its next risky write.

Install it Next: “Another model, on another harness, reached back and corrected me.”