RAVID architecture
How RAVID coordinates routing, compute and storage into one continuously changing privacy layer.
Privacy tools usually protect a connection. RAVID protects the infrastructure around it, by making sure none of it stays in one place long enough to be mapped.
RAVID is organised as four layers, from the centre outward. The core decides when things change. The outer layers decide how traffic, compute and data move.
- 00Orchestration core
The central coordination layer manages time, motion, routing and infrastructure changes.
- 01Stealth network
Communication travels through dynamically generated pathways designed to reduce persistent routing information.
- 02Infrastructure
Compute resources can be continuously replaced, relocated and reconfigured.
- 03Storage
Information can be fragmented, distributed and reconstructed only when needed.
Lifecycle of a request
- 1Epoch begins
The orchestration core opens a new time window and publishes which nodes and routes are valid for it.
- 2Path is built
The client selects several relays from the current set and builds a layered, encrypted path. No relay learns the full route.
- 3Traffic moves
Packets are sent in uniform sizes with timing smoothing so that size and rhythm reveal less about the activity.
- 4Services resolve
The destination may be a short-lived compute instance or reconstructed data fragments, not a fixed server.
- 5Epoch ends
Paths and temporary identifiers expire. Infrastructure may be replaced or relocated. The map the observer built goes stale.