Nexus Engine SDK Architecture

Overview

Nexus Engine is an extensible, modular WebGL/WebGPU runtime SDK designed for building interactive 3D spatial applications. It acts as a foundation ("Lego baseplate") where advanced functionalities—such as physics, vehicles, mobile UIs, NLP, and AI agents—can be dynamically plugged in as standalone systems.

The Core Philosophy

1. Engine SDK First: The primary product is the SDK (@neural-workspace/nexus-engine-core), which orchestrates scenes, provides the event bus, and defines the Plugin Framework interfaces.
2. Modular Systems: Advanced features (e.g., Drones, Pathfinding, NLP) are not baked into the engine. They are independent, standalone, plug-and-play modules.
3. Decoupled Architecture: You can build your own systems locally or seamlessly pull proprietary systems from the Neural Workspace marketplace using your API key.

Architecture Structure

• @neural-workspace/nexus-engine-core: The Core Engine SDK. Contains the scene orchestrator, engineEventBus, and strict TypeScript interfaces for the Plugin System (EditorPlugin schema).
• Nodes: Standard 3D static objects (Meshes, Lights, Cameras).
• Systems: Encapsulated logical or 3D modules.

Technical Decisions

1. React-First SDK: Chosen because many features (mobile phone, advanced UI overlays, dynamic NLP chatbots) are much easier to implement and maintain in React compared to Vanilla JS.
2. Event-Driven Architecture (Loose Coupling): Systems do not import each other. For example, a Drone system listens for a generic COMMAND_RECEIVED event from the NLP system, and requests paths via PATHFINDING_REQUEST. If a dependency is missing, systems degrade gracefully.
3. Three.js: Standard reliable 3D web technologies.

Documentation Index

• Plugin System & Schema-Driven UI