ZeqSCADA — Secure Industrial Control

Device sync, SCADA, metering, fault detection.

• Protocol ID — zeq-scada
• Category — IoT
• Endpoint — POST /api/iot/scada/command
• Auth — api-key
• Rate limit — 60/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Secure industrial control using TESC ephemeral channels. Every command encrypted with a PLAT valid for one Zeqond (0.777s) — replay attacks physically impossible.

Signature

Request

POST /api/iot/scada/command

Param	Type	Required	Default	Description
controllerId	string	✓	—	SCADA controller identifier.
command	object	✓	—	Control command payload.
priority	string		"normal"	'normal', 'high', 'emergency'. Default: 'normal'.

Response

{ commandId, encrypted, plat, zeqondSent, acknowledged, latencyMs }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "controllerId": "<value>",
  "command": {},
  "priority": "normal"
}' \
  "https://api.zeq.dev/api/iot/scada/command"

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

• Near — wrap /api/iot/scada/command in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqSCADA — Secure Industrial Control alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqSCADA — Secure Industrial Control as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

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.