---
title: "Governance and audit"
description: "How Tedix scopes authority and preserves evidence for digital work."
---

> 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.

# Governance and audit

# Governance and audit

Tedix treats authorization and evidence as part of execution, not as an
afterthought.

## Scoped authority

A worker receives an identity, role, policies, tool grants, and spending
limits. Sensitive operations can require an approval before execution.
Delegated work carries explicit scope instead of inheriting every capability
of the delegating worker.

## Evidence with the work

Tedix can preserve:

- who or what requested the work;
- which worker or external agent performed it;
- the tools and source material used;
- approvals and policy decisions;
- produced artifacts and completion receipts;
- costs and provider attribution where available.

This separates a successful outcome from an unsupported claim that something
probably happened.

## Customer-owned continuity

Operational history and memory remain attributable to the customer
organization. Runtime components can change while the worker's identity,
policies, and durable records remain stable.

Governance is not a promise that every automated decision is correct. It is
the system for limiting authority, preserving evidence, and making review or
rollback possible.

Source: https://docs.tedix.dev/governance-and-audit/index.mdx