docs: WireGuard vs SSH, Flux GitOps, CONTRIBUTING with TDD-first
Document why WireGuard and SSH are complementary layers, add Flux boundaries for the ground segment, shared var/ data paths in docs/06, and a contributor guide with the required test-first workflow.
This commit is contained in:
@@ -12,11 +12,16 @@ Rules for anyone (human or tooling) contributing to this repository.
|
||||
## Project layout
|
||||
|
||||
```
|
||||
docs/ Design documentation (Markdown + Mermaid)
|
||||
simulator/ Virtual drone fleet — Python data generator (Parquet/DuckDB pipeline)
|
||||
prototype/ 2D swarm visualization — React + TypeScript (Vite)
|
||||
docs/ Design documentation (Markdown + Mermaid)
|
||||
simulator/ Virtual drone fleet — Python data generator (Parquet/DuckDB pipeline)
|
||||
prototype/ 2D swarm visualization — React + TypeScript (Vite)
|
||||
infra/ Ansible host prep, Terraform workloads, Flux GitOps overlays
|
||||
var/t1/ Shared T1 live lake (gitignored runtime data)
|
||||
var/t3/ Shared T3 warehouse (gitignored runtime data)
|
||||
```
|
||||
|
||||
See [`CONTRIBUTING.md`](CONTRIBUTING.md) for the development workflow and TDD requirements.
|
||||
|
||||
## Conventions
|
||||
|
||||
- Markdown: ATX headings, fenced code blocks with language tags, pipe tables.
|
||||
|
||||
Reference in New Issue
Block a user