ZeqPulse

The heartbeat lane. HulyaPulse, Zeqond, timebase bridge — every protocol anchors here.

• Protocol ID — zeq-pulse
• Category — Core
• Endpoint — GET /api/zeq/pulse
• Auth — none
• Rate limit — 60/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Real-time HulyaPulse state — zeqond count, phase [0,1), R(t), field strength. The heartbeat of the framework.

Signature

Request

GET /api/zeq/pulse

No parameters.

Response

{ zeqond, phase, R_t, fieldStrength, timeToNextZeqond, pulseHz, zeqondSec, alpha, precision, timestamp, modulation }

Runnable example

curl -sS \
  "https://api.zeq.dev/api/zeq/pulse"

Integrate

1. Heartbeat monitor — poll this protocol every Zeqond (0.777s) from any service to keep workers pulse-coherent.
2. Workflow anchor — seed every compute call with the current zeqond from /api/zeq/pulse so downstream results align on the same phase.
3. Clock drift detector — compare returned phase against local estimate; deviation > 0.001 flags clock skew.

Seeds

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