NomadNet

Type: Application Role in Styrene: Hub platform for fleet configuration and identity registry

NomadNet is a text-based communication and information platform built on Reticulum and LXMF. In Styrene, it serves as the fleet’s configuration authority.

Why Styrene Uses NomadNet

The Styrene Hub needs to:

  • Serve device specifications
  • Store fleet configuration
  • Register device identities
  • Act as LXMF propagation node

NomadNet provides all of this out of the box:

  • Pages — Serve text/micron content over Reticulum
  • Node mode — Acts as LXMF propagation node
  • No HTTP — Works entirely over mesh networks
  • Low bandwidth — Designed for constrained links

Hub Architecture

┌─────────────────────────────────────────┐
│  Styrene Hub (NomadNet node)            │
├─────────────────────────────────────────┤
│  /styrene/                              │
│  ├── devices/                           │
│  │   ├── rpi4b.yaml     (device spec)   │
│  │   ├── nanopi-r5c.yaml               │
│  │   └── ...                            │
│  ├── fleet/                             │
│  │   ├── mesh.yaml      (fleet config)  │
│  │   └── identity.yaml  (registry)      │
│  └── index.mu           (micron page)   │
├─────────────────────────────────────────┤
│  LXMF Propagation Node                  │
│  (stores messages for offline devices)  │
└─────────────────────────────────────────┘

Micron Format

NomadNet uses “micron” markup for pages — a minimal format designed for bandwidth-constrained networks:

`!Styrene Fleet Hub`b

Welcome to the fleet configuration hub.

`[Device Specs`:/styrene/devices/`]
`[Fleet Status`:/styrene/status`]

>Last updated: 2026-02-01

This format renders in NomadNet’s TUI and can be converted for other outputs.

Propagation Node Role

When styrened is offline, messages destined for it are held at the Hub:

styrene-tui ──LXMF──→ Hub ──stores──→ styrened online ──delivered

This enables true asynchronous fleet management — send commands, disconnect, devices execute when they reconnect.

Hub Deployment

Current: K8s on brutus cluster Future: Dedicated hardware for off-grid scenarios

The Hub must be reachable from both:

  • Operator workstation (styrene-tui)
  • Fleet devices (styrened)

Data Served

PathContentSize
/styrene/devices/*.yamlDevice specifications~1 KB each
/styrene/fleet/mesh.yamlMesh configuration~2 KB
/styrene/fleet/identity.yamlDevice identity registrygrows
/styrene/*.muHuman-readable pages~1 KB each

All content fits easily over Reticulum links, even over LoRa.

TUI Integration

The TUI (styrened.tui) will include a Hub browser screen:

  • Browse available device specs
  • View fleet configuration
  • Read documentation pages
  • All without leaving the TUI

Resources

Graph

Backlinks