One identity, one hash-linked audit log, one encryption boundary. Sovereign, fault-isolated, folder-portable — copy it anywhere and it wakes with the same memory. Everything else in this store is a window onto it.
Zeq treats physical law as its instruction set — 1,606 named operators across 65 domains, on one 1.287 Hz clock, resolved to ≤0.1%. Every result is deterministic and proof-carrying. On top you build state machines you own, state contracts that automate with receipts, and channels — whole applications hosted on your machine. The apps below are what people built; you can build the next.
READ THE SDK & START BUILDING →{{ a.short }}
Same operators, same seven phases, byte-identical receipts in JavaScript, Python, Rust, Go and curl. The runtime is the API.
OPEN THE LADDER →curl -sX POST https://zeq.me/api/zeq/compute \
-d '{"operators":["KO42","NM23"],"inputs":{"m":5,"v":30}}'
// → 2250 J · zeqProof 07deea3f… · 7 steps OK
Every domain below runs the same machine — byte-for-byte identical. Because computation is deterministic, the same call returns the same bits on any of them, so no node is the “main” one and none can drift out of agreement. Any one of the fourteen is the whole framework; each simply opens on the facet its name describes — the clock, the observatory, the SDK, the ledger. Pick whichever door you like.
{{ s.blurb }}
{{ s.sdk }}
SELECT · BIND · VALIDATE · COMPUTE · VERIFY · PULSE · RETURN. Every call publishes all seven phases with status, duration and detail — then signs the envelope. Nothing is a black box, so you can teach it.
A state contract is named states plus transitions that fire operators on a condition or a schedule. Dry-run it at no cost, deploy it, version it, pause or freeze it — and every firing lands on the audit log with its own ZeqProof. Intent becomes computation, and compliance falls out of the receipts.
AUTHOR A CONTRACT →{{ a.short }}
{{ e.short }}
A state machine is a per-user computer: its own key pair, its own audit log, its own tick. Two keys separate powers — a machine key authorises compute, an owner key authorises administration. Copy the folder anywhere and it wakes with the same memory. Everything below docks onto it instead of a vendor’s server.
MINT YOURS →{{ a.short }}
Hand over a proof digest and anyone can verify the whole path from genesis — without trusting you, without trusting the framework, without re-running the compute.
zeq verify 07deea3f…
// → verified · 7 steps OK · τ 2,297,725,582
100 questions from classical mechanics to quantum gravity — each answered by composing real operators through the seven-step wizard. Every level mints a state contract.
PLAY PHYSICS WIZARD →A channel is a whole application hosted on a machine: front end, optional back end, files — served publicly under a strict sandbox. Code inside a channel computes key-free, because the node fills in your machine’s identity at the boundary. Author in Studio, scaffold in Workbench, publish versioned.
OPEN STUDIO →{{ a.short }}
100 questions from classical mechanics to quantum gravity, each answered by composing real operators through the seven-step wizard. Nothing is marked from an answer key: the engine computes every answer live, so you cannot bluff it — and every level you clear mints contract state on your machine. The most enjoyable way to learn what the framework actually is.
PLAY THE WIZARD →{{ a.short }}
ZLM is ours: a language model bound to the kernel, not a wrapper around someone else’s. Ask in plain English and the reply is a computed, signed number — the operator calls are inspectable behind every sentence. The model proposes; the machine computes; nothing hallucinated survives contact with the pipeline.
TALK TO ZLM →{{ a.short }}
One engine evaluates 1,606 named operators across 65 domains through SELECT, BIND, VALIDATE, COMPUTE, VERIFY, PULSE, RETURN. A formula is data the machine reduces, never code it runs — which is why the same call returns the same bits on every node, and every result carries a signed envelope anyone can re-verify offline.
HOW A NUMBER IS MADE →A real-time Earth monitor on the 1.287 Hz clock: seismic events, weather patterns and global telemetry, every reading stamped to the zeqond it arrived at. One shared tick is what lets two sensors on different continents claim the same moment — and what makes precursor patterns comparable at all.
OPEN THE EARTH MONITOR →{{ a.short }}
Zeq is a physics virtual machine. Physical law is the instruction set: you name operators and it computes them for real, on one clock, and every result comes back with a proof anyone can re-check.
Apps you open and use. Machine surfaces that run your own machine. SDK documentation, which explains and is not an app. Nodes, the domains the framework runs on. Every card says which it is, under its name.
Everything is stamped to 1.287 Hz. One tick is a zeqond: exactly 777,000,777 nanoseconds. That shared tick is what lets two machines agree that they ran the same computation.
{{ g.lesson }}
{{ g.fact }}
{{ a.short }}
Work the ladder top to bottom. Each rung links to the surfaces that use it, so you read the call, run it, then watch the transition land in the Observer.
zeq state —
Each row is one computation this machine ran. Name is what it was for; operators are the equations it composed, KO42 always first; τ is the Zeqond it ran at — one tick of the 1.287 Hz HulyaPulse, 0.777000777 s; the digest is its ZeqProof, which anyone can re-verify offline. Idle ticks are not shown — a tick is the kernel’s heartbeat, not something the machine did.
{{ a.short }}
This is what your machine reports about itself right now — identity, anchor, credits, plan and envelopes, read live from the machine. Each row opens the surface that governs it.
{{ detailBlurb }}
{{ detailWhat }}
{{ detailHow }}
{{ detailWhy }}
{{ detailRev }}
{{ detailDeep }}
{{ detailSdk }}