1.1. Fleetmesh Architecture Overview
1.1.1. Fleetmesh System Architecture & Product Specifications
Fleetmesh (fleetmesh.org) is a sovereign, verifiable edge compute, storage, and networking fabric.
1.1.1.1. 1. Product Boundaries
Fleetmesh decouples the edge execution plane from declarative fleet orchestration:
+---------------------------------------+
| meshctl |
| Declarative Fleet Orchestrator (Rust)|
+---------------------------------------+
|
[meshnode-control/1]
(Unix Domain Socket / IPC)
|
+---------------------------------------+
| meshnode |
| Sovereign Node Daemon Engine (Python)|
+---------------------------------------+
| | |
+--------------+ | +--------------+
| | |
+---------------+ +---------------+ +---------------+
| Wire Transport| | Compute & ZK | | Storage & Sync|
| - Iroh QUIC | | - WASM sandboxes| | - SQLite |
| - libp2p | | - ZK-CPU proofs | | - Blossom |
| - FIPS datagram| | - AI inference | | - Negentropy |
| - WebSocket | | - Cashu escrows | | - Event stores|
+---------------+ +---------------+ +---------------+
1.1.1.1.1. 1.1 meshnode — Sovereign Node Runtime
meshnode is an autonomous daemon running on physical servers, edge gateways, VPS instances, or embedded leaves (Raspberry Pi, mobile).
Core Compartments: Storage engines, cryptographic vaults, bilateral token-bucket budget accounting, and multi-transport listeners.
Local Control IPC: Exposes
/var/lib/fleetmesh/control.sockusing the line-delimitedmeshnode-control/1protocol (cmd,args,ok,result).
1.1.1.1.2. 1.2 meshctl — Declarative Fleet Orchestrator (Rust)
meshctl is the single-binary CLI for declarative configuration management:
Non-Destructive Hot-Reconciliation: Diffs declared manifests against running
meshnodedaemons and applies updates live without dropping QUIC connections or resetting receipt counters.Multi-Target Exporter: Compiles abstract manifests into:
Kubernetes Deployments, Services, and ConfigMaps (
--target=k8s).Podman Quadlet container units (
--target=quadlet).Hardened systemd service and timer units (
--target=systemd).Docker Compose topologies (
--target=compose).
Live Terminal Diffing: Visual green/red structural diffs (
meshctl diff).Legacy Migration: Converts legacy
fleetmesh.org/v1alpha1manifests tofleetmesh.org/v1alpha1(meshctl convert).
1.1.1.2. 2. Declarative Resource Kinds (fleetmesh.org/v1alpha1)
Kind |
Role |
Key Specifications |
|---|---|---|
|
Daemon identity & endpoints |
Node class ( |
|
Bilateral peering contract |
Ingress/egress filter seams, transport preference ladder, token-bucket window budgets. |
|
Capacity ceilings & admission |
Tier admission rules, AIMD recovery schedules, blinded commitment secrets. |
|
Verifiable compute execution |
WASM runtime ( |
|
AI/LLM model routing |
Provider adapters ( |
|
Multi-node fleet topology |
Peer mesh graph, cluster definitions, cross-region routes. |
1.1.1.3. 3. Verifiable Compute & Execution Fabrics
Fleetmesh provides a multi-runtime verified compute fabric (detailed in [verified-compute-methods.md](file:///Users/j/Code/fleetmesh/fleetmesh.org/docs/verified-compute-methods.md)):
WASM Fuel Metering: Deterministic bytecode execution in [
WasmExecutor](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/compute/executors/wasm.py) with strictly metered fuel allocations, memory limits, and reproducible execution roots under modessampleanddual.Groth16 Zero-Knowledge Verification: Pure-Python BN254 pairing engine with C/Rust acceleration hooks ([
ZkGroth16Executor](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/compute/executors/zk.py#L30)) verifying ZK-CPU proofs without revealing private inputs under Modeproof.zkVM STARK-to-Groth16 Verification: Verification of RISC Zero and Succinct SP1 zkVM receipts ([
ZkVmExecutor](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/compute/executors/zk.py#L275)) binding execution journals to image IDs under Modeproof.Off-Chain Prover Services: Decentralized order-book prover delegation ([
ZkProverExecutor](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/compute/executors/zk.py#L425)) for compute-heavy witness proving.Compute-Over-Data Batching: Container execution ([
BacalhauExecutor](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/compute/executors/nondet.py#L198)) with Blossom CAS volume staging/uploading ([BlossomMountBridge](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/compute/executors/bacalhau.py#L304)), 5-state lifecycle progress tracking, and cooperative cancellation under Modedelivery.AI / LLM Model Proxying & Streaming: Direct inference connector ([
LlmExecutor](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/compute/executors/nondet.py#L26)) with Draft 2020-12 schema validation, real-time token streaming over Iroh QUIC/FIPS with per-frame ChaCha20Poly1305 AEAD encryption, and variable token escrow settlement.Autonomous ReAct Agent Orchestration: Multi-step reasoning loops ([
AgentExecutor](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/compute/executors/agent.py#L395)) with AST-safe calculator, regex, SHA-256, Blossom blob fetching, recursive child Kind 30810 Asks with budget caps, and honesty gate protection.NIP-90 DVM Gateway: Bidirectional protocol bridge ([
DVMGateway](file:///Users/j/Code/fleetmesh/meshnode/fleetmesh_node/planes/services/dvm/gateway.py)) translating Nostr Kinds 5000–5999 into canonical mesh jobs, settling via live Lightning HTLC hold invoices or order-book delegation.
1.1.1.4. 4. FIPS-140-3 Native Datagram Transport
High-assurance environments deploy the fleetmesh_fips Rust sidecar:
Direct cryptographic boundary encapsulation.
Identity-native datagram passing via
SCM_RIGHTSUnix domain sockets.Zero-dependency deployment on hardened Linux kernels.