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. Plane Breakdown --------------- .. list-table:: :widths: 20 20 60 :header-rows: 1 * - Plane - Compartments - Summary * - :doc:`identity` - Announce, Discovery, Linked, Presence - Node cryptographic identity announcement, peer discovery across libp2p and Nostr, DID linking, and heartbeat presence tracking. * - :doc:`peering` - Peering, Budget, Capacity, Reporter, Strain, Trust - Bilateral peering handshakes, micro-credit budgeting, load shedding, network trouble reporting, strain monitoring, and peer reputation. * - :doc:`operations` - Scheduler, Updates - Periodic recurring tasks, tick generation, and signed software release verification and auto-updating. * - :doc:`services` - 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. * - :doc:`store` - Sync, Retention, BlobWire, BlobReplication - Negentropy range-based state reconciliation, storage quota pruning, chunked blob transfer, and mirror replication. * - :doc:`transport` - Link, LAN, P2P, Bridge, Mediation - Transport health watchdog, local LAN multi-cast, NAT traversal, Unix socket bridge, and multi-hop circuit mediation. .. toctree:: :maxdepth: 2 :hidden: identity peering operations services store transport