Set a performance budget for one route and make the pipeline enforce it
A budget the pipeline enforces, so the next regression fails a check instead of arriving in a support ticket.
The ticket
Set a performance budget for one route and enforce it in the pipeline.
Acceptance criteria
- The budget is a stated number with a rationale
- A deliberately seeded regression fails the check
- The measurement is stable enough not to fail at random
- Raising the budget is a reviewable change, not a silent one
What lands as proof
A seeded regression failing the check, plus repeated measurements showing it does not flap.
Why teams defer it
- Choosing the number needs somebody to commit to it publicly, and nobody wants to own a threshold that will page them.
- A flaky performance check gets disabled within two weeks, so the measurement has to be stable first.
- It edits pipeline files, which stops the run for a human to approve.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: set a performance budget for one route and enforce it in the pipeline. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means budget fails on a deliberately seeded regression, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.