Plan capacity
Use measured budgets and explicit admission limits instead of architectural scale claims.
Outcome
The environment admits work only inside measured browser, database, workflow, provider, and spend budgets.
Prerequisites
Record the exact build, machine, browser, region, database, object store, compute class, and network profile. Use deterministic fixtures before any paid concurrency run.
Steps
- Start with per-run concurrency, worker concurrency, provider rate limits, and transactional budget reservation.
- Run the committed fixture for the surface being activated.
- Record raw samples, percentile method, warm-up, and summarized result.
- Optimize only the measured bottleneck.
- Publish the supported limit with its fixture definition and environment.
No numeric million-block, task, or agent capacity is currently claimed. Proposed budgets become release claims only after their owning fixtures run and evidence is saved.
Verify
The result names the exact scope it proves. A UI virtualization check does not prove database paging; a deterministic simulator does not prove paid provider concurrency.
Recover
If a budget fails, reduce admitted work or fix the measured path. Preserve the failing benchmark; do not weaken or delete the threshold without a reviewed decision and before/after evidence.