3. The Six Architectural Planes (fleetmesh_node.planes)
Fleetmesh organizes its 29 compartments into six functional planes. Each plane represents a distinct layer of responsibility with well-defined data flows and explicit channel interactions.
3.1. Plane Breakdown
Plane |
Compartments |
Summary |
|---|---|---|
Announce, Discovery, Linked, Presence |
Node cryptographic identity announcement, peer discovery across libp2p and Nostr, DID linking, and heartbeat presence tracking. |
|
Peering, Budget, Capacity, Reporter, Strain, Trust |
Bilateral peering handshakes, micro-credit budgeting, load shedding, network trouble reporting, strain monitoring, and peer reputation. |
|
Scheduler, Updates |
Periodic recurring tasks, tick generation, and signed software release verification and auto-updating. |
|
Settle, PaidFetch, Sidecars, Compute, ComputeWire, DVM, Gossip, nsite |
Value transfer via Cashu, paid content fetching, pluggable sidecar bridges, sandboxed compute (WASM / zk-verify), NIP-90 DVMs, and decentralized web hosting. |
|
Sync, Retention, BlobWire, BlobReplication |
Negentropy range-based state reconciliation, storage quota pruning, chunked blob transfer, and mirror replication. |
|
Link, LAN, P2P, Bridge, Mediation |
Transport health watchdog, local LAN multi-cast, NAT traversal, Unix socket bridge, and multi-hop circuit mediation. |