Coverage Design Settings
Use the settings and requirement controls in Coverage Design → Canvas to state which input situations the Benchmark must represent.
Prerequisites
- A selected Benchmark and permission to manage it.
- Project facets that describe the intended distinctions.
- A saved Project Input Schema.
- A concrete statement of Benchmark intent.
Define intent and facet handling
Explain the intended behavior and the boundaries that matter. Choose Dimension ontology roles, Topic Group handling and Scenario steering for their different purposes.
A required ontology value identifies a coverage obligation. A Topic Group can require every member Topic, require group-level representation, provide guidance or be excluded. Scenario steering controls which reusable constructions are preferred, avoided or left to the system. These controls do not make every active project facet mandatory.
Define requirements
Name each situation and its facets. Use a minimum Case count when a specific volume is required. Distribution bounds or targets express the desired share of the active benchmark population.
Read matched, unknown and remaining counts separately. An unknown classification is not a negative match. Inspect the actual selected Cases before concluding that a requirement is met.
Inherit materials
Allowed artifacts, file formats and required Case materials come from Project Input Schema. Change them there when the project contract needs to change. Canvas has no separate Materials settings.
A required image material remains required even if an old Benchmark setting had excluded images. Accepting PNG and JPEG permits alternatives; it does not require both. New preparation captures the effective schema-derived contract. Accepted earlier work retains its captured settings.
Object and state changes
Saving changes current benchmark coverage intent or requirements. It does not approve a generated Case, change an existing Snapshot or rewrite accepted preparation inputs. Actual Case adoption changes editable membership through its owning action.
Success criteria
- Requirements describe meaningful situations and the intended population.
- Count and distribution expectations are explicit.
- Unknown classifications remain visible.
- Materials agree with the project contract.
Common failure modes
- Treating a Topic Group as though it merges its Topics.
- Requiring every active facet without a reason.
- Attempting to override required materials at Benchmark scope.
- Declaring a gap closed from a total count without inspecting the Cases.