novox
Novox HQ — mission, research, decisions, design. The reasoning behind what we build.
Updated 2026-11-13 13:41:55 +00:00
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Updated 2026-11-13 13:40:34 +00:00
Novox Mesh — the catalogue. Module manifests the mesh builds, provisions and runs. Data, not a control-plane concern.
Updated 2026-11-13 13:40:29 +00:00
Novox Mesh — the tool runtime. Binds the mesh broker (AMQP) and serves the assigned modules' tools through the sdk harness.
Updated 2026-11-13 13:09:38 +00:00
Novox Mesh — networking: the route-proxy module, which serves the mesh's names and routes, moved out of the controller's repository (issue 1126).
Updated 2026-11-13 13:09:35 +00:00
Novox Mesh — tier 0. One statically linked binary that requires nothing present. Applies declared state on a machine; decides nothing.
Updated 2026-11-13 13:09:32 +00:00
Novox Mesh — contracts: every seat's definition (verbs, events, fixtures) and the Go and TypeScript packages generated from them (ADR 0613).
Updated 2026-11-13 13:08:50 +00:00
Novox Mesh — the stable spine a module's own code builds against. Tool harness, provisioner reconcile loop, broker/event contract, runtime contracts, sealing. Holds nothing per-module (ADR 0044).
Updated 2026-11-13 13:08:13 +00:00
Updated 2026-11-13 12:49:34 +00:00
Novox Mesh — tier 2. The controller: everything that needs to know about more than one node. Decides; never applies.
Updated 2026-11-02 20:42:06 +00:00
Novox Mesh — the lab. Scenario lifecycle, networking and placement. Ships to nobody; runs on a workstation.
Updated 2026-10-23 17:54:02 +00:00
Sample todo app in React
Updated 2020-06-26 15:51:11 +00:00