ZeqMaritimeNav

Hydrodynamics, navigation, port logistics.

• Protocol ID — zeq-maritime-nav
• Category — Maritime
• Endpoint — POST /api/maritime/nav
• Auth — api-key
• Rate limit — 15/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Ship navigation with HulyaPulse great-circle routing. Weather routing optimization, ECA compliance, current/wind set and drift compensation.

Signature

Request

POST /api/maritime/nav

Param	Type	Required	Default	Description
departure	object	✓	—	{ port, lat, lng, time }
destination	object	✓	—	{ port, lat, lng }
vesselType	string		—	'container', 'tanker', 'bulk', 'cruise'.

Response

{ route, distance_nm, eta, fuelConsumption_mt, ecaCompliant, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "departure": {},
  "destination": {},
  "vesselType": "<value>"
}' \
  "https://api.zeq.dev/api/maritime/nav"

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