How a request flows

This page follows one message through Zyx. The same path serves a typed message, a scheduled run, a trigger and a call from an outside AI tool.

The path

You: chat, phone, or AI tool
  │
  ▼
Workspace
  picks the cheapest model that fits,
  adds what this person may see
  │
  ▼
eve runtime: runs the model's loop
  │  the model calls a tool
  ▼
Kernel: decide()
  ├─ allow  → the tool runs
  ├─ refuse → the model is told why
  └─ hold   → approval card, turn waits
               │ a person approves
               ▼
             the same call runs once
  │
  ▼
Privacy gate on the result
  │
  ▼
Event log (Postgres)
  the answer, with its Sources

Step by step

1. The message arrives. It comes from the workspace, from the phone over a private network, or from an AI tool through Zyx’s MCP server, and acts as one known person. A schedule or a trigger acts as itself, with rights to its own folder only.
2. The model is chosen. Zyx picks the cheapest model that fits the work. A folder can cap which models and providers it may use and how much it may spend. See Models and cost.
3. Context is gathered. Zyx searches what this person may read and adds the best passages and the folder’s memory. See Readers and rights.
4. The model works. It runs inside eve, the one runtime. It may call tools: read a file, search, draft a mail, change a page in a connected app.
5. Every tool call is decided. Before any call runs, the kernel decides: allow, refuse, or hold for a person. See The kernel and approvals.
6. A held call waits without blocking anything. The card shows in the chat. No process waits. When a person approves, the same call runs exactly once and the same turn continues, even after a restart. A message sent past an open card, or Stop, withdraws the card and says why.
7. Results come back through the gate. Credentials in a result are blocked, personal data is redacted, and anything from outside is marked as data, not instructions.
8. Everything is written down. Each step lands in one event log in Postgres. The answer lists its Sources; a click opens the file, mail or page.

Bigger work: jobs

When a request needs several steps, Zyx proposes a plan on one card: the outcome, the steps and the checks. After approval it runs step by step, each step on the cheapest model that can do it, and every tool call still passes the kernel. See Skills and workflows.

Safety limits on a turn

• On the eve loop, the same tool call three times in one turn stops the turn. So does the step limit (100 steps unless the company sets its own).
• A folder’s spend cap and the company’s monthly cap stop new work when reached. The owner gets a notice and can raise the cap.
• A halt switch stops every agent and routine at once.