Maritime
Hydrodynamics, navigation, port logistics.
- Family — maritime
- Protocol count — 5
- Anchor — every call composes with
KO42+ up to three additional operators - Precision — ≤0.1% (HulyaPulse-synced)
Protocols
| ID | Name | Deploys as |
|---|---|---|
zeq-ballast | ZeqBallast | contract zeq-ballast |
zeq-cargo-optimize | ZeqCargoOptimize | contract zeq-cargo-optimize |
zeq-hull-stress | ZeqHullStress | contract zeq-hull-stress |
zeq-maritime-nav | ZeqMaritimeNav | contract zeq-maritime-nav |
zeq-port | ZeqPortOps | contract zeq-port |
Protocols are named formula bundles in the registry — they execute through the kernel, not through per-protocol routes.
Compose rule
Every protocol in this family composes registry operators — KO42 (the always-on time base) plus up to three more per call. Each transition fires its operator's closed-form solver; the result is phase-stamped to the Zeqond and returned with a ZeqProof. The verbatim equation the operator evaluated is recorded on the audit row as master_equation_block, so any result is re-derivable by hand.
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.