Teammately Docs
Docs menu

reference

Project Topics

Maintain source-grounded subject areas, editable groups, and Atlas relationships used to organize project and benchmark coverage.

Project Topics

Definition

Project Topics are reusable subject areas derived from project knowledge, entered by an administrator, or contributed by an expert. They organize cases by what they are about. Unlike a Dimension, a Project Topic is not one value on a fixed behavior axis: a case can belong to several Topics.

The Project Topics workspace contains Topics, Groups, and Atlas.

Fields, states, or lifecycle rules

Topics

Each Topic has a name, description, active state, author type, case usage, benchmark usage, and source mentions where available. Source mentions retain evidence such as the originating Reference Material, Project Agent Brief, manual entry, or expert suggestion.

The Topic detail shows its definition and source grounding, linked and example cases, coverage confidence, nearby-topic signals, coverage by Dimensions and ontology values, and editable membership in Topic Groups.

An AI-created or source-extracted Topic remains an editable project artifact. Review its definition and grounding before using it to steer a benchmark.

Groups

A Project Topic Group is an editable bundle of Topics. It does not merge or replace its members. Groups let benchmark setup express intent at a useful scale while retaining Topic-level traceability.

In Get Started, a Group can be handled as:

  • Cover every topic: the benchmark should represent each member Topic.
  • Cover the group: the group should be represented without requiring every member.
  • Use as guidance: it can guide story construction without becoming a coverage obligation.
  • Do not use: exclude the Group from this benchmark's setup.
  • Unset: no explicit instruction.

Groups can start from manual work, AI suggestions, source material, or Atlas exploration. Manual edits remain significant; regenerating a suggestion should not be treated as authority to overwrite the reviewed group.

Atlas

Atlas visualizes Topics, relationships, and Groups. Use it to inspect neighborhoods, redundancy, missing nearby Topics, and possible groupings. Relationships are analytical evidence, not a taxonomy merge. A close position or strong relation score does not mean two Topics are interchangeable.

The Topic coverage view can distinguish direct case grounding from breadth, Dimension spread, and binding confidence. When a Topic looks thin, inspect the linked cases before generating more. The problem may be missing cases, weak classification, an overly broad definition, or a duplicate Topic.

Refresh and review

Project Topics can be refreshed from current project context and indexed sources. Refreshing can create or update Topics, source mentions, evidence, and relationship analysis. Review the resulting changes and recommendation runs before incorporating them into Groups or benchmark setup.

Worked example

Example: group without flattening

The project has Topics for Contract renewal, Price adjustment, and Termination notice. An administrator groups them as Agreement lifecycle. One benchmark chooses Cover every topic because each action has distinct risk. Another chooses Use as guidance because it only needs broad agreement-related examples. The individual Topics remain traceable in both benchmarks.

Related task pages

Reference / Coverage EngineeringDimensions and OntologyDefine reusable behavior axes and their allowed values, then inspect how cases and benchmarks cover them.Reference / Coverage EngineeringCase Construction PatternsDefine reusable mechanisms for constructing cases and steer how benchmarks use or avoid them.Task / Coverage ManagementSet Up Benchmark CoverageDefine benchmark intent, facet handling, artifact preferences, and evidence requirements before generating coverage work.Task / Benchmark DatasetsDataset RepresentationAnalyze how distinct benchmark Cases are distributed across facets, evaluator rules, and provenance.

Source confidence

Code-backed: the current Topic, Group, source-mention, statistics, relationship, Atlas, suggestion, and benchmark-handling contracts establish this model.

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 Coverage Engineering Design the behavior space a benchmark must represent and connect reusable project facets to benchmark coverage work. Coverage Engineering Dimensions and Ontology Define reusable behavior axes and their allowed values, then inspect how cases and benchmarks cover them. Coverage Engineering Case Construction Patterns Define reusable mechanisms for constructing cases and steer how benchmarks use or avoid them. Coverage Management Set Up Benchmark Coverage Define benchmark intent, facet handling, artifact preferences, and evidence requirements before generating coverage work.
AI context