MeshMap · Gossip-Merkle swarm

What each leaf carries: BPv7 custody bundles → meshnet (operator sign-in)
density · range · terrain & elevation · signal · time — propagation, latency & uptime from geography
OV-1 austerity meshnet-swarm tabletop: devices carry custody leaves, no fixed backhaul, no central server — the field map below is the OV-2 operational node-connectivity view of that concept (nodes=devices, edges=needlines).
Field map random-geometric graph OV-2
🔋 Battery life by broadcast mode
Scenario presets Metro mesh
Tunable parameters
Map legend what the dots & lines mean
source reached waiting unreachable
peer repeater ferry (mule) road (drag ● to reroute)
Live geometry & propagation solved in real time
swarm://math.console0 lines
Field survey report config → operationalizable next steps
⏱ Danger Zone — layer-lag playground capture → first internet-validated hash
Hash ladder, log-time: L1 entry_hash (on-device, offline-capable) → mesh replicas (gossip, still no internet) → L2 witness leaf — FIRST INTERNET → L3 git SHA → L4 Rekor. The red band is the Danger Zone (solid to median, hatched to p95).
Survival curve — share of captures still inside the Danger Zone after t.
REVENANT · integrity-by-permanence. At scale, messages propagate peer-to-peer with no central server via gossip + Merkle-root comparison — two peers exchange roots, the lagging peer pulls missing leaf-ids by stanza-id. This simulator is the geometry that governs whether, how fast, and how reliably that swarm converges.