Provider-agnostic cloud operations laboratory for collecting, reconstructing, replaying, and investigating infrastructure state and operational history.
- Python 99.6%
- Makefile 0.4%
| .vscode | ||
| core | ||
| docs | ||
| examples | ||
| tests | ||
| .gitignore | ||
| Makefile | ||
| pyproject.toml | ||
NIMBUS Documentation
docs/
├── architecture/ Current implementation decisions and specifications
├── rfcs/ Domain and architectural specifications (RFC-000 onward)
├── development/ Project history (changelog, devlog)
├── diagrams/ Mermaid and exported diagrams
└── blog/ Engineering blog posts
- architecture/ — maps how the design decisions in the RFCs were translated into code. Contains SPECIFICATIONS.md (technology stack) and CAPABILITIES.md (user-visible capabilities).
- rfcs/ — the authoritative source for domain concepts, invariants, and architectural rules. RFCs define what must be true; they do not prescribe implementation.
- development/ — records what changed and why. CHANGELOG.md is a chronological log; DEVLOG.md captures rationale, alternatives, and lessons.
- diagrams/ — visual representations of architecture, data flow, and state machines.