Framework Parameters

Operators, constants, equations, experiments — the registry surface.

• Protocol ID — framework-params
• Category — Data
• Endpoint — GET /api/framework/params
• Auth — none
• Rate limit — 120/min
• Version — 1.287.6
• Precision — ≤0.1% (KO42-enforced)

What it does

Core framework tuning — pulse frequency, Zeqond duration, alpha, precision target, max operators.

Signature

Request

GET /api/framework/params

No parameters.

Response

{ pulse_frequency_hz, zeqond_s, alpha_modulation, precision_target, ko42_mandatory, ... }

Runnable example

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

Integrate

1. Introspection — list what the kernel can compute before authoring a wizard step.
2. Schema generation — feed returned operator definitions into typed bindings in any language.
3. Experiment catalog — wire the response into a UI selector for reproducible demos.

Seeds

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