# Daevix Docs
> Daevix documentation — architecture, sovereignty, the CLI and the operator API.

Self-hosted governance for autonomous AI agents. This index lists every page; a
page marked (pending) is stated as not-yet-written rather than linking to nothing.
The raw markdown of any page is available by appending `index.md` to its URL, and
pages published as-is from the repository link to the exact commit they render.


## Get started
- [What Daevix is](https://docs.daevix.com/get-started/what-daevix-is/): Daevix is an execution-time control plane for autonomous agents. It observes what an agent does, audits it against the record, and contains it by default — split across two planes so sovereign data never leaves the enclave that owns it.
- [Quickstart](https://docs.daevix.com/get-started/quickstart/): The shortest real path from a fresh checkout to a running enclave that an agent can talk to over its local metadata socket.
- [Your first agent](https://docs.daevix.com/get-started/your-first-agent/): Register a governed agent in a running enclave, watch the enclave reconcile it into a pod, and read the agent's identity over its local metadata socket.


## Concepts
- [The plane boundary](https://docs.daevix.com/concepts/the-plane-boundary/): The single invariant the whole system is built around: sovereign data and its keys stay inside the enclave, and the controlplane never receives them.
- [Enclaves](https://docs.daevix.com/concepts/enclaves/): An enclave is the sovereign data plane that mediates everything an agent does. It runs inside the customer's Kubernetes cluster on Kata containers and Cilium, and every operation on sovereign data happens here.
- [Desired state and convergence](https://docs.daevix.com/concepts/desired-state-and-convergence/): Understand what desired state means for a governed agent: the controlplane publishes a scoped policy snapshot, the enclave pulls it and enforces it locally, and every change takes effect on the next pull without restarting anything.
- [Attribution, not authentication](https://docs.daevix.com/concepts/attribution-not-authentication/): After reading this page you can explain how the enclave names the agent behind every connection and metadata request, and why that naming rests on where the agent runs instead of a secret that the agent presents.


## Guides
- [Register an enclave](https://docs.daevix.com/guides/register-an-enclave/): Bring a new enclave under management: mint its broker identity on the controlplane, deliver the key into the cluster, then let the broker pull and converge. Registration records metadata only — never sovereign data.
- [Author an egress policy](https://docs.daevix.com/guides/author-an-egress-policy/): Write the destination allow and deny rules that the enclave gateway enforces on every agent connection, scope and lock them, and read the audit verdicts that prove what the policy did.
- [Read the audit stream](https://docs.daevix.com/guides/read-the-audit-stream/): Tail the enclave's or the controlplane's audit as it happens, read the record shape that each event arrives in, and trace a client action back to the server-side row that proves what the platform did.
- [Offboard with crypto-shred](https://docs.daevix.com/guides/offboard-with-crypto-shred/): Erase an org's data irreversibly over the operator API: open a grace window, then destroy the org's encryption key so every value encrypted under it becomes permanently unreadable, and sweep the dead rows.


## Reference
- [CLI reference](https://docs.daevix.com/reference/cli-reference/)
- [Operator API](https://docs.daevix.com/reference/operator-api/): The controlplane's operator API manages identity, policy, and the desired state of each enclave. It authors and publishes; the enclave converges. It never receives sovereign data.
- [Audit event taxonomy](https://docs.daevix.com/reference/audit-events/)
- [Configuration](https://docs.daevix.com/reference/configuration/): Configure every Daevix component through command-line flags and DVX_ environment variables. This page gives the precedence rules, the defaults that differ per component, and the fail-closed settings that you cannot quietly turn off.
- [IAM](https://docs.daevix.com/reference/iam/)
- [Workload identity federation](https://docs.daevix.com/reference/workload-identity-federation/)


## Architecture
- [Overview](https://docs.daevix.com/architecture/overview/)
- [Agent identity](https://docs.daevix.com/architecture/agent-identity/)


## Security
- [Threat model](https://docs.daevix.com/security/threat-model/)
- [Key custody](https://docs.daevix.com/security/key-custody/): Trace who holds which keys where: the two KMS trust domains, how each plane generates and stores its keys, what keeps the controlplane out of enclave key custody, and what rotation and destruction look like.


## Sovereignty
- [Data residency](https://docs.daevix.com/sovereignty/data-residency/): Sovereign data lives in the enclave that owns it and never transits the controlplane. Residency is a property of where the enclave runs and where its keys live — both inside the customer's boundary.
- [Controlplane data minimization](https://docs.daevix.com/sovereignty/controlplane-data-minimization/)


## Self-hosting
- [Self-hosted controlplane](https://docs.daevix.com/self-hosting/self-hosted-controlplane/)
- [Cluster prerequisites](https://docs.daevix.com/self-hosting/cluster-prerequisites/): Check what a Kubernetes cluster needs before you deploy a daevix enclave into it: the Kubernetes and Cilium features that the enclave depends on, Kata container VMs for agent pods, the node host paths that its DaemonSets mount, and the images and certificates to stage.


## Changelog
- [Releases](https://docs.daevix.com/changelog/releases/): Learn how the maintainers cut a Daevix release, how the workflow proves the build reproducible, and where the docs site version comes from.