ZeqSevereWeather

Forecasting, radar, nowcasting, severe events.

• Protocol ID — zeq-severe-weather
• Category — Weather
• Endpoint — POST /api/weather/severe
• Auth — api-key
• Rate limit — 20/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Severe weather detection and alerting. Tornado vortex signatures, hail probability, lightning prediction using R(t) convective instability indices (CAPE/CIN).

Signature

Request

POST /api/weather/severe

Param	Type	Required	Default	Description
radarData	object		—	Reflectivity/velocity data from weather radar.
location	object	✓	—	{ lat, lng, radius_km }.
alertTypes	array		—	['tornado', 'hail', 'lightning', 'flood', 'wind'].

Response

{ alerts, tornadoProbability, cape_J_kg, cin_J_kg, hailSize_cm, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "radarData": {},
  "location": {},
  "alertTypes": []
}' \
  "https://api.zeq.dev/api/weather/severe"

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/weather/severe in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqSevereWeather alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqSevereWeather 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.