The workspace
Globe, panels, projects, sessions
The workspace is where you do the work — the project viewer where the Globe, the panels, the auto-generated tabs, and the Jax chat all meet. It is one reactive surface over a single source of truth.
Core concepts
Open a project and you land in its workspace. The center of gravity is the Globe; everything else arranges itself around it and reacts to the same state. The defining property of the workspace is that there is only one truth underneath it — the Nexma DataStore — and every panel is a renderer of that truth, not a separate copy.
The Globe
The Globe is Nexma's map-native canvas: a 3D-capable basemap with your project's layers on top. It inverts the usual pattern. Instead of a dashboard with a map panel buried inside it, the map is the primary surface and the dashboards slide in around it.
- Layers come from your project. Anything in the DataStore with geometry renders as a Globe layer automatically. Adding spatial content means writing it to the project.
- Click is read. Click any feature to see its full record. Right-click to pin it as Jax context.
- Edit is write. Drag a vertex and the record updates. Drop a polygon and a new selection is saved.
- 3D where it matters. Building extrusions, indoor models, and point clouds render inline; the basemap toggles between dark, light, and satellite.
See Nexma DataStore.
Side panels and auto-generated tabs
The workspace is not hardcoded to any domain. Its tabs and inspectors are generated from the active Ontology.
- Object tabs appear for each entity type in your ontology, grouped by tier, so a fiber project shows cabinets and closures while a logistics project shows depots and routes — with no code change.
- Inspectors show the full typed record for whatever you select, including the constraints that govern it.
- The Object Explorer browses instances as a table, typed by the active ontology, for when you want rows rather than a map.
See Object Explorer.
The Jax chat surface
The Jax panel is where you describe outcomes and watch them happen. Jax reads the same project everyone else sees, plans the work, runs it through the engines, and writes results straight to the DataStore. Because its output is the same kind of object you would create by hand, you can edit what Jax produces and Jax can build on what you draw.
See Jax overview.
Projects vs sessions
Two layers of context organize your work:
| Layer | What it holds | Lifetime |
|---|---|---|
| Project | One Ontology, its Skills, and all spatial state in the DataStore | Persistent — your business as code |
| Session | A single Jax conversation inside a project | A thread of work; many per project |
You can run several sessions against the same project. Switching to a different project opens a new tab, so two projects never share a workspace.
One write, everything reacts
This is the property that makes the workspace feel different. When Jax — or you — writes once to the DataStore, every surface responds in lockstep.
Move a transformer in the inspector, and the Globe layer redraws, the object tab updates its row, the constraint check re-runs, and the mobile app sees the change. You never reconcile views by hand, because there is only one view of one truth.
Where to go next
- Understand the truth underneath in Nexma DataStore.
- See how tabs are generated from the Ontology.
- Learn the container model in Projects and resources.
- Explore alternatives safely with Spatial Branches.
- Drive it all with Jax.