Skip to main content

Protocol Registry

Zeq OS ships 235 protocols spanning quantum, classical, relativistic, applied, engineering, and signal-processing domains. Each is a named formula with a canonical operator composition and a worked example.

The protocol pages in this section are generated from the registry source at app/artifacts/api-server/src/lib/protocols.ts. The generator is run as part of npm run build.

How protocols work​

Every protocol is:

  • An ID — e.g. zeq-propagation, zeq-formulation, zeq-master-equation.
  • A formula — a closed-form expression in the framework's notation.
  • An operator composition — 1 to 3 operators plus KO42, from the 42+ spectrum.
  • A parameter schema — required and optional inputs with units.
  • A worked example — inputs and expected outputs.

When you call zeq.compute({domain: "quantum_mechanics", inputs: {...}}) without specifying a protocol, the SDK picks the closest match from the registry and executes it.

When you call zeq.run("zeq-propagation", {...}) you are asking for that specific protocol by ID.

Categories​

  • Quantum mechanics protocols
  • Classical mechanics protocols
  • General relativity protocols
  • Electromagnetic & signal protocols
  • Applied science — medical, genomics, pharma, forensic, cosmic
  • Engineering — structural, seismic, fluid, thermal, aero, orbital
  • Zeq-native — zeq-tether, zeq-pocket, zeq-protect, zeq00, zeq000
  • Awareness / self-referential — ON0, QL1, TM1, TX, XI1, LZ1, CHI95, PSI96, MK1, VX
  • Meta-protocols — framework-params, operators-list, canonical-registry, wizard-run

Excluded categories​

Five protocols are in the registry but omitted from the public docs: ballistic, electronic warfare, mil-crypto, mil-logistics, and ballistic-forensics. Zeq is a harmonic-frequency platform; weapons framings are out of scope.

Browsing​

Use the sidebar to navigate the full registry, or search via the docs search bar.