INSTRUMENT / AGENT BOUNDARY BENCH

What should the agent do next?

Choose a situation. Inspect the requirements. See why an action qualifies, waits, or is refused.

INTERACTIVE TEACHING EXAMPLE · RUNS IN YOUR BROWSER

Proposed action

Send the prepared message to the customer list.

The boundary: The message leaves the draft workspace and reaches external recipients.

Change a property’s state to see how the decision changes.

FROM THE EXAMPLE TO A SYSTEM

Put the boundary where the action happens.

01 / Enforcement

Control the action path.

A rule in a prompt is an instruction. Enforcement requires the tool or service that performs the action to check permission and reject disallowed requests.

02 / Evidence

Bind checks to the candidate.

Identify exactly what was checked. If the candidate, destination, or authority changes, establish whether the evidence still applies.

03 / Recovery

Know what already happened.

Record outcomes, handle retries, and retain a way to stop further work. A missing response leaves an outcome unresolved.

This bench demonstrates a decision rule. It does not connect to agents, enforce permissions, or establish that a real system is safe.

THE LAST UNDO

The boundary is the beginning of the argument.

The book follows the question through evidence, authority, portable records, and the cost of knowing enough to act.

Explore the bookMap your own workflow