Glossary
Canonical terms
This glossary defines the canonical Nexma terms used across the documentation. When two words could describe the same thing, this page names the one Nexma uses. Refer back to it whenever a term is unfamiliar or you want the precise definition rather than the surrounding prose.
Platform and agent
| Term | Definition |
|---|---|
| Nexma | The AI-native spatial operating system — a horizontal platform where domain functionality is delivered through Skills, not hardcoded. |
| Jax | The spatial intelligence agent. You describe what you want in plain language; Jax reads and writes the world model, reasons against the Ontology, and runs the engines. |
| Primitive | One of the eight generic, scoped actions Jax acts through: Read, Write, Edit, Delete, Glob, Grep, Run, Solve. Never a domain-specific tool. |
| Skill | A domain package that reconfigures Jax and the world model for a vertical — fiber, water, electric, defense, logistics. Swappable per project. |
| Ontology | The typed world model for a domain: entity types, relationships, and constraints. Defines what exists and the rules it obeys. |
The world model
| Term | Definition |
|---|---|
| Nexma DataStore | The single source of truth — a real, persistent file system that holds the live world model and spatial data. Every surface reads and writes it. |
| Nexma DataBase | The time-series and tracking store that retains state over time, so the operational picture has continuity and history at scale. |
| Object Explorer | The instance browser, typed by the active Ontology — the table and graph view of every entity in a project. |
| Spatial Branch | A git-style branch of the world model. Work in isolation on a branch, then merge into Main, with full diff and review. |
| The Globe | The map surface. A renderer onto the DataStore — it shows the world model, it is not a separate copy of it. |
The engines
| Term | Definition |
|---|---|
| Nexma AgentEngine | Composes, schedules, and observes Jax in repeatable workflows. The orchestration layer for the agent. |
| Nexma MathEngine | The optimization engine. Formulates spatial goals and Ontology constraints into solvable problems and returns provably optimal, auditable plans. Reached through Solve. |
| Nexma GeoEngine | The spatial analysis engine — isochrones, buffers, overlays, proximity, routing. Reached through Run. |
| Nexma InsightEngine | The perception layer — computer vision over overhead imagery, full-motion video, and sensors. Detects, classifies, tracks, and grounds. |
| Nexma SatelliteEngine | Tasks fresh imagery over an area of interest for the InsightEngine to analyze. |
| Nexma SyncEngine | Connects external systems and feeds into the world model and keeps them current. |
| Event Broker | Routes platform events to webhooks and streams — job completion, detections, feed updates. |
Work and access
| Term | Definition |
|---|---|
| Project | A bound container of world model and data — one Ontology plus one or more Skills. The unit of work and of scope. |
| Session | A single Jax conversation within a project. The timeline records each action. |
| Automation | A scheduled or triggered workflow that runs Jax without a person in the loop, composed and observed through the AgentEngine. |
| Organization | The boundary for members, projects, Skills, and data. Everything belongs to an org, not a personal account. |
| Role | The permission set a member holds in an org — Viewer, Designer, Reviewer, Admin, or a configured equivalent. |
| Authority flag | A single permission checked on every operation: read, write, delete, run, solve, approve, share. |
| API key | A scoped token for programmatic access, bound to one organization. |