Teammately Docs
Docs menu

concept

Policies and rubrics

Learn how Teammately turns product judgment into reusable policies and scoring rubrics.

Policies and rubrics

Definition

Policies state governed expectations for behavior and the situations to which those expectations apply. Rubrics are evaluator definitions used to judge Case responses. A Policy can link relevant Cases and Rubrics, but the objects remain separately versioned and reviewable.

Why it matters

This separation lets a team correct the right layer. A mistaken rule belongs in the Policy; an overbroad scope belongs in applicability; an unreliable check belongs in the Rubric. Evaluation evidence should show which applicable Rubric produced each outcome rather than treating an aggregate score as the standard itself.

Standard pair check

The pair is healthy when...Rework it when...
The policy states the product behavior rule.The policy is only tone, preference, or broad quality advice.
Applicability names the cases where the rule belongs.The same rubric could apply to nearly everything.
The Rubric tests one observable requirement.The Rubric combines several decisions into one unclear result.

Where it appears in the product

Create and inspect Policies and Rubrics under Correctness Governance. Expert Contributions can supply attributable candidate artifacts, but contributed content is not automatically approved. Benchmark Evaluations reports applicable Rubric outcomes for the frozen Benchmark Version.

Artifacts it affects

Policies and Rubrics affect Case links, applicability, Benchmark Versions, evaluator coverage, Run results, failure clusters, and staleness. Changing either governed object requires a new version boundary before the revised standard is treated as current evaluation evidence.

Worked example

Eligibility policy to must-level rubric

A support Policy requires entitlement answers to use the controlling contract or state uncertainty. Its applicability is limited to plan limits, contract exceptions, and admin-controlled access. A linked binary Rubric checks whether the response identifies that source or explicitly withholds an unsupported eligibility claim. Evaluation results can then show the failed Rubric on the affected Cases without broadening the rule to unrelated setup questions.

Source confidence

Code-backed: the current Policy and Rubric list and detail routes define their separate identities, editable fields, links, versions, and approval state. Expert Contribution and Benchmark Evaluation pages define how attributable input and evaluator outcomes enter those objects' wider lifecycle.

Found something unclear?

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

Report a docs issue

Continue learning

Related docs

AI context