Teammately Docs
Docs menu

reference

Ontology

Use ontology values to classify cases consistently within each coverage dimension.

Ontology

Definition

Ontology values are the controlled labels used inside a coverage dimension. They keep case classification consistent enough for teams to plan coverage, compare benchmark segments, and explain gaps.

Use this reference when free-form tags are making coverage hard to read or when a benchmark segment needs stable vocabulary before results are trusted. Ontology values remain project-scoped foundations.

Fields, states, or lifecycle rules

  • Ontology values belong to dimensions; they should not drift into unrelated free-form tags.
  • Values should be specific enough to separate meaningful behavior, but not so narrow that coverage becomes fragmented.
  • Changing ontology values can change segment-level benchmark interpretation.
  • Ontology should support coverage decisions, not replace expert judgment or policies.
  • This page does not define a public taxonomy API.

Ontology should be read with Coverage dimensions, Dimensions and ontology, and Generate a dimension schema.

Worked example

Ontology boundary

01

Start

Behavior input

Dimension
Source support level.
02

Middle

Judgment into standard

Ontology values
Explicit support, implied support, conflicting source, no source.
03

Result

Interpretation

Interpretation
Segment results are easier to trust because the team knows which support condition each case represents.

Source confidence

Code-backed: Dimension types and the Dimension settings, ontology-row, and proposal components establish ontology members as labels owned by a Dimension and used for classification. Vocabulary quality and cross-reviewer consistency require project review.

Related task pages

Reference / Coverage EngineeringDimensions and OntologyDefine reusable behavior axes and their allowed values, then inspect how cases and benchmarks cover them.Reference / Object ModelCoverage dimensionsOrganize cases by the behavior axes that matter to product correctness.Task / Coverage EngineeringGenerate a dimension schemaAsk Teammately for coverage-dimension proposals, then accept only the dimensions and ontology values that describe meaningful behavior.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 Dimensions and Ontology Define reusable behavior axes and their allowed values, then inspect how cases and benchmarks cover them. Object Model Coverage dimensions Organize cases by the behavior axes that matter to product correctness. Coverage Engineering Generate a dimension schema Ask Teammately for coverage-dimension proposals, then accept only the dimensions and ontology values that describe meaningful behavior.
AI context