docs: align wire-spec and mark implemented vs proposed
Keep the 45-byte pose frame consistent across docs, simulator, and prototype, clarify MinIO is not peer sync, and state clearly that the repo is a from-scratch platform sketch with options rather than mandates.
This commit is contained in:
@@ -17,6 +17,25 @@ This repository describes how to build, deliver, test, and operate that platform
|
||||
7. **SQL is the contract.** Peer data access is read-only DuckDB SQL over SSH forced commands — the query language already lives on both ends, so no service, port, or protocol is invented for it.
|
||||
8. **No debug API.** The bench and the flight use the same channel: an engineer debugging on the ground runs the identical query through the identical wrapper, permissions, and output format a peer drone would use. What you test is what flies.
|
||||
|
||||
None of the concrete tool picks above are mandates. This repo is a **from-scratch platform sketch**: enough structure to hire and build against, with every decision recorded so the team can replace a piece when a better fit appears.
|
||||
|
||||
## Implemented now vs proposed next
|
||||
|
||||
Honest map so a reader knows what runs today versus what is design intent.
|
||||
|
||||
| Area | Implemented in this repo (runnable PoC) | Proposed for a production air-gapped fleet |
|
||||
| --- | --- | --- |
|
||||
| On-board layout | Hive-partitioned Parquet writer, seal step, DuckDB views | Same contract; Compose services under systemd |
|
||||
| Pose path | Fixed **45-byte** UDP frame + 2D bandwidth visualisation | Zenoh pub/sub (UDP kept as degraded minimal profile) |
|
||||
| Peer query | Read-only SQL **gate** over HTTP explorer (keyword allow-list) | Same gate idea via **SSH forced command** + OS/engine hardening |
|
||||
| Bulk sync | Visualised opportunistic transfer volume | rsync/rclone over persistent SSH between peers |
|
||||
| Mesh trust | Ansible templates for WireGuard + ed25519 forced commands | Provisioned per-device keys; nothing joins at runtime |
|
||||
| Ground segment | k3d/Terraform sim: lake, Grafana, offload CronJob, optional MinIO | k3s warehouse, GitOps overlays, post-flight mirror |
|
||||
| CI / delivery | GitHub Actions: pytest, smoke flight, Trivy, semver release + fleet manifest artifact | Self-hosted GitLab + registry inside the air gap (same stages) |
|
||||
| Docs | Problem, architecture, ADRs, design journey, open questions | Living ADRs owned by the team |
|
||||
|
||||
Start from the [design journey](docs/12-design-journey.md) for the story; use the table above when reviewing scope.
|
||||
|
||||
## Documentation
|
||||
|
||||
| Document | Contents |
|
||||
|
||||
Reference in New Issue
Block a user