Coverage Stories
Stories explain the situation behind a coverage requirement. They connect Benchmark intent to testable facet combinations and the Cases prepared to exercise them.
Prerequisites
- An identified Benchmark intent and current coverage requirements.
- Dimensions, Topics or Scenarios that describe the relevant distinctions.
- A Case input contract that can represent the situation.
Make a Story concrete
Describe the actor, request, source condition, conflict or constraint that changes expected behavior. A Story should help an operator explain why a slice matters without treating a chart category as a complete situation.
Tuples name smaller obligations. Their statement of what must be demonstrated, facet references and intended count guide preparation and review. A tuple's requested count does not prove that its Cases are realistic or distinct.
Read Stories with Canvas
Use Canvas to inspect current requirements and selected Cases. Stories supply planning context; requirement assessments supply current matched, unknown and remaining counts. Do not substitute a Story budget for actual dataset membership.
Where a Story is created or edited through the available controls, preserve its rationale and relationship to the relevant facets. An archived Story is history rather than a new instruction to remove every related Case.
Materials
Project Input Schema supplies allowed artifacts and required material keys. Story planning can request an appropriate allowed artifact. It cannot disable required input, add an unaccepted family or create another materials policy.
Object and state changes
Story edits change current planning context. Prepared work records the Story and input contract it accepted. Existing Snapshots and completed Runs retain their original Cases and criteria.
Success criteria
- A reviewer can tell what situation each tuple must demonstrate.
- Facet references identify the intended project concepts.
- Counts are interpreted alongside actual Case quality and membership.
- Current requirements and captured preparation inputs are distinguished.
Common failure modes
- Using a generic title as the entire requirement.
- Counting near-duplicate Cases as distinct coverage.
- Reconstructing an accepted preparation from today's edited Story.
- Treating Story generation as automatic Case adoption.