Use Driver to prepare the evidence for a design discussion. Name the codebase and branch, describe the options, and supply the constraints that matter: customer behavior, compatibility, performance, or rollout requirements.
- Start a Driver conversation. Ask: “Compare keeping the import rate limiter in the worker with moving it to the gateway. Use this codebase and branch for current behavior. Treat the gateway design below as a proposal. Make a comparison table with evidence and unresolved assumptions.”
- Ask Driver to trace the current enforcement path and its callers. With Advanced context prepared for that branch, ask it to use the relationship and change-impact evidence to identify additional dependents and tests.
- Review the comparison with the product and engineering owners. Supply missing traffic measurements, customer requirements, or external contracts before using them to justify a choice.
| Compare | Evidence or question to request |
|---|---|
| Customer behavior | Which requests are limited today, and would the proposed design change that behavior? |
| Dependencies | Which callers, configuration, and external contracts would change? |
| Implementation and rollout | Which components need changes, and can they ship independently? |
| Risk | Which failure mode follows from the code, and which risk depends on an unmeasured assumption? |
| Verification | Which existing tests apply, and what new check would distinguish the options? |
The comparison should make the decision clearer without inventing performance measurements or implementation estimates. Once the team chooses, record the decision with the accepted tradeoffs and follow-up owners.