Studio experiment E10 · for the editor's review

Only a boundary is a control

What stands between the agent and each thing it can do is one of four kinds: none, expectation, setting, boundary. Drawn as four walls the agent's path meets: it passes the first, jumps the second, breaks the third, and stops at the fourth. Then Claude Code on your own machine: turn its confirmations off and one barrier moves, and not one number does.

Not part of the talk: an experiment for the review. Which kinds count as a control ("not a control", "a control: holds") is abp.sgit.ai's own reading, as the data file's note on the barrier kinds says; the four kinds and their meanings are the upstream pack's. Every word, count and label is read at load from the studio's data: the barrier kinds, the enforcer test and the two Claude Code examples from abp-examples.json, the plain label of the row that moves from capabilities.json. Which barrier moves is computed by comparing the two examples' rows. Published drafts from one author's network, derived (0 of 22 rows measured); no score and no rating. Made by ruv.sgit@the-ultimate-insider in run r15-e10-four-barriers at deck@'s request, the editor's word. Frame by frame, the sources and what was left out: the explainer.

v1: four walls, one that holds

Open it on its own · the end state · light · the data: abp-examples.json, capabilities.json