ZeqMilLogistics

Sensor fusion, trajectory, C2, threat modeling.

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

What it does

Military logistics optimization. Supply chain routing under contested conditions, ammunition expenditure forecasting, force sustainment modeling.

Signature

Request

POST /api/defense/logistics

Param	Type	Required	Default	Description
units	array	✓	—	[{ unitId, location, strength, supplies }]
supplyPoints	array	✓	—	[{ location, inventory }]
threatLevel	string		"medium"	'low', 'medium', 'high', 'contested'.

Response

{ supplyRoutes, sustainmentDays, criticalShortages, alternateRoutes, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "units": [],
  "supplyPoints": [],
  "threatLevel": "medium"
}' \
  "https://api.zeq.dev/api/defense/logistics"

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