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. The high-agent workflow gate is
scripts/benchmark-high-agent-workflow; it exercises fixed concurrency tiers of 1, 4, 16, and 32 across 2,048 deterministic attempts, verifies the 128-operation workflow-history fence and Continue-As-New behavior, and digest-binds the existing browser event/replay/projection gate. - 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.
The committed high-agent fixture proves bounded control-plane scheduling and history rotation only. It does not claim 2,048 simultaneous paid agents or hosted-provider latency. Numeric million-block, provider-throughput, and hosted-agent capacity remain unclaimed unless their owning measured fixture and environment are 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. The workflow regression also runs a real local Temporal execution with continuously ready children, proves the configured history limit is not crossed, observes Continue-As-New, and replays the first history deterministically.
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.