Skip to content

Guides

Why does this limit exist?

Ask Driver where a limit is enforced and what evidence explains its origin. Name the codebase and select the branch you want to examine. Advanced context with prepared history is needed for the code-history step below.

  1. Ask: “Where is the 50,000-row export limit enforced on this branch? Cite the check, settings that override it, and tests for the boundary.”
  2. With Advanced history ready, ask Driver to inspect the prepared history for changes to the enforcing file. Follow the cited change and any accessible Jira issue explaining it. You can also supply the relevant historical diff or decision record directly.
  3. Distinguish the reason supported by evidence from a plausible rationale that nobody recorded.
  4. Ask Driver to trace the callers and tests that depend on the limit, then identify what would need checking before raising it. Supply known operational constraints, such as memory or downstream request limits, when they are not recorded in the available sources.
  5. Copy the supported explanation and open questions into the engineering issue or documentation where your team records decisions.

The result should separate enforced behavior, recorded rationale, and unanswered questions. If the original reason is absent, take that question to the code owner. With Basic context, you can still locate the limit and its tests and compare any history you supply.