It shows you operate systems, not just design them

“For Tab I'd skip hedging - at sub-100ms and that request volume the duplicate cost isn't worth a p99 win nobody perceives. For an Agent step I'd hedge or retry, because the user is already committed and a failed step costs more than a few hundred milliseconds. I'd put the choice behind a per-surface policy and watch p99 latency, cost per request and step-success rate to confirm it.”

When you make a tradeoff call, always state the metric you'd watch to know if you were wrong. "I'd shed low-priority traffic first and watch shed-rate by QoS class plus error budget burn" beats "I'd add load shedding." Naming the instrument is the senior move - it shows you operate systems, not just design them.