Operator Database Browser

Frontend app protocols — wizard, simulator, playground.

• Protocol ID — operator-database
• Category — Ecosystem
• Endpoint — GET /api/framework/registry
• Auth — none
• Rate limit — 120/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Paginated, searchable operator database combining generated (1,340+) and canonical (1,500+) operators.

Signature

Request

GET /api/framework/registry

Param	Type	Required	Default	Description
category	string		—	Category filter.
search	string		—	Full-text search.

Response

{ total, filtered, operators }

Runnable example

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

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

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