perflisted

# Performance Quality Assess how a system behaves under declared resources and load. Operate the project's performance capability and explain the capacity, latency, resource use, and limitations supported by its facts. Read [Quality concepts](../../CONCEPTS.md) before discovery or interpretation. It defines ownership, subject identity, execution facts, evaluation, comparison, and result states shared by the skills. The project owns its Cases, protocol Runners, Judges, resource/load profiles, Probes, SLOs, safety limits, and baselines. A perf Runner invokes a service protocol; Workload identifies a Service's platform carrier. Record where the load generator executes separately from both. ## Discover and select Read the project's AGENTS.md and README, then locate: - the canonical performance, capacity, stress, soak, or regression commands and operating notes; - the target Service, Environment, deployed revision, Workloads, load-generator location, and application connection path; - Cases or stimuli, case mix, protocol Runner, raw completion signals, and independent Judge; - named experiments and resource/load profiles, both request rate and maximum inflight limits, phase schedules, duration, arrival distribution, and request/time budgets; - Probes, SLOs, breakers, stop/cancellation behavior, cooldown, cleanup, and target authorization; - native run schema, raw requests and resource observations, evaluation records, reports, and comparison baselines. Classify the re