Nexma AgentEngine
Orchestrate agentic spatial workflows
Nexma AgentEngine is the AI operating system Jax runs on. It turns one-off prompts into a governable workforce: compose Jax into reusable spatial workflows, schedule and trigger them, and observe every step end-to-end. Agents design, analyze, and operate physical infrastructure — every action grounded in the world model and fully auditable.
Core concepts
Most spatial automation is a pile of brittle scripts with no awareness of the world they act on and no record of what they did. AgentEngine replaces that with multi-step agent plans that reason against the Ontology, act through scoped primitives, and leave a complete trail.
- Compose. Chain Jax steps — design, analyze, optimize, dispatch — into reusable workflows that run the same way every time, across any domain.
- Orchestrate. Launch workflows on a schedule, on a data change, or on a live event from the Event Broker, so the world model stays current without anyone watching it.
- Observe. Every tool call, read, and write is streamed and logged. Inspect a run live or replay it after the fact, with full context behind each decision.
- Govern. Agents act only through the eight primitives, run in scoped isolation, and can be gated by human approval. Every action is logged and reversible.
A workflow built for one domain ports to another by swapping the Ontology. The steps are generic; the meaning comes from the world model.
How it works
A workflow is an ordered set of Jax operations against the DataStore. Each step is one of the eight primitives, with inputs, a timeout, and a permission scope. The engine runs the plan, streams every action, and records the result.
1Workflow: nightly-network-validate
2 trigger on schedule — 02:00 daily
3 scope project · branch:main · role:validator (read + solve)
4 steps
5 1. Glob designs/**/*.json → every active design
6 2. Read constraints from Ontology → the rules to check
7 3. Solve re-validate each design → violations, if any
8 4. Write reports/validation.json → the run record
9 on-failure retry x2 → escalate to #ops → no partial commitThe plan is declarative and versioned alongside the world model it acts on. Multi-step runs are repeatable, not chaotic, because context passes cleanly between steps and concurrent workflows operate in isolated scopes.
Build, orchestrate, observe, govern
| Stage | What you get |
|---|---|
| Build | Multi-step plans from reusable blocks, domain-agnostic steps, proven templates for design, analysis, and operations |
| Orchestrate | Schedules and triggers, deterministic handoff between steps and agents, per-run isolation |
| Observe | Live run view, full run history to replay any past run, metrics and alerts on throughput, success, and cost |
| Govern | Scoped tooling bounded by permissions, automatic audit trail, human-in-the-loop approval gates |
Multi-agent fleets
A single unmonitored loop does not scale to real infrastructure. AgentEngine runs fleets of agents across projects and organizations with deterministic handoff, isolation, and governance. One agent can hand context to the next, a workflow can fan out across regions, and the whole fleet stays observable and accountable.
This is what makes it safe to let agents act on the live world: scoped tools, isolation, approval gates, and a complete record of who did what, when, and why.
Multi-step plans and tool use
Inside a run, Jax decides which primitive to use at each step — Read to load state, Run for deterministic geo-math, Solve to call the MathEngine, Write to commit a result. The engine does not hardcode the plan; it gives Jax the controls and records the choices. When a step needs optimization, perception, or fresh imagery, the relevant engine is invoked and its result flows back into the same world model.
Insert an approval gate before any step that commits a change to the live world, so a person signs off before an agent writes.
Where to go next
- Automations — the scheduled and event-driven workflows AgentEngine runs.
- Jax — the agent the engine orchestrates.
- The eight primitives — the one safe tool surface every step uses.
- Event Broker — the live signals that trigger workflows.