Vik's assistant: how a message travels
Workflows · Workflow 5 of 6
Last synced 2h ago
Not connected
The Worker (Cloudflare) holds every rule and is the only thing on the public internet. The AI runs on a separate 24/7 box that only makes outbound calls: a bridge polls the Worker and drives two OpenClaw agents. The Worker side is built and tested. The box side (bridge, plugin, prompts, gateway configs) is written and tested against fakes, but has never run on the real box (purple).
Built & testedWritten, tested with fakes, never run for realVik's call (Telegram bot)Decision
1 · A client message Front desk answers logistics; every action is a Worker tool.
2 · Handoff to Vik and back Health, complaints, sensitive or odd questions: Vik decides with one tap. Design and price questions stay with the assistant until the deposit is paid.
3 · Morning summary, paid requests and Vik's own commands
Safety: the front desk only has CozyInkz client tools, bound to one conversation by its session key (never by model arguments), and no shell, files, browser or web. Health answers never reach the box: Vik's assistant sees only each consent form's status and whether there are health flags. Vik's tools use a separate owner token. Vik picked Telegram (buttons never expire); his bot isn't made yet.
Wide diagram: scroll sideways, or pinch to zoom on a phone.