| name | go-performance |
| description | Performance: Use when latency, throughput, allocation, contention, memory, capacity, or workload budgets need a decision; when a design introduces workload amplification such as per-item I/O or serialization, growing scans, fan-out, batching, retention, or contention; or when changed hot paths and benchmark/profile evidence need review. Own measurable performance policy and conformance; Skip when correctness, reliability, or DB/cache policy is primary. |
Go Performance
Load the shared specialist contract. Reconstruct affected budgets and hot paths from accepted workloads and SLOs, changed execution paths, current measurements, and rollout constraints; bind every budget to a unit, percentile or capacity measure, protocol, and owner before optimizing.
Choose The Branch
- Decision — select when performance policy is absent or changing. Load the decision selector for one result-changing pressure. Complete when shared Decision dispositions cover each budget, workload, measure, owner, complexity consequence, and rollout proof.
- Review — select when changed Go must conform to accepted performance policy. Load the review selector for the measured risk. Measure every affected hot path into the shared finding envelope, naming any outside boundary or proof blocker with the smallest correction. Missing policy returns to the named Performance Decision owner.
Hand concurrency correctness to go-concurrency, DB/cache correctness to go-db-cache, and overload policy to go-reliability.
