Governance and audit

Accountability is the product, not a compliance layer bolted onto it. Tedix treats authority and evidence as part of execution: every unit of agent work carries an identity that persists, a budget that holds, an approver who is never the requester, and a record you can show afterward.

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.

A settled outcome records what the executor reports; completion does not require independent review or certify correctness. Inspect the evidence and record corroboration or contradiction when the result is checked.

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.

Choose governance proportional to the risk

Tedix does not require every customer repository to copy the controls used by the Tedix infrastructure monorepo. A team can use ordinary repository reviews, record agent attribution without blocking delivery, or require exact claim-bound proof for autonomous production deployments. See advanced repository governance for the decision guide. Nimbus Docs creation and publication do not require repository provenance enforcement.