Changelog

What ships:

• Branch from any commit. Switch the active branch from the workspace selector or

via /branches.

• Commit Codex state on demand or on a schedule. Commits carry author and message.
• Spatial diff overlay — added, modified, and removed features render side-by-side

on the Globe with a toggle.

• Merge with Jax-mediated conflict review. Each conflicting hunk is presented for

accept, reject, or rewrite.

• Blame at the feature level. Click any feature for its last-modifier and the

commit that touched it.

• Time-travel. Check out any prior commit as a read-only view for design review or

audit.

Terminology mirrors Palantir Foundry's Global Branching for enterprise familiarity: "branches", "Main", "merge".

Cinematic mode:

• Scripted camera path with timed reveals. Useful for stakeholder walkthroughs and

recorded design briefs.

• Per-step narration card with auto-advance or manual control.
• One-click capture to MP4 or animated GIF.

Vertex inspection:

• Hover any vertex on the Globe to see coordinates, elevation, and the source

feature.

• Click to lock the inspector and pull up the full property tree.
• Trace upstream and downstream dependencies — what created this vertex, what

consumes it.

An investigation is a Codex-resident object with:

• A subject (the anomalous feature or feed).
• A timeline of related events automatically pulled from the Codex history.
• A working chat with Jax, scoped to the investigation.
• A finding — the resolved root cause and the corrective action taken.

Closed investigations stay queryable. Patterns surface across investigations to inform future automations.

Coverage:

• Fetch. OpenStreetMap, SRTM/DEM, Sentinel and Landsat imagery, US Census

TIGER, regional administrative boundaries, NLCD landcover, NOAA weather.

• Trace. Network tracing (upstream, downstream, isolation), service-area

isolation, watershed delineation.

• Project. Reproject between common CRSes; project to a local UTM zone

inferred from the active polygon.

• Index. R-tree, H3 hex grid, S2 cells.
• Geoprocess. Buffer, dissolve, clip, union, intersect, difference,

centroid, simplify, and 22 more verbs.

Solver-family coverage now reaches 5 families × 5 problem types — see Solvers.

Navigator:

• Tree view of the active workspace.
• Click to switch projects in the same tab; cross-project switches open a new tab

to preserve your session context.

• Drag to reorder; right-click for project actions.

Building inspector:

• Click any building footprint to pin it.
• Inspector shows OSM tags, address resolution, and any Codex features anchored

to the building.

• Inline street-level imagery when available.

The pattern:

• A dashboard is dashboards/{name}.json.
• A layer style is styles/{layer}.json.
• An export is exports/{name}.json declaring format, projection, and field

selection.

Jax composes these from natural-language requests. Edits to the JSON re-render the view. Exports run on demand or on a schedule via Automations.

Engine:

• Roles map to authority sets — read, write, delete, run, solve, approve, share.
• Shadow mode logs decisions without enforcing, for safe rollout of new rules.
• Approval queues for sensitive operations (baseline promotion, share, delete).
• Audit log captures every decision with actor, target, and rationale.

Subagents inherit the deny set of their parent — an agent cannot acquire authority the user does not have. See Permissions.

What changed:

• Project gate — a unified entry that resolves URL, last-active session, and

permission scope before mounting the workspace.

• Switcher pinned to the top bar; supports keyboard navigation.
• SSE-based real-time sync — when a teammate writes to the project Codex, your

view updates within a frame.

• Codex history writes accept full snapshots, not just deltas, for compatibility

with the Branches workflow.

Drone feed:

• Position, altitude, heading, speed, payload, battery — every 1s while airborne.
• Renders on the Globe as a 3D drone model with a flight-path trail.
• Pin a drone in Jax chat to ask "why did this drone divert?" with full context.

Automation engine:

• Triggers on feed events (threshold cross, geofence enter/exit), Codex changes,

and cron.

• Each automation is automations/{name}.json — see

Automations.

Alert panels:

• Configurable severity bands with desktop, email, and webhook channels.
• Acknowledgement and resolution tracked in the Codex audit stream.

Workflow:

• Ask Jax: "Build a 6-slide deck for tomorrow's review of the Riverside FTTH

design. Highlight the budget delta versus baseline."

• Jax composes a draft and renders it inline.
• Edit slides directly or refine in chat.
• Present in full-screen with a presenter notes pane and a narration track.

Decks live at presentations/{name}.json in the Codex. Re-running the source design re-renders the deck.

What ships:

• 3D crew models on the Globe, scaled by vehicle class.
• Per-crew popup with the active work order, ETA, and last-known signal strength.
• Task list view with filter by crew, district, or work-order class.
• One-click "ask Jax about this crew" to surface the full operational context.

