What a shape is, and what it is not
Agent architecture is the practice of deciding who asks whom, in what order, and what has to be true before that arrangement is worth building.
The definition
A shape is the arrangement of the parts: who asks the model, how many times, in what order, and who decides what happens next. That is the whole of it.
Six shapes appear in this volume. They run the same job, on the same input, against the same checks, using the same model with the same instructions. The only thing that differs between them is the arrangement — and that difference is worth up to a factor of four in cost and the difference between a right and a wrong answer.
Four things it is not
| why it is not the shape | |
|---|---|
| the model | hold it fixed and the six shapes still cost different amounts. Every figure in this volume is measured with one scripted model precisely so the arrangement is the only variable |
| the prompt | the wording is the same in every shape here. What differs is how many times it is sent and what is in scope each time |
| the tools | all six shapes read the same files and look rates up in the same table. Reading a file is free; asking about it is not |
| the framework | a framework is an implementation of a shape, usually of one shape. Choosing a framework before choosing a shape is choosing the answer before the question |
That last row is the reason this volume exists. Most writing on the subject names a shape and recommends it. Six articles will name six different shapes with equal confidence, and all six can be right about some workload — which is a fact about workloads, not about shapes.