IoT
Device sync, SCADA, metering, fault detection.
- Family — iot
- Protocol count — 5
- Anchor — every call composes with
KO42+ up to three additional operators - Precision — ≤0.1% (HulyaPulse-synced)
Protocols
| ID | Name | Deploys as |
|---|---|---|
zeq-iot-fleet | ZeqFleet — Device Fleet Management | contract zeq-iot-fleet |
zeq-iot-sync | ZeqIoT — Device Synchronization | contract zeq-iot-sync |
zeq-meter | ZeqMeter — Smart Metering | contract zeq-meter |
zeq-scada | ZeqSCADA — Secure Industrial Control | contract zeq-scada |
zeq-sensor-fusion | ZeqFusion — Sensor Fusion | contract zeq-sensor-fusion |
Protocols are named formula bundles in the registry — they execute through the kernel, not through per-protocol routes.
Compose rule
Every protocol in this family composes registry operators — KO42 (the always-on time base) plus up to three more per call. Each transition fires its operator's closed-form solver; the result is phase-stamped to the Zeqond and returned with a ZeqProof. The verbatim equation the operator evaluated is recorded on the audit row as master_equation_block, so any result is re-derivable by hand.
Papers
- Zeq paper — https://doi.org/10.5281/zenodo.18158152
- Framework paper — https://doi.org/10.5281/zenodo.15825138
Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.