kyzo-bench

The process for onboarding a new comparative subject (opponent database or engine) into one or more kyzo-bench benches. Use whenever a story adds a competitor that doesn't already have a rig, whether into one existing bench or across several. Enforces pin-first, fairness-before-wiring, and treats the output-format correctness bridge as the genuinely hard, per-workload step that no interface generalizes.

The discipline for executing one bench or demo story from the shared KyzoDB board. Use when picking up any story. Enforces working from the board, one coherent end-state target, verify-the-number, hostile methodology review, and the anti-avoidance rules.

The verify-with-run discipline for a benchmarks repo. Use whenever making any claim about what a rig does, what a run produced, what an opponent's configuration is, or what a result file contains. Every such claim must be backed by a real run whose output is quoted, or by reading the actual file.