الانتقال إلى المحتوى الرئيسي

ZeqPulse SSE Stream

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

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

What it does​

Server-Sent Events stream ticking every 777ms (one Zeqond). Each event contains zeqond, phase, R_t, and timestamp.

Signature​

Request​

GET /api/zeq/pulse/stream

No parameters.

Response​

SSE stream: { zeqond, phase, R_t, pulseHz, timestamp } every 777ms

Runnable example​

curl -sS \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  "https://api.zeq.dev/api/zeq/pulse/stream"

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/stream in a language SDK so builders can call it in three lines.
  • Medium — publish a reference integration demonstrating ZeqPulse SSE Stream alongside a real workload, with pulse-aligned metrics.
  • Far — propose ZeqPulse SSE Stream as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers​

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.