[Workers]

Per-isolate profiles for every HOOX Cloudflare Worker — gateway, execution, data, agents, and UI.

Each page is an isolate profile: bindings, routes, secrets, and behavior for one worker in the mesh.

Worker sources live as git submodules under workers/ in hoox-sh/hoox. Each repository carries a GitHub description, package.json description, and a README with a shared Mesh interconnect section that links every sibling isolate.

Ingress & execution

WorkerRoleSource
hoox (Gateway)Public webhook ingress, WAF/auth, two-phase DO idempotency + rate-limit DO, notify chatId allowlist, queue/service dispatchhoox-worker
trade-workerExchange REST execution (Binance / Bybit / MEXC), queue concurrency, named D1 RPCs, test tradingtrade-worker
web3-wallet-workerOn-chain wallet identity (ethers.js); bridge toward DeFi settlementweb3-wallet-worker

Data & intelligence

WorkerRoleSource
d1-workerSQL proxy + named /rpc/list-* / insert RPCs, dashboard stats, settings KVd1-worker
agent-workerConfigurable cron (1–1440 min) risk, trailing stops, multi-provider AI, kill switchagent-worker
analytics-workerAnalytics Engine fan-in (trades, signals, latency, heartbeats)analytics-worker
report-workerBrowser Rendering PDFs → R2, telegram deliveryreport-worker

Tooling (outside core mesh auth)

WorkerRoleSource
pyne-workerPython PYNE edge evaluate — Pine Script™ /run, bar-close cron, R2 OHLCV, alerts (hoox pyne)pyne-worker

Channels & UI

WorkerRoleSource
telegram-workerAlerts, bot commands, outbound/inbound chat allowlists, RAGtelegram-worker
email-workerMailgun / email signal parsing → trade-workeremail-worker
dashboardNext.js ops console (OpenNext, public)monorepo workers/dashboard

Related

  • Architecture — mesh topology
  • Test Trading — sandbox fills across trade / agent / dashboard
  • Parent monorepo README — worker table with repository links