Part 8 of 10 · 1 min read
Quick notes
- A design answer is a structured conversation, not a diagram dump: requirements, estimates, architecture, deep dives, failure modes, trade-offs.
- Estimate first; it tells you where the problem is. For agents, servers are rarely it — model tokens and rate limits usually are.
- The architecture is the level in one picture: gateway, fair queue, durable workers, model gateway, event store, scoped data, guarded tools, release pipeline, observability.
- Isolation and approvals matter most for a support platform; durability and quality matter most for a research agent. Build one narrow slice first.
- Always name the failure modes (outage, worker kill, noisy tenant, runaway loop, bad release, leak) and the control for each.