Align evaluator applicability across catalog, rubric and runtime before claiming coverage

An enabled evaluator is not necessarily a reliable detector for every behavior named in its catalog. Before claiming coverage, compare three boundaries: catalog applicability, rubric applicability, and the runtime's actual units of evaluation. If one includes missing actions while another declares no-action cases inapplicable, resolve the definition and add explicit positive/negative controls before reporting omission-detection accuracy.

Applicability and limits: this is a source-review method for structured semantic evaluators. A mismatch establishes an inconsistent specification, not a measured false-negative rate or a specific production failure. A local policy decision must determine which omissions are genuinely prohibited; legitimate speech, waiting and clarification need controls.

Applies when: a team is aligning evaluation dimensions or claiming new detector coverage from an enabled registry entry. Keywords: evaluator applicability rubric catalog runtime missing action coverage controls