Case Pool surface
Definition
Case Pool is a tab under Assets → Cases, not a separate Case object type. It shows reusable project Cases and candidate material that can be inspected before explicit selection into a Benchmark Dataset.
Use this reference when deciding whether a Case should stay in the project collection, be prepared further, or be selected for a Benchmark. Sourcing Tasks is the adjacent job and audit surface; it is not another Case state.
Fields, states, or lifecycle rules
- Case Pool can contain useful Cases that are not selected into any Benchmark.
- Candidate and in-use labels describe curation and membership context; they do not create a different persisted Case type.
- Coverage dimensions and ontology values help explain what behavior the pool represents.
- Adding a Case to a current Benchmark Dataset changes mutable membership. A new Dataset Snapshot is required to freeze that change as an evidence boundary.
- This page does not define public upload schemas, export contracts, or retention behavior.
Related objects
Read Case Pool with Cases, Candidate and In-Use Cases, Coverage Dimensions, and Benchmark Dataset Cases. Use Case Pool for operating instructions.
Worked example
Case pool boundary
Start
Behavior input
- Raw case
- A new support transcript shows a refund exception question that reviewers have not seen before.
- Case pool state
- The example is a candidate case because it may close an exception-handling coverage gap.
Result
Interpretation
- Interpretation
- It should not affect benchmark scores until source context, output identity, coverage labels, and benchmark membership are clear.
Source confidence
Code-backed: the Assets Cases routes expose Case Pool and Sourcing Tasks tabs, candidate and in-use views, and an explicit add-to-Benchmark action. Case Pool is therefore a curation surface, not automatic Benchmark membership, a separate Case schema, or a public storage contract.