Delivering a use case

This is the end-to-end path from a business problem to a production system: model the world, give Jax capabilities, connect real data, design, optimize, review, and operate. Every stage maps to a concrete part of the platform.

Core concepts

A use case in Nexma is delivered the way software is delivered — incrementally, reproducibly, and with a full audit trail. You start by defining what your world is made of, you give the agent the capabilities to act on it, you wire in live data, and then you iterate with Jax until the plan is sound. Nothing is throwaway: each stage produces durable, version-controlled state in the Nexma DataStore.

1. Define the ontology

Start with the world model. Decide what entity types exist, how they relate, what properties they carry, and which constraints must always hold — splice ratios, voltage drop, pressure budgets, regulatory geometry. Author it on the ReactFlow canvas or describe it to Jax and let it draft the graph. A correct ontology is what keeps every later stage honest, because constraints are validated on every write.

See Ontology.

2. Load a skill

The ontology says what the world is; a Skill says what Jax can do with it. Bind one or more skills to the project to give Jax a prompt, tool bindings, validators, examples, and the UI surface for the domain. Skills compose, so you can start with one capability and add others as the use case grows.

See Skills overview.

3. Connect data via Nexma SyncEngine

A plan is only as good as its inputs. Use Nexma SyncEngine to bring real-world data into the project — addresses, parcels, existing assets, terrain, vendor systems. Feeds land in the DataStore and spatial ones render on the Globe automatically, so Jax can design against reality instead of assumptions.

See Nexma SyncEngine and live data.

4. Design with Jax

Now describe outcomes. Jax reads the project, plans the work, and writes results straight to the DataStore, streaming each step onto the Globe. Inspect what it produces, pin features as context, and ask it to refine — "move every closure that violates the new bend-radius rule," "what changes if cabinet capacity drops to 144 ports." You and Jax are editing the same artifacts.

See Jax overview and AgentEngine.

5. Optimize with Nexma MathEngine

Where the work is a hard tradeoff — routing, siting, scheduling, allocation — Jax dispatches to Nexma MathEngine. It picks a solver family (mixed-integer programming, vehicle routing, constraint programming, simulation, or heuristic search), formulates the problem from the DataStore, runs it in the browser or on the solver server, and explains the answer in plain language.

See Nexma MathEngine.

6. Branch and review

Before anything becomes operational truth, branch the DataStore to explore alternatives without disturbing main. Reviewers compare the branch against main the way they read a pull request — entities added, links rewired, constraints checked — and merge when approved. Main stays the operational truth; branches are where the team experiments.

See Spatial Branches.

7. Operate in the field and the office

A delivered use case keeps running. The same project drives day-to-day operations: office teams monitor and adjust on the web workspace, while field crews receive work orders, capture evidence, and report progress through the Nexma mobile app — reading and writing the same DataStore with no extra sync. Automations can watch for conditions and act on a schedule.

See Mobile overview, Field ops, and Automations.

Where to go next

• Choose a starting world model in Skills overview.
• Tailor the path to your role in Next steps by role.
• Understand the foundation in Architecture overview.
• Try it hands-on with the Quickstart.