sjat
3cfcb1c2e9
High-level build order for the project (Approach A): one Off-site/Remote-access track first (Gandi DNS-as-code -> askari -> NetBird control plane -> enroll ubongo + road-warrior laptops -> harden), a procurement gate sized by /capacity-review, then the Cluster track. Sequences the docs/TODO.md backlog into milestones and records why the order is what it is. Decisions captured this session: Gandi over Cloudflare is values-driven and independent of NetBird (sequenced first so records are born at Gandi); public DNS managed as code (Ansible, consistent with internal DNS + Terraform-owns-no-DNS); NetBird-on-ubongo before base default-deny (chicken-and-egg); cluster procurement gated on patterns proven on two cheap hosts. Wire ROADMAP.md into CLAUDE.md's Further-reading index and point TODO.md at it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| access | ||
| backup | ||
| decisions | ||
| hardware | ||
| reviews | ||
| runbooks | ||
| security | ||
| superpowers | ||
| testing | ||
| CAPABILITIES.md | ||
| FRICTION.md | ||
| README.md | ||
| ROADMAP.md | ||
| TODO.md | ||
docs/
Project documentation.
decisions/— Architecture Decision Records (ADRs): the "why" behind the design. Numbered from 001; each records context, the decision, and what was ruled out.runbooks/— step-by-step operational procedures (add a host, add a role, rotate secrets).
For what is actually built vs only designed, see STATUS.md at the repo root —
the ADRs describe intent, not necessarily current reality.