sjat/boma
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
boma/docs
History
sjat 5d14efc864 docs: Phase 1 complete — clients enrolled + NetBird client runbook 
mamba + work laptop enrolled in the mesh → ubongo reachable from anywhere; the
mobile-access goal is met and Phase 1 (remote access) is complete. Adds
docs/runbooks/netbird-client.md (reusable client-enrollment runbook) + STATUS/
ROADMAP flips + CLAUDE.md reading-table entry.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-17 17:11:32 +02:00
..
access docs(access): correct ADR-021 governance (runbook+gate, not scaffold) 2026-06-09 17:52:24 +02:00
backup docs(backup): add BACKUP.md template + backup__* contract (ADR-022) 2026-06-10 11:20:01 +02:00
decisions docs: record Caddy/Gandi DNS-01 as resolved + proven (was M4a deferral) 2026-06-15 06:57:55 +02:00
hardware docs: record ubongo physical build (2026-06-11) 2026-06-11 10:32:26 +02:00
reviews docs(review): 2026-06-14 repo audit — M4a doc drift + Traefik→Caddy lag 2026-06-14 18:37:54 +02:00
runbooks docs: Phase 1 complete — clients enrolled + NetBird client runbook 2026-06-17 17:11:32 +02:00
security docs(netbird): M4b done — STATUS/ROADMAP/risks/friction 2026-06-16 07:48:53 +02:00
superpowers docs(plan): M5 mesh-enrollment implementation plan 2026-06-17 15:49:28 +02:00
testing chore(kaizen): first /kaizen run — curate 12 friction signals 2026-06-14 21:46:23 +02:00
CAPABILITIES.md docs: reconcile 2026-06-14 review findings (O1-O7,O18,O22) 2026-06-14 19:06:33 +02:00
FRICTION.md docs: M5 mesh enrollment — ubongo + askari on the mesh 2026-06-17 16:40:02 +02:00
README.md docs: reconcile lower-severity review findings (O9-O24) 2026-06-14 19:31:40 +02:00
ROADMAP.md docs: Phase 1 complete — clients enrolled + NetBird client runbook 2026-06-17 17:11:32 +02:00
TODO.md docs(todo): collapse done items to one-line pointers; open-only convention 2026-06-14 22:00:53 +02:00

README.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).
  • security/ — security baseline, accepted-risk register, per-service checklist + template (ADR-002/004).
  • testing/ — testing methodology artifacts + the VERIFY.md template (ADR-008/017).
  • access/ — operational-access doctrine + the ACCESS.md template (ADR-021).
  • backup/ — backup doctrine + the BACKUP.md template (ADR-022).
  • hardware/ — capacity reference + /capacity-review output (ADR-012).
  • reviews/ — /review-repo audit trail.
  • CAPABILITIES.md / ROADMAP.md / TODO.md / FRICTION.md — what boma does, the build order, the backlog, and recurring-friction notes.

For what is actually built vs only designed, see STATUS.md at the repo root — the ADRs describe intent, not necessarily current reality.