Teammately Docs
Docs menu

reference

Candidate and In-Use Cases

Distinguish examples under consideration from cases that actively support benchmark evidence.

Candidate and In-Use Cases

Definition

Candidate Cases are Cases or prepared Case proposals still being considered for reuse or benchmark membership. In-use Cases are already selected by one or more Benchmarks. The distinction describes current use, not intrinsic quality: a Candidate can be excellent but not yet selected, while an in-use Case can later require correction or removal from the editable dataset.

Fields, states, or lifecycle rules

  • Case Pool rows can retain source type, source label, coverage targets, review notes, and the Benchmarks that currently include the Case.
  • Adding a Case to a Benchmark changes editable membership. It does not retroactively add the Case to an existing Snapshot or Benchmark Version.
  • Removing a Case from a Benchmark does not delete the reusable project Case.
  • A Case can be in use by several Benchmarks at once; membership must be interpreted per Benchmark.
  • Generated or contributed Cases still require review for schema conformance, materials, realism, and intended coverage before selection.
  • Historical Runs continue to reference the Case versions frozen into their Benchmark Version.

Use Case Pool to inspect reusable Cases and sourcing work. Use Benchmark Dataset Cases to inspect or change membership for one Benchmark. Use Dataset Snapshots when that membership must become immutable evaluation evidence.

Worked example

Promotion without rewriting history

Case Foundry prepares a Case for a missing high-impact exception tuple. It remains a Candidate while reviewers inspect its input and materials. After approval, the operator adds it to the current dataset for the support Benchmark, so it becomes in use there. Earlier Snapshots remain unchanged; the Case enters evaluation evidence only after the team creates a new Snapshot and Benchmark Version.

Source confidence

Code-backed: Case Pool navigation, benchmark Dataset Case actions, and Case sourcing types expose candidate counts, in-use counts, source context, coverage targets, and benchmark inclusion. Snapshot pages define the separate immutable evidence boundary.

Related task pages

Concept / Coverage EngineeringCase PoolUse the Case Pool to collect, triage, enrich, and promote candidate cases.Reference / Object ModelCase Pool surfaceUnderstand Case Pool as the Assets view for reusable project Cases, candidates, and explicit Benchmark selection.Task / Operating ManualImport and prepare casesBring cases into the project, conform them to Project Input Schema, inspect materials, and prepare benchmark selection.Quickstart / Learning ManualProduct quickstartConfigure one project foundation, one benchmark slice, one expert contribution, one evaluation, and one evidence-backed improvement.Concept / Operating ManualTask indexRoute correctness work to the current project foundation, benchmark workspace, evaluation, or improvement surface.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs

Coverage Engineering Case Pool Use the Case Pool to collect, triage, enrich, and promote candidate cases. Object Model Case Pool surface Understand Case Pool as the Assets view for reusable project Cases, candidates, and explicit Benchmark selection. Operating Manual Import and prepare cases Bring cases into the project, conform them to Project Input Schema, inspect materials, and prepare benchmark selection.
AI context