ZTB1 Timebase Bridge

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

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

What it does

Bidirectional Unix ↔ Zeqond time conversion. Lossless mapping between standard epoch time and HulyaPulse computational time.

Signature

Request

POST /api/zeq/timebridge

Param	Type	Required	Default	Description
timestamp	number	✓	—	Unix timestamp (seconds) or Zeqond count.
from	string		"unix"	'unix' or 'zeqond'. Default: 'unix'.

Response

{ unix, zeqond, phase, phaseRadians, R_t, direction }

Runnable example

curl -sS -X POST \
  -H "Content-Type: application/json" \
  -d '{
  "timestamp": 0,
  "from": "unix"
}' \
  "https://api.zeq.dev/api/zeq/timebridge"

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