Case Foundry
Case Foundry coordinates Case preparation for the situations defined in Coverage Design. Read preparation progress separately from reviewed Case quality and benchmark membership.
Prerequisites
- Coverage intent and requirements that identify the missing situation.
- Relevant Story or tuple planning context.
- Project Input Schema and the materials needed by that contract.
- Permission to prepare and review Cases.
Prepare candidates
Start from Canvas and the intended coverage slice. Confirm whether the work should reuse source material, synthesize a situation or refine existing candidates through the available preparation controls.
Preparation captures the relevant planning and input settings. Its queued, running, partial, completed, failed or cancelled state describes that accepted operation. A completed operation is not a statement that every current requirement is now satisfied.
Project Input Schema owns allowed artifact families, formats and required material keys. An unavailable required family produces an actionable preparation error. Do not replace required material with text or change the project contract merely to make generation appear complete.
Review the result
Open Case Review to inspect input content, generated materials, provenance and the situation demonstrated by each candidate. Read added, synthesized or retrieved counts as preparation activity. Confirm actual selected membership in Canvas or Benchmark Datasets.
If requirements or source material changed after preparation started, inspect the captured inputs before requesting another operation. Historical completion does not establish freshness against today's settings.
Object and state changes
Preparation creates an attributable operation and reviewable candidate material. Review and explicit membership operations determine which Cases enter the editable benchmark. Existing Snapshots remain unchanged.
Success criteria
- Candidate preparation is tied to a named input need.
- The captured contract and actual required materials agree.
- Partial or failed work remains distinguishable from successful output.
- Reviewed membership, rather than generation volume, explains progress.
Common failure modes
- Generating around an unresolved correctness question.
- Treating operation completion as Case approval.
- Using obsolete Benchmark material preferences instead of Project Input Schema.
- Assuming an old preparation handled newly edited requirements.