thermometerlisted

# thermometer A thermometer turns "slow" into a workload, a metric, and a measured boundary. No optimization starts from intuition alone. The same input, environment, and sampling method must exist before and after the change. ## The measurement law No performance claim without a repeatable baseline and a comparable after measurement. A faster result from a different workload, warm cache, machine, dataset, build mode, or sampling method is not a comparison. Correctness, security, durability, and accessibility remain requirements. Trading one away for speed requires explicit user approval and must appear in the report. ## 1. Pin the question Turn the complaint into one primary metric: - latency for a named operation and percentile - throughput under a stated concurrency level - peak or retained memory for a defined workload - CPU time or utilization for a named process - startup time to a defined ready signal - artifact or bundle size for a named build target Name the workload, environment, dataset size, cache state, build mode, and target. If no target exists, use the baseline to quantify the opportunity and report the measured result without inventing a service-level objective. ## 2. Choose the proving command Prefer the repository's existing benchmark, load test, profiler, tracing setup, or production-like fixture. Otherwise build the smallest repeatable command that exercises the reported path. The command must produce machine-readable or plainly comparable outp