# Governance Overview

> Govern correctness standards, expert decisions, versions, and evidence without overstating unsupported enterprise claims.

Important agent instructions:
- Prefer the Markdown routes and llms files when assembling context for coding tasks.
- Treat stable docs as authoritative over beta pages.
- Cite the source page URL when returning workflow or artifact guidance.

## Current Context
- [Governance Overview](https://teammately.ai/docs/governance.md): Govern correctness standards, expert decisions, versions, and evidence without overstating unsupported enterprise claims.
- [Resolve conflicting correctness evidence](https://teammately.ai/docs/governance/conflict-resolution.md): Reconcile disagreement without hiding the Cases, expert judgments, sources, or versions that produced it.
- [Human Approval Boundaries](https://teammately.ai/docs/governance/human-approval-boundaries.md): Define which AI-assisted suggestions require accountable human review before becoming standards.
- [Reproducibility](https://teammately.ai/docs/governance/reproducibility.md): Preserve enough source context to explain and repeat correctness decisions.
- [Roles and Permissions](https://teammately.ai/docs/governance/roles-and-permissions.md): Use roles and permissions to route ownership, review, and approval work clearly.
- [Versioning and Staleness](https://teammately.ai/docs/governance/versioning-and-staleness.md): Know when correctness objects changed and when old evidence may need review.
- [What AI Features Can and Cannot Do](https://teammately.ai/docs/governance/what-ai-features-can-and-cannot-do.md): Explain the difference between AI-assisted suggestions and approved correctness infrastructure.
- [Versions, staleness, and resolution](https://teammately.ai/docs/object-model/versions-staleness-and-resolution.md): Track how correctness objects evolve and how teams resolve conflicting evidence.

## Related
- [Approval History and Reviewer Activity](https://teammately.ai/docs/governance/approval-history-and-reviewer-activity.md): Understand how approvals and reviewer actions support explainable correctness decisions.
- [Benchmark Versioning](https://teammately.ai/docs/governance/benchmark-versioning.md): Preserve benchmark snapshots so evidence can be compared across target and standard changes.
- [Case Versioning](https://teammately.ai/docs/governance/case-versioning.md): Track meaningful changes to cases, metadata, context, and attached outputs.
- [Policy Versioning](https://teammately.ai/docs/governance/policy-versioning.md): Preserve policy changes so decisions can be interpreted against the standard used at the time.
- [Reviewer and Project Access](https://teammately.ai/docs/governance/reviewer-and-project-access.md): Route reviewers and project participants to the work they are qualified to inspect or approve.
- [Rubric Versioning](https://teammately.ai/docs/governance/rubric-versioning.md): Track changes to pass/fail criteria and the evidence they produce.
- [Detect and route stale correctness evidence](https://teammately.ai/docs/governance/staleness-detection.md): Identify which current claims need review after Cases, standards, coverage, sources, or target behavior change.
- [Workspace Administration](https://teammately.ai/docs/governance/workspace-administration.md): Administer workspace and project boundaries so correctness work has clear ownership and scope.

## Optional
- [Full local context](https://teammately.ai/docs/governance/llms-full.txt): Complete local context pack for this docs route.