Teammately Docs
Docs menu

reference

Metadata and context

Use record context and metadata fields to make Teammately cases easier to filter, review, and analyze.

Metadata and context

Definition

Metadata and context are the supporting fields that make records and cases understandable after they move through import, review, coverage, and benchmark workflows. Context explains the situation; metadata helps filter, segment, trace, and compare it.

Use this page when a case is technically present but not useful because reviewers cannot see why it belongs in a behavior slice or what source information should be considered.

Fields, states, or lifecycle rules

  • Context should preserve the information a reviewer needs to judge the case.
  • Metadata should support filtering, coverage planning, benchmark segmentation, and run interpretation.
  • Metadata is not a substitute for output identity or source context.
  • Dropped or inconsistent metadata can make coverage look balanced while hiding a missing behavior segment.
  • This page does not define a public metadata schema or export format.

Metadata and context should be read with Cases, Importing cases, Case versions, and Coverage Engineering.

Worked example

Metadata and context boundary

01

Start

Behavior input

Raw record
A support transcript includes a customer request, account tier, candidate answer, and later human correction.
02

Middle

Judgment into standard

Context
The account tier and correction explain why the answer was unsafe.
Metadata
The case can be segmented as exception request, enterprise tier, and human-corrected source.
03

Result

Interpretation

Interpretation
If that context or metadata is dropped, review and coverage work can still run but the evidence becomes harder to trust.

Source confidence

Code-backed: Cases and record presentation expose contextual fields to reviewers, while Case Pool column mapping and upload-queue types show how imported columns become usable record context. Field availability depends on Project configuration; this is not a universal metadata schema.

Related task pages

Reference / AssetsCasesUnderstand canonical project cases, their input and materials, and how they become members of benchmark datasets.Task / Operating ManualImport and prepare casesBring cases into the project, conform them to Project Input Schema, inspect materials, and prepare benchmark selection.Task / Benchmark EvaluationsConnect Model OutputsMap externally produced outputs to immutable Benchmark Cases and create an output-only reference Run.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

Assets Cases Understand canonical project cases, their input and materials, and how they become members of benchmark datasets. Operating Manual Import and prepare cases Bring cases into the project, conform them to Project Input Schema, inspect materials, and prepare benchmark selection. Expert Contributions Contributed Artifacts Inspect policies, rubrics, cases, and coverage observations produced through attributable expert contribution work.
AI context