# 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.

Category: Performance and cost
Source: https://letsship.ai/use-cases/set-a-performance-budget
Published: 2026-08-25

## Goal

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.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Add a performance budget for {route}

Description: 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

Before you create the issue, measure the current numbers for a route in this repository and replace {route} with it. Propose the budget in the description.
```

## 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.