The same Codex stream powers desktop visualization and mobile field execution — see Mobile.

Indoor model:

• Three Codex layers — structure (walls, floors), equipment (racks, panels,

sensors), routes (cables, escape paths).

• Custom 3D layer with fill-extrusion. Inside an active building polygon, the

basemap drops to 2D to avoid z-fighting.

• Floorplans imported from PDF, DWG, or generated from a brief.

Engineering diagrams:

• Splice diagrams (closure-by-closure tray layouts).
• Riser diagrams (floor-by-floor cable runs).
• Annotated 2D floorplan diagrams with callouts.

See Indoor 3D modeling for the full model.

Feed catalog highlights (sample of 60+):

• Weather, lightning, wind, ocean currents, river gauges, air quality, UV.
• Flights, ships, trains, bus fleets, fleet vehicles.
• Earthquakes, tsunamis, cyclones, volcanoes, floods, active wildfires.
• Threat scanner, network intel, exposure scanner, abuse intelligence.
• Sanctions, court records, ad library, public procurement.
• Deforestation, emissions, sea ice, glacial retreat.

Architecture:

• Scheduled worker fetches each feed on its native cadence.
• Cached payloads served to browsers — zero external API calls per request.

See The data strip.

Earthquake feed:

• USGS real-time stream as a Codex feed.
• Magnitude-scaled markers with depth-aware coloring.
• Temporal slider for retrospective review.

Viz engine:

• Single configuration drives chart type, axes, color, and overlays for any

feed.

• Adding a feed requires no per-feed UI code — feed-chart-mapping.ts entry only.
• Charts respond to the same temporal slider as the spatial layers.

Connectors:

• Salesforce credentials persist per workspace; OAuth refresh handled

transparently.

• HubSpot adapter with the same shape — accounts, contacts, deals, activities.
• Account geocoding fills missing coordinates against the configured provider.
• Territory polygons sync into the CRM skill.

Automations canvas:

• Visual editor for Automations.
• Drag triggers and steps; the canvas writes to automations/{name}.json.
• Editing the JSON updates the canvas.

The schema:

• Account, Contact, Lead, Opportunity, Deal, Activity, Campaign, Quote.
• Territory polygons as first-class features with owner and pipeline-value

attributes.

• Pipeline as a flow overlay between stages.

Jax does:

• Territory design balancing account count, value, and drive time.
• Account routing under day-length and activity-mix constraints.
• Pipeline forecasting with stage-weighted roll-up.

See CRM & sales.

Highlights this month:

• Water skill: pressurized network design with elevation-aware pump sizing.
• Electric skill: 15kV feeder loops, branch-fuse placement, voltage-drop validation.
• Cross-skill projects: a single project can now hold both fiber and lighting in one

municipal workspace.

• New solver: simulation-based pressure-drop check across a full distribution graph.

Scopes:

• Organization. Shared across every user in the workspace.
• User. Specific to one user across every project.
• Project. Stored in the project Codex; visible to anyone with project read

access.

• Session. Ephemeral to one Jax conversation.

The recall indicator on the input bar shows which memories were retrieved before generation. Click to inspect, edit, or pin.

The model:

• Workspace. The home (/data-strip) — feeds, automations, organization

context.

• Project. A Codex container with branches, designs, runs, and members.
• Session. A single Jax conversation, scoped to a project.

URL semantics:

• /projects/:id selects the project and the most recent session.
• /projects/:id/sessions/:sessionId selects a specific session.
• Switching projects in the same tab swaps Codex and Jax context. Switching from

one project's session to another opens a new tab so neither conversation loses state.

What changed under the hood:

• Codex storage moved to a transactional, durable backend.
• Eight generic primitives — Read, Write, Edit, Delete, Glob, Grep,

Run, Solve — replace dozens of domain-specific tools.

• Domain knowledge moves to the system prompt; tool surface stays generic.
• Every write is versioned for Branches and

time-travel.

For the engineering rationale, see The Codex.

What changed for users:

• Designs and feeds persist across sessions and team members. No more reload-to-reset.
• Full project history with point-in-time replay, useful for design reviews and audits.
• Jax and humans now operate on the same project artifacts — no separate AI workspace.

Migration: existing projects were transparently rehydrated. No action required.

Service:

• All five families behind one authenticated endpoint.
• Identical request and response shapes across families.
• Stateless; horizontal scaling.

Browser fallback:

• Lightweight MIP for problems under a few hundred variables.
• Custom heuristics for graph problems.
• In-browser VRP for small fleets.

The dispatcher chooses location automatically. See Solvers.

Voice:

• Push-to-talk with on-device transcription where supported; falls back to

