---
title: "Advanced repository governance"
description: "Choose whether a tenant repository needs standard review, agent attribution, or claim-bound deployment enforcement."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.tedix.dev/llms.txt
> Use this file to discover all available pages before exploring further.



# Advanced repository governance

Use the least restrictive controls that cover the repository's actual risk.
Tedix does not require a Git certification service or repository observer key.

- Keep normal tests, branch protections, and risk-appropriate approvals.
- Link the Work Item, agent run, commit, and outcome evidence when attribution is useful.
- Give agents only the repository and deployment permissions their task requires.
- Verify source changes, test execution, and production behavior separately.
- Keep changes small and provide a tested recovery path for releases.

A commit reference identifies an artifact; it is not proof of correctness,
a passing test run, or a successful deployment. Work acceptance happens before
execution and settlement records the commits afterwards; no separate review or
certification step sits between them. Historical Git-tie receipts remain audit
records, but new work does not produce them.

Source: https://docs.tedix.dev/governed-repositories/index.mdx