Unified mesh · doctrinal centrepiece
Ground + Sky Civic Mesh
தரை + வான் · ஒரே வலை
Not two projects. One mesh. The ground layer carries daily reads; the sky layer carries archive integrity when the ground is hostile. Same archive, same 21 Laws, same covenant.
The diagram in words
┌─────────────────────────────────────┐
│ Node 000 · Cloud Core (London) │
│ archive.tlte.cloud · Tier-A spine │
└───────────────┬─────────────────────┘
│ WireGuard overlay
┌───────────────┼─────────────────────┐
│ │ │
CivicNet ground Public Brain kiosks Sky Layer
(5G + fibre) (offline-first) (hosted payload)
│ │ │
└── Nodes 001–010 (planned) ──────────┘
│
Federation ladder
(Ally → Sovereign)
Now · Aarambam
Only the cloud core exists. Ground and sky layers are drafted; neither is deployed.
Becoming · Nilaiththanmai
Reads served from the nearest node. Sky fallback when the ground is throttled. Archive spine reconciles across both once per era.
Why unified
- One archive, one integrity hash, one covenant.
- No dual governance — sky trustees and ground stewards sit in the same Continuity Office.
- Failure modes are complementary: ground carries volume, sky carries continuity.
What the mesh guarantees
- An archive read is possible even if any one of ground or sky is down.
- Every node's mirror is verifiable — SHA-256 manifest, no trust required.
- No node is single-purpose. Every node reads and every node reconciles.