ZeqTraffic

Bridges, roads, utilities, lifecycle.

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

What it does

Traffic signal optimization and flow modeling. Zeqond-timed green wave synchronization, congestion prediction, accident probability scoring using R(t) vehicle density.

Signature

Request

POST /api/infra/traffic

Param	Type	Required	Default	Description
intersections	array	✓	—	[{ id, lat, lng, currentPhase, vehicleCount }]
optimizationGoal	string		"throughput"	'throughput', 'emissions', 'emergency-preempt'.

Response

{ signalTimings, greenWaveSpeed_kmh, congestionScore, accidentRisk, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "intersections": [],
  "optimizationGoal": "throughput"
}' \
  "https://api.zeq.dev/api/infra/traffic"

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