Orchestration core

Every other layer of RAVID changes over time. The orchestration core decides how fast, and keeps everything consistent while it does.

Epochs#

Time is divided into epochs. An epoch is the unit of change: node sets, routing parameters and temporary identifiers are valid for one epoch and then retired. Shorter epochs give observers less time to correlate; longer epochs reduce overhead. The core can tune epoch length per layer.

Responsibilities#

• Scheduling rotation of routes, relays and compute instances.
• Publishing the current, signed view of valid nodes so clients can build paths without asking a central server about their own traffic.
• Health and capacity tracking, so rotation never drops the network below safe capacity.
• Overlap windows where old and new infrastructure run together, so rotation does not break open sessions.

What the core does not see#

The core coordinates infrastructure, not users. It does not route traffic, does not hold user keys and does not need to know which client uses which path. Clients fetch the published network view and build their routes locally.