Ocalt for AI
Train your AI on OcaltQL and give it real agency. Let it spawn servers on demand, track and control your devices, read your emails and trigger actions halfway across the world when it finds a specific phrase, or automatically adjust hardware the moment the weather turns hot. Have it pull live maps and geolocation data, plot routes, watch for movement in a specific area, or react the second someone enters a geofence. One language, full system access — so your AI doesn't just talk about doing things, it actually does them.
One language is the whole point
A model that can call twenty APIs has to be taught twenty schemas, twenty auth models and twenty failure modes — and it will get one of them wrong. A model that can write OcaltQL has to be taught one grammar.
Reading an inbox, moving a file across a continent, restarting a machine and drawing a chart of the result are the same language, in one script, executed in one request. There is no orchestration layer between the model's intent and the thing happening.
Agency, not suggestions
The gap between an assistant and an agent is whether the output does anything. OcaltQL output does. A model emits a script; the script runs; the machine reboots, the invoice files itself, the gate opens.
That is a different proposition from a model that produces a plan for a human to execute. It is also a different risk profile, which is why the next section matters as much as this one.
Bounded by design
Every script runs inside one namespace. A model can only read and write that account's /root and /mounted, and can only address machines that account has registered. It cannot see the host, other customers, or anything above its own root.
The blast radius of a hallucinated script is the account that wrote it. That containment is what makes handing a model real execution reasonable rather than reckless.
What it looks like
A model watching an inbox, acting on what arrives, and telling a machine on the other side of the world about it — one script, no glue.
NEW EMAIL IMAP connects and captures the mailbox. EMAIL SEARCH finds what matters. DIRECTIVE EXEC restarts the service on a machine behind a home router with no static IP. NOTIFICATION reports back. Four verbs, one execution, one charge.
Where to start
Give a model the OcaltQL documentation as context and let it write. Every plan including Free has the entire language — the constraint is queries per day, not capability.