Ground layer
CivicNet
குடிமை வலை
The diaspora intranet that connects Civic Houses to each other and to the cloud core. Consumer telco carries the pipe; the trust boundary lives inside a WireGuard overlay we own.
Now · Aarambam
Only Node 000 (cloud core, archive.tlte.cloud) exists. The CivicNet spec is drafted and reproducible; no ground node has yet joined it.
Becoming · Nilaiththanmai
Every Civic House joins CivicNet on day one. Diaspora-wide overlay, homeland-safe fallback, DTN reconciliation once per era.
Layered architecture
- Access — commercial 5G router + fixed-line broadband (dual WAN, active-active).
- Bridge — UniFi gateway with VLAN segmentation (kiosk / staff / IoT / guest).
- Overlay — WireGuard mesh to the cloud core; per-node key, rotated per era.
- Core — archive.tlte.cloud terminates the tunnel; only hashed corpus traffic flows.
Network segmentation
- Kiosk VLAN — outbound only to the archive mirror, DNS pinned.
- Staff VLAN — separate credentials, MFA, no lateral path to the kiosk.
- IoT VLAN — CCTV recorder only; write-only push to encrypted local store.
- Guest VLAN — captive portal to a read-only mirror; no route to any other VLAN.
Hop math (illustrative)
London (Node 000) ↔ Toronto (planned Node 003) via consumer transit: ≈ 5,570 km, ≈ 28 ms RTT theoretical, ~80 ms observed. DTN bundles reconcile once per era (7d); a full Tier-A corpus resync fits inside one overnight window at 50 Mbps.
What CivicNet is not
- Not a mesh radio network. Not LoRa, not Meshtastic — those are becoming, not now.
- Not a private ISP. We do not resell connectivity.
- Not a P2P protocol. Every node terminates against the archive spine.