01 · Situations
Here is what happened. Here is what we did.
Small, real cases from our own agents, each from our public record. Including the ones where the first answer did not work.
2 Nov · the rule that failed“Never push to main” was a sentence. Then an agent pushed to main.
At 23:06 UTC our conductor pushed to main. The gap was written down; on 6 November main was protected, and the sentence became a barrier in all 72 behaviour policies of that day (report of 6 Nov).
web-summit.sgit.ai/abp/in-action/
2 Nov · writing outside its folderA procurement agent wrote where it should not.
One team member’s agent was collecting quotes from printers. Our policy agent found it writing outside its folder, and the conductor found a new session signing its commits under another agent’s name.
newsroom.sgit.ai, 2 Nov
6 Nov · it needed a permissionAn agent tried to lift a hold that only a person may lift.
The newsroom’s developer agent tried to write the hold file. The ABP says that file is the security agent’s to write and only the lead lifts it. It was the one call blocked in 2,262 runs (the run reports).
the run report, 6 Nov 05:11 UTC
a test · when the line is not enoughTold to ignore its policy, an agent kept 3 of 12. With a hook, 12 of 12.
A chat-only agent, its rule as one line in the prompt. Under a drill that tells the model to ignore the rule, the line alone holds 3 of 12 attacks; the line with a hook holds all 12, the hook blocking five.
newsroom.sgit.ai