[Architecture]
System topology, data flow, bindings, storage, and ADRs for the HOOX edge mesh.
This track covers how HOOX is structured as a multi-worker mesh on Cloudflare — not day-to-day trading setup (see End User) and not deploy runbooks (see DevOps).
Start here
| Page | What it covers |
|---|---|
| System Overview | Mesh layout, isolation, Smart Placement |
| Data Flow | Signal → execute → ledger → notify |
| Communication | Service bindings, queues, internal auth |
| Bindings | Wrangler binding contracts across workers |
| Storage | D1, KV, R2 roles and retention |
| Endpoints (context) | Routing architecture (canonical API list lives under API) |
| Design System | Shared UI / token conventions |
| ADRs | Architecture decision records |