{"query":"Versioning and Staleness","corpusVersion":"local","generatedAt":"2026-09-13T04:41:02.836Z","results":[{"blockId":"governance.versioning-staleness#versioning-and-staleness","pageId":"governance.versioning-staleness","title":"Versioning and Staleness","pageTitle":"Versioning and Staleness","url":"https://teammately.ai/docs/governance/versioning-and-staleness.md","humanUrl":"https://teammately.ai/docs/governance/versioning-and-staleness#versioning-and-staleness","markdownUrl":"https://teammately.ai/docs/governance/versioning-and-staleness.md","sectionId":"versioning-and-staleness","kind":"concept","productArea":"governance","score":1783.7970566108222,"reasons":["search_match","title_match","display_title_match","term_match"],"markdown":"# Versioning and Staleness"},{"blockId":"governance.versioning-staleness#where-it-appears-in-the-product","pageId":"governance.versioning-staleness","title":"Where it appears in the product","pageTitle":"Versioning and Staleness","url":"https://teammately.ai/docs/governance/versioning-and-staleness.md","humanUrl":"https://teammately.ai/docs/governance/versioning-and-staleness#where-it-appears-in-the-product","markdownUrl":"https://teammately.ai/docs/governance/versioning-and-staleness.md","sectionId":"where-it-appears-in-the-product","kind":"concept","productArea":"governance","score":552.0485780859661,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Where it appears in the product\n\nUse the owning object page to inspect its current version and activity. Use Dataset Snapshots and Benchmark Versioning for immutable evaluation boundaries. Use Staleness Detection to identify downstream artifacts affected by a change. Use Conflict Resolution when expert or source evidence disagrees about what the new governed state should be."},{"blockId":"governance.versioning-staleness#definition","pageId":"governance.versioning-staleness","title":"Definition","pageTitle":"Versioning and Staleness","url":"https://teammately.ai/docs/governance/versioning-and-staleness.md","humanUrl":"https://teammately.ai/docs/governance/versioning-and-staleness#definition","markdownUrl":"https://teammately.ai/docs/governance/versioning-and-staleness.md","sectionId":"definition","kind":"concept","productArea":"governance","score":550.0993680600436,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Definition\n\nVersioning preserves the exact artifact state used by an earlier decision or evaluation. Staleness is the signal that current evidence, configuration, or interpretation may no longer support the same claim after a related object changes. A stale signal routes review; it does not automatically delete an artifact, invalidate every historical result, or approve a replacement."},{"blockId":"governance.versioning-staleness#related-workflows","pageId":"governance.versioning-staleness","title":"Related workflows","pageTitle":"Versioning and Staleness","url":"https://teammately.ai/docs/governance/versioning-and-staleness.md","humanUrl":"https://teammately.ai/docs/governance/versioning-and-staleness#related-workflows","markdownUrl":"https://teammately.ai/docs/governance/versioning-and-staleness.md","sectionId":"related-workflows","kind":"concept","productArea":"governance","score":542.800368665607,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Related workflows\n\n{% related-card-grid title=\"Related workflows\" %}\n- [Versions, staleness, and resolution](/docs/object-model/versions-staleness-and-resolution)\n- [Staleness Detection](/docs/governance/staleness-detection)\n- [Compare Harness Versions](/docs/benchmark-evaluations/compare)\n- [Product quickstart](/docs/quickstart)\n- [Task index](/docs/operating-manual/task-index)\n{% /related-card-grid %}"},{"blockId":"governance.versioning-staleness#source-confidence","pageId":"governance.versioning-staleness","title":"Source confidence","pageTitle":"Versioning and Staleness","url":"https://teammately.ai/docs/governance/versioning-and-staleness.md","humanUrl":"https://teammately.ai/docs/governance/versioning-and-staleness#source-confidence","markdownUrl":"https://teammately.ai/docs/governance/versioning-and-staleness.md","sectionId":"source-confidence","kind":"concept","productArea":"governance","score":532.4283184594617,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Source confidence\n\nCode-backed: current Policy and Rubric types preserve versioned governance facts, Snapshot routes preserve immutable benchmark evidence, and Comparison Directions expose a deliberately narrower advisory stale label. Cross-object staleness remains a review and routing decision, not an automatic global state transition."},{"blockId":"governance.versioning-staleness#why-it-matters","pageId":"governance.versioning-staleness","title":"Why it matters","pageTitle":"Versioning and Staleness","url":"https://teammately.ai/docs/governance/versioning-and-staleness.md","humanUrl":"https://teammately.ai/docs/governance/versioning-and-staleness#why-it-matters","markdownUrl":"https://teammately.ai/docs/governance/versioning-and-staleness.md","sectionId":"why-it-matters","kind":"concept","productArea":"governance","score":531.2470896590012,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Why it matters\n\nCases, Policies, Rubrics, Benchmark Versions, Harness Versions, and Improvement Session goals can change independently. Named versions keep old evidence interpretable. Staleness helps teams decide which current Datasets, evaluator links, Runs, or customer-owned human review context need attention before being treated as current."},{"blockId":"governance.versioning-staleness#operational-check","pageId":"governance.versioning-staleness","title":"Operational check","pageTitle":"Versioning and Staleness","url":"https://teammately.ai/docs/governance/versioning-and-staleness.md","humanUrl":"https://teammately.ai/docs/governance/versioning-and-staleness#operational-check","markdownUrl":"https://teammately.ai/docs/governance/versioning-and-staleness.md","sectionId":"operational-check","kind":"concept","productArea":"governance","score":526.6341136125461,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Operational check\n\nName the changed artifact and version, identify which downstream claim depended on it, and decide whether the old evidence remains historically valid, requires qualification, or needs replacement through a new canonical workflow. Never “resolve” staleness by editing a label while leaving the evidence boundary ambiguous.\n\nWhen the object is a Comparison Direction, also check whether a **Potentially stale** label is only advisory. Dismiss the label if the team decides the direction still represents a useful boundary.\n\n{% example-demo title=\"Revised applicability after evaluation\" %}\nExperts revise a Policy so it applies only when the customer explicitly requests a recommendation. Runs against the old Benchmark Version remain valid evidence under the former applicability rule. The current Dataset and linked Rubrics are reviewed, a new Snapshot and Benchmark Version establish the revised boundary, and new Runs use it. Any customer-owned human review context names both boundaries instead of marking every old result simply “wrong.”\n{% /example-demo %}"},{"blockId":"governance.versioning-staleness#artifacts-it-affects","pageId":"governance.versioning-staleness","title":"Artifacts it affects","pageTitle":"Versioning and Staleness","url":"https://teammately.ai/docs/governance/versioning-and-staleness.md","humanUrl":"https://teammately.ai/docs/governance/versioning-and-staleness#artifacts-it-affects","markdownUrl":"https://teammately.ai/docs/governance/versioning-and-staleness.md","sectionId":"artifacts-it-affects","kind":"concept","productArea":"governance","score":509.75510570754284,"reasons":["search_match","page_title_match","term_match"],"markdown":"## Artifacts it affects\n\nCommon triggers include changed Case input or materials, revised Policy scope, revised Rubric criteria, changed dataset membership, changed Harness configuration, and superseded source material. The responsible next action depends on the owner: correct a Case, approve a new standard version, refresh coverage, create a new Snapshot, run a new evaluation, or preserve an old result as historical context.\n\nComparison Directions use a narrower stale signal. **Potentially stale** is an advisory label for untouched AI-suggested directions, not a versioned approval state and not automatic removal. User-created and user-edited directions remain user-owned even when Teammately considers them while avoiding duplicate suggestions."}]}