Internal documentation
For people running, changing or reviewing ACC.
| Page | What it covers |
|---|---|
| Architecture | Components, how they talk, trust boundaries |
| Components | Each part's job, interfaces and files |
| Data model | Tables and what they hold |
| Configuration | Settings and environment variables |
| Security | Auth, secrets, permissions, threat model |
| Development | Setup, tests, lint, the demo instance, conventions |
| Operations | Install, deploy, back up, restore, runbook |
| Containers qualification runbook | Owner-only account/build/pin/setup/collect/rollback order and qualification pitfalls |
| Design system | UI tokens, components and rules |
| Decisions and roadmap | Why it is built this way, and what's next |
| Group Exchange | Group exchange publishes explicitly selected committed history |
| Manual failover | PostgreSQL standby setup, explicit authority changes, crash fencing and failback |
| Device pairing | Disabled LAN pairing, signer contract, transient imports and rendered policy boundaries |
| Telemetry implementation | The main ACC owns the telemetry queue |
| Node task ownership | Main-created machine tasks, lifecycle owners, cancellation and leak tests |
| Dependency updates | Use this runbook when reviewing dependency PRs or replacing a downloaded tool |
| Website | How rynhult.dev and its /docs/ are built from site/ and this wiki |
| Mobile Devices | This is the experimental server contract for native iOS/Android enrollment and credentials |
This page is generated from docs/wiki/Internal.md; the same page is under Guide inside Rynhult.