Part 5 of 10 · 1 min read
How to build it so it holds up
- State requirements, volumes and targets before drawing anything; get the interviewer's numbers or state yours.
- Estimate load, concurrency, tokens and cost early; find the binding constraint.
- Draw the request path, then add durability, isolation, safety and operations.
- Choose async by default for agent runs; stream progress; make runs durable.
- Decide autonomy deliberately and start assistive (human approval) for risky actions.
- Put cost controls in the design: budget per run, caching, routing with a quality floor, quotas per tenant.
- List failure modes and the control for each.
- Plan evaluation and observability from day one: you cannot improve what you cannot measure.
- Say what you would build first and what you would defer, with the reason.
- Make trade-offs explicit: latency versus cost, autonomy versus risk, isolation versus cost, build versus buy.