Build
Reference tells you what exists. Build tells you how to ship with it.
Each chapter pairs a real Zeq app with the protocols, operators, and SDK calls behind it — so you can follow the path from "idea" to "phase-locked deployment."
Start here — the workflow every chapter assumes
The Zeq agent doesn't take a one-line prompt and burn 100 ZEQ on a build. The canonical loop — shared by the homepage wizard, the Pulse, and the CLI — is spec → plan → build. Read it first; every later chapter assumes the loop is in your head.
➤ Architect together: Spec → Plan → Build
Chapters
| Chapter | What you'll build |
|---|---|
| Quickstart | Compute your first KO42-wrapped result in 60 seconds |
| Physics Simulation | Wind tunnels, fluid dynamics, seismology, cosmology |
| Robotics & Controls | Orbital planners, robotics labs, traffic + vehicle dynamics |
| Life Sciences | Biomechanics, genomics, medical calc, pharma kinetics |
| Climate & Energy | Climate models, power grids, weather |
| Cryptography & Identity | HITE, mail, messaging, auth, vault, BYOK |
| AI · Signal · Quantum | Neural architect, quantum circuits, RL, signal classifier |
| Software to Hardware | Compress, game engine sync, blockchain, CLI, pulse, globe |
| Utility & Meta | Financial, materials, structural, ZSP cross-domain |
| SDKs | Language bindings — TS, Python, MCP |
How to read it
Each chapter is self-contained: a problem statement, the kernel equations that solve it, a runnable curl, and three integration patterns. Every computation carries KO42 (mandatory), HulyaPulse 1.287 Hz locking, and ≤0.1% numerical error.
Reference surfaces for cross-lookup: Protocols · Operators · API · Apps · SDKs · Ship
Papers: Zeq Paper · Zeq Framework
Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.