Goals

Goals are the fitness criteria every version is scored against — they define what "better" means for your run. Each goal has a direction (Maximise or Minimise) and a weight; the weights sum to 1.00 and determine how much each metric counts toward a version's overall score.

Metric types

• Worker metrics are measured on your runner — the built-in runtime, CPU, and memory, plus any custom benchmark metrics your benchmark records (e.g. XXH32_MBps, XXH64_MBps). See Benchmarks for how these are produced.
• LLM metrics are judged by the review panel — qualitative criteria the reviewer models score, such as seed_option_malformed_input_robustness, hash_output_compatibility, cli_regression_coverage_depth, and fix_scope_and_maintainability.

Direction and weights

• Maximise / Minimise sets which way is "better" for each metric.
• The weight column sets each metric's importance. In this run the primary goal — robust handling of a malformed --seed operand — is weighted 0.60, so it dominates scoring, while the performance metrics are kept small as non-regression guardrails.
• Weights must total 1.00 — use Normalise to rescale them, then Save & recompute to re-score every version against the updated goals.

You can pin goals and tune weights at any point during a run; recomputing re-ranks the versions — and the ★ BEST pick — accordingly.