Field notes

AI engineering · July 22, 2026 · 4 min read

AI operators that take real actions

Most AI features stop at generating text. The useful ones execute bounded, validated actions. Here's the pattern we use to let agents change real data safely.

A chatbot that tells you what to do still leaves you doing the work. The jump from novelty to utility happens when the model can take an action — and the engineering challenge is making that action safe, typed, and reversible.

Tool calls over free text

In our agentic work OS, the model doesn't emit prose that a human re-enters. It emits a typed tool call — create_tasks, update_tasks, schedule_huddle — that the server validates against the schema before touching Postgres. The board updates live, but nothing runs that the server hasn't checked.

This inverts the usual flow. Instead of the AI describing an outcome, it proposes a structured operation, and the backend decides whether that operation is allowed.

Bounded by design

Every operator has a fixed set of tools. It cannot invent new capabilities at runtime. Context — the current board state — is injected each turn so the model acts on reality, not a stale snapshot. Destructive or ambiguous actions pass through a confirmation step.

The result is an agent that feels capable without being unpredictable. That balance is the whole product.

AI operators that take real actions — Kruzeniski Studio · Kruzeniski.ai