ZeqRadar

Sensor fusion, trajectory, C2, threat modeling.

• Protocol ID — zeq-radar
• Category — Defense
• Endpoint — POST /api/defense/radar
• Auth — api-key
• Rate limit — 10/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Radar system modeling. Radar range equation, Doppler processing, clutter rejection, CFAR detection with HulyaPulse-timed pulse repetition interval optimization.

Signature

Request

POST /api/defense/radar

Param	Type	Required	Default	Description
radarParams	object	✓	—	{ peakPower_W, frequency_GHz, antennaGain_dBi, pulseWidth_us }
target	object	✓	—	{ rcs_m2, range_km, velocity_ms }
environment	object		—	{ clutter, jamming, weather }

Response

{ snr_dB, detectionProbability, dopplerShift_Hz, maxRange_km, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "radarParams": {},
  "target": {},
  "environment": {}
}' \
  "https://api.zeq.dev/api/defense/radar"

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