All platform features
Sparkplug B primary host
A conformant primary host, not MQTT with a schema bolted on — birth and death certificates, sequence tracking and rebirth.
QUBIQ publishes STATE, tracks the sequence number on every message, and requests a rebirth when it detects a gap. When an edge node disappears, its death certificate marks that node's metrics stale rather than leaving a number on a screen that stopped being true twenty minutes ago.
The implementation carries its own compliance test suite and a simulator probe, because "mostly works" is not a useful property for a state-management protocol.
What you get
- NBIRTH / DBIRTH schema announcement with aliases
- NDEATH / DDEATH marks metrics stale, not merely stopped
- Sequence-gap detection with automatic rebirth request
- Command writes back to edge nodes
- Compliance suite runs in CI