docs: audit links, glossary T0-T4, readability pass
CI & Release / Verify simulator (push) Skipped
CI & Release / Trivy scan (push) Skipped
CI & Release / Semantic Release (push) Skipped
CI & Release / Verify simulator (pull_request) Failing after 4s
CI & Release / Trivy scan (pull_request) Skipped
CI & Release / Semantic Release (pull_request) Skipped

Extend glossary with storage floors, source of truth, and linkable anchors.
Fix broken links, pose frame drift, rsync/offload wording, and README tone.
Add docs/improvement audit records and live demo links in design journey.
This commit is contained in:
2026-07-10 10:46:59 +01:00
parent ed531f9fb6
commit 5f6fd8462c
27 changed files with 376 additions and 193 deletions
+7 -3
View File
@@ -6,9 +6,13 @@ Accepted (2026-07-08)
## Context
Data lives in three places: on the drone's NVMe in flight (T1), in the ground
warehouse after landing (T3), and in the dev/simulation environment. If each
tier used a different format or layout, offload would need transformation code,
Data lives across [storage floors](../00-glossary.md#t0--hot) T0T4. Primary persistent
stores are [T1](../00-glossary.md#t1--warm) (drone NVMe in flight) and
[T3](../00-glossary.md#t3--warehouse) (ground warehouse after landing);
[T0](../00-glossary.md#t0--hot) is the in-memory hot window,
[T2](../00-glossary.md#t2--shared) optional on-board derived replication,
[T4](../00-glossary.md#t4--dev) dev/sim slices. If each floor used a different
format or layout, offload would need transformation code,
schemas would drift, and a query proven on the bench would not run unchanged on
flight data.