Documentation / Productivity

OMNI

The intent-driven do engine for the entire Ocalt ecosystem. Say what you want done. OMNI executes it.

Open OMNI

Overview

OMNI is a single surface where you state what you want done. It turns natural-language intent into executed actions across every part of the Ocalt platform — tasks, workflows, files, databases, infrastructure, email, storage and more.

It is not another task list or another dashboard. It is the layer that takes a goal and makes the rest of the ecosystem carry it out.

What it is

A multidomain *get it done* product. You describe the outcome. OMNI maps the intent onto the underlying Ocalt services — OcaltQL, ClockWork, Fabric, Ocaltio, Email and the rest — executes the necessary operations, and returns the result.

The gap between an assistant and an agent is whether the output does anything. OMNI's output does. There is no orchestration product in between for the model to get wrong; the language is the orchestration.

What it does

  • Accepts plain-language goals and breaks them into the steps required.
  • Coordinates the correct Ocalt services to complete the work.
  • Surfaces progress, results and any remaining decisions in one place so you never have to leave the surface to finish the job.
  • Stays inside your namespace. It can only touch /root, /mounted, and machines you have registered.
  • Shows you the script when you want to keep it, schedule it, or hand it to a colleague.

How it works

OMNI is an orchestration layer on top of the stack, not a second runtime. The work it does is OcaltQL. If you can read the language, you can read what it did. If you cannot, you can still confirm the result and ask for the next change.

A model that can call twenty APIs has to be taught twenty schemas. A model that can write OcaltQL has to be taught one grammar. That is why OMNI can move a file, restart a machine, draft an invoice and draw a chart of the result in one pass.

Getting started

  1. Open omni.ocalt.com signed in.
  2. State something small and checkable: create a database, write a file, list machines.
  3. Read back what ran. Keep the script if it is a job you will want again.
  4. Widen the intent: “remind every open invoice”, “restart nginx on edge-01 if the inbox says site down”.

If you would rather drive the model yourself, give it the grammar at ql.ocalt.com and an API key from accounts.ocalt.com, then POST to https://ql.ocalt.com/api. OMNI is that loop with a product around it.

What a good intent looks like

  • Outcomes, not tool names. “Raise a PO for anything under 10 units” beats “open ClockWork inventory”.
  • A namespace that already has the data. OMNI cannot invent your supplier's email.
  • A bound. “On greenhouse only” is safer than “on every machine”.
  • A way to tell you. End the thought with who should know.
A worked shape
Watch the support mailbox.
If a subject contains "site down", restart nginx on edge-01
and notify me with the exit code.
Do not touch any other machine.

Who it is for

Anyone who wants real work done across the Ocalt ecosystem without becoming an expert in every individual product. Operators who already know the language and want a faster first draft. Teams that want a shared surface rather than a shared pile of scripts in chat.

OcaltQLWhat OMNI actually runs.OcaltQL ConsoleEdit the script OMNI produced.ClockWorkBusiness data OMNI can act on.FabricMachines OMNI can address.

FAQ

Does OMNI run without my confirmation?

Treat it like a console you typed into. If you asked it to drop a table, it will. Start with read-only intents until you trust the loop. Use a dedicated account for an always-on agent.

Is this a chatbot with plugins?

No. Plugins would be twenty schemas. OMNI speaks one language that already covers files, mail, machines, databases, media and HTTP.