Repository source and configuration establish tracked implementation. Feature specifications state intended contracts. Neither proves that a stack is deployed, healthy, or current in a live environment unless separately recorded as verified evidence.
| Document | Covers |
|---|---|
architecture/README.md |
Platform ownership, layers, dependencies, and deployment boundaries |
deployment/README.md |
CI, Tekton, BuildKit, images, and reconciliation workflows |
edge-networking/README.md |
Gateway API, DNS, certificates, aliases, and edge routing |
host-provisioning/README.md |
Inventory, K3s lifecycle, host configuration, and verification |
kubernetes-workloads/README.md |
Workload conventions, scheduling, inference, and registries |
observability/README.md |
Metrics, logs, traces, profiles, dashboards, and alerts |
secrets-management/README.md |
Authentik, OpenBao, secret delivery, and operational boundaries |
storage/README.md |
Ceph, object storage, backups, and recovery evidence |
voice-satellites/README.md |
Supported satellite provisioning and unresolved deployment state |
operations/README.md |
Cross-feature operational runbooks and command safety |
quality/README.md |
Testing, documentation validation, and evidence expectations |
research/README.md |
Non-authoritative research and evaluation records |
- Root and scoped
AGENTS.mdfiles govern contributor and agent behavior. - Approved feature specifications define intended behavior.
- Tracked source, tests, and configuration establish repository implementation.
- Runbooks describe supported operations but do not prove live execution.
- Research and Git history preserve evidence without governing current behavior.
Conflicts between intended contracts and tracked implementation remain explicit verification gaps until an approved change resolves them.