Bus · Layer 1
Lattice is our name for the bus. A service publishes to a subject, and anything that cares subscribes. Nobody calls anybody else directly, so you can add or swap a part without touching the rest.
Messages are addressed by subject, not by destination. Senders and receivers stay decoupled.
Devices and machines talk over an MQTT broker, which is the same wire your edge firmware already speaks.
Inside the daemon, services use an event bus. The browser gets those events live over server-sent events.
Mx keeps the last value and a history for each mx:// subject, so a new subscriber gets the current state straight away.
Subscribe to a whole branch with MQTT wildcards instead of listing every topic.
Every service publishes an immutable build version and a heartbeat. Divergence is detected and healed.
One reading, several listeners, no coordination. These are real subject shapes from the platform.
kv/service/<name>/heartbeat — a service announces its version and healthkv/subject/device/<id>/sensor_data — a device reports a readingkv/device/<id>/ota_event — a firmware update changes statekv/result/diagnosis/<id> — reasoning publishes a resultLattice is the layer 1 rule that holds the others apart. Layers publish and subscribe; they don't call each other.
Copyright (c) 1998-2026 spw1.com and steven p williams All Rights Reserved