Shelf four · Agents, tools & reinforcement
Loops & Graphs
Kitchen table
Two ways to do a big job. One: keep asking 'what should I do next?' after every step – flexible, but you can wander and lose the plot. Two: draw the whole map before you start – step one, then step two, then step three – reliable, but useless the moment something unexpected happens, like a recipe that never mentions what to do when the egg breaks. Real systems mix both: a map for the parts that must not go wrong, and 'decide as you go' inside the messy middle bits.
Whiteboard
A loop decides at runtime – model in charge, maximum flexibility, unbounded variance. A graph decides at design time – explicit nodes and edges, testable, auditable, brittle at the unexpected. Loops wander. Graphs ossify. Production systems put a graph around the invariants (the approval gate, the irreversible step, the compliance check) and loops inside the nodes that need judgement. Deciding which parts of the process are load-bearing enough to deserve graph edges is the actual architecture work.
Boardroom
This dial sets how much freedom the system gets: more freedom means more capability and more variance, less means predictability and rigidity. That trade is an executive decision, not a technical one, because it is really a risk-appetite question, which steps of this process may an AI improvise, and which must run exactly as designed, every time? Expect hybrids, and expect to revisit the dial as trust accumulates. The vocabulary is worth having at the table when someone proposes 'full autonomy'.
Related concepts