cloud STT when offline transcription is unavailable.

• TTS reply in the device locale, configurable speed.
• Voice barge-in — speak again to interrupt the response.

i18n:

• EN, HE, AR ship in the box.
• Full RTL layout, mirrored icons, locale-aware date and number formatting.

Built for crews running real deployments:

• Offline-first sync across spotty connectivity.
• Dual-camera capture with auto-tagged location and orientation.
• Live crew positions render on the desktop Globe — same project, same source of truth.
• Voice-driven Jax field assistant for hands-free task execution.

iOS is in beta with a small set of partners.

Initial catalog:

• Flights (ADS-B Exchange).
• Ships (AIS).
• Weather (NOAA).
• Earthquakes (USGS).
• Lightning (Blitzortung).

Architecture decisions made now and still in effect:

• Feeds write to Codex, not to memory.
• Reactive layer renders any GeoJSON feed automatically.
• Right-click on any entity pins it to Jax chat as spatial context.

The protocol:

1. Solver returns a candidate result.
2. Validation runs every active constraint from the agent skill.
3. Violations are re-encoded as additional constraints; the problem is re-solved.
4. After a small number of attempts without convergence, Jax stops and surfaces

the unresolved constraints with an explanation.

This is the difference between "the solver returned a number" and "the design is correct." See Solvers.

The big release: Jax stops asking for hand-holding. Give it a polygon, a goal, and a project, and it returns a finished, validated design — not a draft that needs an engineer to clean up.

What works now:

• End-to-end design generation across every shipped skill.
• Automatic validation against the rules of your domain.
• Self-correction when constraints are violated — no silent failures.
• Plain-language explanations for every non-trivial decision.

Capability:

• Up to N parallel web searches per question, with results merged and deduped.
• Citations rendered inline with hover-card source previews.
• Research artifacts saved to research/{topic}.json for re-use.
• Works in both the desktop chat and the mobile field assistant.

Research is reserved for genuine context-gathering. Routine domain answers stay local to the agent skill — no unnecessary network round-trips.

The canvas:

• Drag entities and relationships onto the graph.
• Edit properties inline; constraint expressions accept a small typed DSL.
• Validates against the AgentSkill type system as you edit.
• Live-renders the resulting Globe layer config and toolbar in a preview panel.

The same designer ships across the desktop workspace and the public template catalog.

The pattern:

Behavior:

• Registry is a constant manifest — names and dynamic-import paths only.
• The plugin module loads on first request, caches for the session.
• Switching skills swaps entities, relationships, constraints, layer config,

toolbar, and AI tools in one transaction.

• Unused plugins do not contribute to the bundle.

5G initial release:

• Macro and small-cell entities with band, EIRP, and antenna properties.
• Coverage simulation against a propagation model (ITU-R P.452).
• Backhaul planning with fiber-first, microwave fallback.
• See 5G wireless.

Construction initial release:

• Phase, activity, resource, and dependency entities.
• Critical-path and resource-leveling solvers.
• Gantt overlay on the spatial view.
• See Construction project-management.

What ships:

• 3D basemap with custom layers for indoor models, fleet models, and equipment.
• WebGL 3D overlay for satellite orbits, beam-coverage cones, and analytical

scenes that need a full 3D camera.

• Single camera shared across both layers; selections and hovers are unified.

Performance budget targets:

• 60 fps with up to ~10,000 indoor entities or ~5,000 fleet markers in scene.
• Lazy LOD for orbital tracks beyond 200 satellites.

Initial scope:

• MIP for facility-location and assignment problems.
• Graph algorithms for routing and connectivity.
• Custom heuristics for problems that fit neither well.
• Stateless service with horizontal scaling.

Browser-side dispatcher:

• Tries the in-browser solver first; falls back to the cloud only when needed.
• Identical response shape from both paths.

What shipped:

• Virtual file system with paths, contents, and a simple change-event bus.
• Reactive Globe layer engine — any GeoJSON file under layers/ renders

automatically.

• _meta/schema.json as the single source of truth for active domain types.
• Toolbar, tabs, and AI tools generated from the active schema.

The persistence and history layer landed later (February 2026); the read-side reactive model has been stable since this release.

Type system shipped today:

• 8 type files defining the contract every skill conforms to.
• All fully typed; JSON-serializable; no any.
• Compiles to a manifest used by the registry, the renderer, the toolbar, and

Jax.

Project shell:

• Mounts a skill as the active domain.
• Wires the toolbar, sidebar tabs, map layers, and AI tools from the skill

manifest.

• Loading a different skill swaps every surface in one transaction.

This is the architectural foundation everything since rests on.