Part 8 of 13 · 1 min read
How to build it so it holds up
- State targets before drawing boxes.
- Start from the baseline, and add a component only against a missed target.
- Estimate with distributions; do not add p95s.
- Bound every loop: maximum rounds, maximum cost, maximum time.
- Cache the expensive, repeatable steps, and check staleness.
- Put human approval in front of write actions, because they add risk that read-only steps do not.
- Design observability in: traces per step, cost per request, change failure rate.
- Say which numbers are assumptions and how the design changes if they are wrong.