Overview
Pre-built domain packages
A skill is a pre-built domain package: an Ontology (the typed world model — entity types, link types, and constraints) paired with a Skill (the capabilities Jax uses against that ontology). Load one and the entire application reconfigures — the toolbar, map layers, sidebar tabs, validations, and Jax's behavior all change to fit the domain. Load a different skill and you get a different application, with zero code changes.
Nexma is domain-agnostic by design. Nothing in the platform is hardwired to fiber, water, or any single vertical. The packages listed here are simply the first domains we have modeled end to end. Anything spatial and rule-governed can be expressed the same way.
How a skill reconfigures the app
A skill carries everything the platform needs to become domain-aware. When it loads, four things happen at once.
- The ontology populates the world model. Entity types, link types, and constraints define what kinds of things exist and what rules govern them. This is the typed contract every other surface reads from.
- The Skill binds Jax's capabilities. Design and optimization tasks, validators, and the system prompt are scoped to the active ontology, so Jax reasons in the domain's own terms.
- The UI redraws itself. Toolbar buttons, sidebar tabs, and map styling are generated from the ontology. A fiber project never shows a hydrant tool; a water project never renders a splitter.
- Everything stays consistent. All surfaces read and write the same world model, persisted in the Nexma DataStore. One write, and the map, tabs, and Jax all react.
Tip: An ontology defines the world; a Skill defines what Jax can do in it. A project binds one ontology and one or more skills. The ontology is fixed for the life of a project; skills are swappable.
Available skills
These are the packaged domains shipping today. Each page covers the ontology it models, what Jax can do, and the standards it enforces.
| Skill | Domain | What it models |
|---|---|---|
| FTTH | Fiber to the home | PON hierarchy from OLT to ONU, optical budgets, splice plans |
| Water distribution | Pressurized water networks | Treatment-to-meter flow, pressure zones, pump sizing |
| Electric distribution | Medium-voltage power | Substation-to-meter feeders, voltage drop, phase balance |
| Gas distribution | Natural-gas networks | Gate-to-meter flow, pressure staging, isolation segments |
| 5G wireless | Macro and small-cell radio | RF coverage, capacity, backhaul planning |
| Construction | Project management | Phases, activities, resources, schedules |
| Logistics | Routing and supply chain | Fleets, orders, routes, time windows |
| CRM and sales | Spatial customer ops | Accounts, territories, pipeline, field routing |
| Legal practice | Matters and deadlines | Cases, attorneys, time, jurisdictional calendars |
| Defense and military | C2 and mission planning | Units, sensors, coverage, engagement geometry |
| World simulation | Agents and physics | Agents, environments, forces, emergent behavior |
Working with skills
Most teams start by loading a built-in skill and using it as-is. From there the ontology is open and editable.
- Use it as-is for the standard domain — every package ships production-correct entities, links, and constants.
- Extend the ontology when your domain has a wrinkle the default does not cover. Add a property or a constraint and every view reacts immediately.
- Compose skills for hybrid work — a municipal project can bind both a fiber ontology and a street-lighting ontology under one workspace.
If your domain is not in the catalog, describe it in natural language and Jax will draft an ontology and a Skill for you to review, edit, and save.
Where to go next
- Skills concept — how a Skill binds Jax's capabilities to an ontology.
- The ontology — the typed world model in depth.
- Nexma DataStore — where every project's world model is persisted.
- Platform overview — how the pieces fit together.