Teammately Docs
Docs menu

reference

Versions, staleness, and resolution

Track how correctness objects evolve and how teams resolve conflicting evidence.

Versions, staleness, and resolution

Definition

Versions, staleness, and resolution describe how correctness artifacts evolve without making old evidence ambiguous. Cases, Policies, Rubrics, Benchmark Versions, supported Case-scoped reference outputs, and customer-owned review context can change at different times; version boundaries explain which evidence belongs to which state.

Use this reference when a result changed unexpectedly, a policy was revised, a case was refreshed, or reviewers need to know whether older benchmark evidence still applies.

Fields, states, or lifecycle rules

  • Versions preserve what changed and what evidence was produced before the change.
  • Staleness means older evidence may no longer reflect the current case, standard, coverage, or candidate boundary.
  • Resolution work should name whether the fix belongs to a case, output, policy, rubric, coverage plan, benchmark version, or run metadata.
  • Comparisons are weak when artifact versions are hidden.
  • This page describes public object semantics, not retention, audit-log completeness, or compliance guarantees.

Versions, staleness, and resolution should be read with Versioning and Staleness, Benchmark versioning, Case versioning, and Policy Conflicts and Revisions.

Worked example

Versions, staleness, and resolution boundary

01

Start

Behavior input

State change
Reviewers revise a compatibility policy after finding unsupported-claim failures.
02

Middle

Judgment into standard

Benchmark evidence
Runs against the old policy remain interpretable, but they should not be summarized as current evidence without naming the old policy version.
03

Result

Interpretation

Interpretation
The resolution note explains whether to rerun, revise the benchmark version, or preserve the old result as historical context.

Source confidence

Code-backed: Benchmark, Policy, and Rubric types carry version facts; Benchmark Datasets → Snapshots and Policy activity preserve named historical boundaries. Cross-object staleness and conflict resolution are explicit review decisions rather than a universal automatic state.

Related task pages

Concept / Governance and ReproducibilityVersioning and StalenessKnow when correctness objects changed and when old evidence may need review.Task / Governance and ReproducibilityResolve conflicting correctness evidenceReconcile disagreement without hiding the Cases, expert judgments, sources, or versions that produced it.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

Governance and Reproducibility Versioning and Staleness Know when correctness objects changed and when old evidence may need review. Governance and Reproducibility Resolve conflicting correctness evidence Reconcile disagreement without hiding the Cases, expert judgments, sources, or versions that produced it. Governance and Reproducibility Detect and route stale correctness evidence Identify which current claims need review after Cases, standards, coverage, sources, or target behavior change.
AI context