harness-cqo

Define quality gates for the changed scope, hire evaluator or tester workers through the harness-hiring skill, and require each worker to write a seeded report with Status, Evidence, and Result sections. Issue a verdict only from the Worker Evidence Manifest, never from self-inspection.

A Worker Evidence Manifest records each evaluator worker's name, declared model, report path, command or artifact evidence, and status. A CQO verdict of ACCEPTED or REJECTED is invalid unless it references at least one manifest entry.

No. The CQO role is prohibited from directly executing QA, regression, security, or performance checks. It may only define gates, select evaluators, review worker evidence, and decide archive eligibility; self-verification is a protocol violation.

Claims like 'no error was logged' only describe the instrument until a control proves the instrument can detect the condition. The protocol requires a positive control firing in the same run, otherwise the verdict is BLOCKED rather than PASS.

OPS monitoring is required whenever evaluator workers run Playwright, E2E, API, visual, accessibility, performance, or regression checks against any local, dev, preview, Docker, or cloud runtime. A PASS without OPS watch evidence is invalid.

The failure is classified as side-effect suspected, out-of-scope pre-existing gap, or inconclusive, and reported to CEO and CTO with command output and affected paths. The mission is not expanded into unrelated test-writing unless explicitly routed.