ZeqRoute — Phase-Aware Routing

Zeqond-grid transport, mesh, routing, DNS.

• Protocol ID — zeq-route
• Category — Network
• Endpoint — POST /api/network/route
• Auth — api-key
• Rate limit — 60/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Shortest path weighted by HulyaPulse phase coherence. Nodes that are phase-aligned get priority — naturally selects the most synchronized route through the network.

Signature

Request

POST /api/network/route

Param	Type	Required	Default	Description
source	string	✓	—	Source node ID or address.
destination	string	✓	—	Destination node ID or address.
hops	number		8	Max hops allowed (1–32). Default: 8.

Response

{ route: [{ nodeId, phase, latencyMs, coherenceScore }], totalHops, pathCoherence }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "source": "<value>",
  "destination": "<value>",
  "hops": 8
}' \
  "https://api.zeq.dev/api/network/route"

Integrate

1. Mesh health probe — tick against this endpoint each Zeqond and alarm on missing edges.
2. Routing seed — inject the returned topology into a BGP/QUIC shim for pulse-aware routing.
3. DNS drift — detect stale propagation by comparing pulse-stamps across resolvers.

Seeds

• Near — wrap /api/network/route in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqRoute — Phase-Aware Routing alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqRoute — Phase-Aware Routing 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.