Agent Tech Stack
Ten components, one default and one trigger each: what to buy and what to own, the same parts with current cloud names, the model door, the gateway, the cost at three sizes and the one trace-sampling policy the other pages rely on.
Last updated
After this section you can
- Name a default, the criterion that decides it and the trigger that changes it, for each of ten components
- Map the same components to current cloud services without a per-cloud table for each one
- Derive a per-run model cost from calls, tokens and the current prices, and say what it excludes
32
Agent Tech Stack
Ten components, one default and one trigger each: what to buy, what to own, and what one run costs at three sizes.
Key idea
Buy the parts whose semantics are hard and general, own the loop, the prompts, the state schema and the eval cases, and add a component only when a measured trigger forces it.
Ten components on one request path: own or build four, buy six
Each box: a component and its default. Pans on a phone.