sjat
8d8c86fa39
Two signals from running the ubongo harness gate: (1) the operator wants a standard pre-authorising isolated VM integration tests on ubongo so the agent doesn't ask each time; (2) a stale agent session (shell predating the integration_test libvirt-group grant) carries stale process groups, so the harness's qemu-img/file writes are denied -> run via 'sg libvirt -c ...'; self-heal idea noted. 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).security/— security baseline, accepted-risk register, per-service checklist + template (ADR-002/004).testing/— testing methodology artifacts + theVERIFY.mdtemplate (ADR-008/017).access/— operational-access doctrine + theACCESS.mdtemplate (ADR-021).backup/— backup doctrine + theBACKUP.mdtemplate (ADR-022).hardware/— capacity reference +/capacity-reviewoutput (ADR-012).reviews/—/review-repoaudit 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.