Nexus Orchestrator Canvas — User Manual — MAN-ORCH-01

Orchestrator Canvas
User Manual

End-user and developer guide for WORMWOOD_APP.html — the Nexus visual pipeline builder. Covers connecting to the engine, building pipeline graphs, configuring nodes, saving and running pipelines, canvas navigation, demo mode, themes, and URL parameters.

Document ID
MAN-ORCH-01
Version
1.0
Audience
Designers & Admins
Tier
5 — User Docs

01 — What Is the Orchestrator Canvas?

Purpose and scope of WORMWOOD_APP.html

The Orchestrator Canvas is the pipeline designer inside Nexus. It lets you visually build, edit, and run process pipelines as directed acyclic graphs (DAGs). Each pipeline node represents a single processing step; edges represent data flow between steps.

The canvas operates at Level 1 (Macro scale) of the Nexus 4-resolution model — the highest level, where entire workflow graphs are composed and executed.

CapabilityDetail
Pipeline browsingSelect an app (org) and a pipeline from the top bar dropdowns
Node placementDrag node types from the right palette onto the canvas
Edge creationDrag from one node's output pin to another node's input pin
Node configurationDouble-click a node to open the config panel; edit properties and rules
Pipeline saveSAVE button commits the current graph to the engine database
Pipeline runRUN button executes the pipeline and opens the run log panel
Multi-level editingFour level tabs (L1–L4) navigate the four Nexus resolution scales
Live SSEServer-Sent Events keep canvas node status indicators live during execution

02 — Accessing the Canvas

How to open WORMWOOD_APP.html and connect to the engine

Direct URL

The canvas is served by the Wormwood engine at:

http://localhost:8011/nexus-ui/WORMWOOD_APP.html

Append URL parameters to pre-configure the session (see Section 12).

From the Hub Dashboard

  1. Log in to NEXUS_APP.html
  2. From the hub, click the "ORCHESTRATOR" button in the top bar, or use the FAB → Orchestrator
  3. The canvas opens in a new tab pre-loaded with the current app and skin

Connecting to the Engine

On first load, the canvas reads the ?key= URL parameter for your API key. If absent, it tries a stored key from localStorage. Without a valid key, all API calls return 401 and the SSE indicator shows OFFLINE.

API Key required: All pipeline operations need a valid API key. Get yours from your Nexus administrator or from the Admin Panel at http://localhost:8011/admin.

03 — Top Bar Reference

Every control in the topbar, left to right

ControlPositionFunction
« HUBFar leftReturn to NEXUS_APP.html Hub Dashboard
WORMWOOD APPCentreCanvas title / breadcrumb root
L1 / L2 / L3 / L4Centre-rightSwitch between the four Nexus resolution levels (Macro, Micro, Nano, Pico)
App selectorRight barDropdown listing all apps registered in the engine; selecting an app loads its pipelines
Pipeline selectorRight barDropdown listing pipelines for the selected app; selecting one loads its graph onto the canvas
SAVERight barWrite the current canvas graph back to the engine (persists nodes + edges)
RUNRight barExecute the selected pipeline; opens the run log panel
DEMORight barRun the autonomous demo sequence (only shown for demo-enabled pipelines)
NEW PIPELINERight barCreate a new empty pipeline for the selected app
ZOOM + / ZOOM −Toolbar below topbarIncrease or decrease canvas zoom by 20%
RESETToolbar below topbarReset zoom to 100% and pan to origin
Zoom % labelToolbar below topbarCurrent zoom level display
SSE indicatorToolbar below topbarLive event connection status: LIVE (green) or OFFLINE (dim)
PALETTEToolbar below topbarToggle the node type palette panel (right side)
ADD NODEToolbar below topbarOpen a quick-add menu for node types
DELETEToolbar below topbarDelete the currently selected node
LOGToolbar below topbarToggle the run log panel

04 — Loading a Pipeline

Selecting an app and pipeline to edit

  1. In the top bar, open the App selector dropdown and choose the app you want to work with
  2. The Pipeline selector populates with all pipelines belonging to that app
  3. Select a pipeline from the dropdown
  4. The canvas clears and loads the pipeline graph — nodes and edges appear
  5. The breadcrumb bar below the topbar updates to show the loaded pipeline name

URL shortcut: Load a specific pipeline directly with ?org=arc&pipeline=nesto-worker-onboard-full&key=your-key in the URL. The canvas loads both the app and pipeline automatically.

Empty Canvas

If no pipeline is selected, the canvas is blank. This is the correct initial state. Select a pipeline or create a new one before editing.

05 — Navigating the Canvas

Pan, zoom, and keyboard shortcuts

Pan

Hold Space and drag anywhere on the canvas background, or right-click-drag. The cursor changes to a grab hand during pan.

Zoom

MethodAction
Mouse scrollScroll wheel zooms in/out centred on the cursor position
ZOOM + buttonZoom in by 20%
ZOOM − buttonZoom out by 20%
RESET buttonSnap back to 100%, pan to default origin (60,40)

Keyboard Shortcuts

KeyAction
Space + dragPan canvas
DeleteDelete selected node
EscapeCancel active connection drag

06 — Working With Nodes

Adding, moving, selecting, and deleting nodes

Adding a Node

  1. Click PALETTE in the toolbar to open the node type panel on the right
  2. Find the node type you want (node types are grouped by category)
  3. Drag the node from the palette onto the canvas at the desired position
  4. The node appears with its default name and two connection pins (input and output)

Alternative: Click ADD NODE in the toolbar to add a node of a chosen type at a default position, then drag it into place.

Node Categories

CategoryColourNode Types
FORMBlueSubmission Form, Review Form, Approval Gate
INTELPurpleOCR Document, Validate Record, AI Transform, Exception Router
STOREGreenWrite deltaPrism, Query deltaPrism, Cache Data
APIAmberHTTP POST, Send SMS, Send Email, Webhook Listener
LOGICOrangeCondition Branch, Parallel Split, Wait/Delay, Loop Iterator

Moving a Node

Click and hold on a node body (not a pin) and drag to reposition it. Edges connected to the node follow the node in real time.

Selecting a Node

Click once on a node to select it. The selected node renders with an accent outline. The DELETE button in the toolbar becomes active.

Deleting a Node

  1. Click the node to select it
  2. Press Delete or click the DELETE toolbar button
  3. The node and all its connected edges are removed from the canvas

Save required: Deletions are not permanent until you click SAVE. Reloading the pipeline without saving discards all unsaved changes.

07 — Connecting Nodes

Drawing edges between node pins

Each node has small circular pins on its left (input) and right (output) sides.

  1. Hover over a node's output pin (right circle) — the cursor changes
  2. Click and drag from the output pin towards the target node
  3. A dashed temporary edge follows your cursor
  4. Release the mouse over the input pin (left circle) of the target node
  5. The edge is created and renders as a bezier curve between the two nodes

Tip: You can connect one output pin to multiple input pins (fan-out). You can connect multiple output pins to one input pin (fan-in). Both are valid pipeline topologies.

Deleting an Edge

Edges cannot currently be deleted individually from the canvas. To remove a connection, reconfigure the pipeline by deleting the relevant node and re-adding it, or edit the graph JSON directly via the engine API (PUT /pipelines/{id}).

08 — Configuring Nodes

Using the Class Panel to set node properties and rules

Opening the Config Panel

Double-click any node on the canvas. The Class Panel slides in from the right, showing the node's configuration fields.

Panel Sections

SectionContent
Node headerNode type badge and editable node label
PropertiesKey–value pairs specific to the node type (e.g., HTTP URL, email recipient, delay duration)
Rule ReferenceLink to the Nexus rule engine rule governing this node. Click EDIT RULE to open the inline rule editor (Pico scale)

Editing Properties

  1. Double-click the node to open the Class Panel
  2. Click the property value field you want to change — it becomes editable (contenteditable)
  3. Type the new value
  4. Click outside the field or press Enter to confirm
  5. Changes are stored in memory; click SAVE to persist to the engine

Inline Rule Editor (Pico Scale)

Click EDIT RULE in the Rule Reference section to open the Pico-scale rule editor directly inside the panel. This editor lets you write or modify the Lua rule expression that governs the node's execution logic.

09 — Saving a Pipeline

Persisting graph changes to the engine

  1. Ensure a pipeline is selected in the Pipeline selector
  2. Click SAVE in the top bar
  3. The status bar at the bottom shows Saved: [pipeline name] v[version] on success

Auto-save is not enabled. All changes (moved nodes, new edges, property edits) are lost on page reload unless you click SAVE first.

10 — Running a Pipeline

Executing the current pipeline via the canvas

  1. Select the pipeline you want to run from the Pipeline selector
  2. Click RUN in the top bar
  3. The Run Log panel opens on the right, showing execution events in real time via SSE
  4. Node status indicators on the canvas update as each node executes (pending → running → pass/fail)
  5. When execution completes, the final status is shown in the run log

Run Log Panel

The run log panel shows a live stream of pipeline events. Each line contains a timestamp, node name, event type, and message. Errors appear in red. Warnings in amber. Successful node completions in green.

Tip: You can keep the run log open while editing. The SSE stream will update it automatically on the next run.

11 — Demo Mode

Running the autonomous demo sequence

Demo mode is available for specific pipelines that have a defined demo sequence (e.g., nesto-worker-onboard-full). When such a pipeline is loaded, the DEMO button appears in the top bar.

  1. Load a demo-enabled pipeline
  2. The DEMO button becomes visible in the right side of the top bar
  3. Click DEMO to start the autonomous demo sequence
  4. The canvas animates through each node in sequence, highlighting execution flow with timed transitions
  5. Demo completes automatically; a completion message appears in the status log

Demo mode is designed for prospect presentations and sales demos. It animates the full pipeline without requiring real backend integrations to be active.

12 — URL Parameters

Configuring the canvas via URL for direct links and integrations

ParameterExampleEffect
?key=?key=local-test-keySets the API key used for all engine requests. Saved to localStorage. Required for all API calls.
?org=?org=arcPre-selects the app (org) in the App selector dropdown. The pipeline list loads automatically.
?pipeline=?pipeline=nesto-worker-onboard-fullPre-selects and loads the specified pipeline. Requires ?org= to be set (or app pre-selected). The pipeline graph loads automatically.
?skin=?skin=glass-emberApplies a visual skin on load (fallback for direct links). When launched from NeXus Hub, skin is passed via sessionStorage['na-session-skin'] instead. Valid values: glass-ember, glass-aurora. Omit to use the stored preference or default.

Example Full URL

http://localhost:8011/nexus-ui/WORMWOOD_APP.html?org=arc&pipeline=nesto-worker-onboard-full&skin=glass-ember&key=local-test-key

This URL opens the canvas, applies the glass-ember skin, selects the ARC app, and loads the Nesto Worker Onboard pipeline immediately — ready to edit or demo without any manual selection.

13 — Visual Skins

Changing the canvas theme

SkinURL valueDescription
Default (Dark Green)omit parameterStandard Nexus dark theme with green (#19E28A) accent
Glass Emberglass-emberWarm amber/orange glass-morphism with frosted panels
Glass Auroraglass-auroraCool cyan/teal glass-morphism aurora effect

Skin preferences are stored in localStorage under the key nexus-theme. The stored skin applies automatically on next load even without the URL parameter.

14 — Multi-Level Editing (L1–L4)

Navigating the four Nexus resolution scales

The level tabs in the topbar switch the canvas between the four Nexus resolution levels. Each level holds an independent graph.

LevelScaleUnitPurpose
L1MacroWorkflow / PipelineThe main execution graph. This is what runs when you click RUN.
L2MicroClass / Entity SchemaEntity class definitions. ChameleonV2 reads these to generate forms.
L3NanoPropertyTyped fields with deltaPrism BDT constraints and RBAC visibility rules.
L4PicoRuleNexus rule engine rules governing each property field.

Most users work exclusively at L1. L2–L4 are used by Nexus system architects when designing entity schemas and validation rules for a new app.

15 — Creating a New Pipeline

Starting from a blank canvas

  1. Select an app from the App selector (the pipeline must belong to an app)
  2. Click NEW PIPELINE in the top bar
  3. Enter a name for the new pipeline in the prompt
  4. An empty pipeline is created in the engine and selected in the Pipeline selector
  5. The canvas clears — you are now editing the new empty pipeline
  6. Add nodes from the palette, connect them, configure each node, then click SAVE

16 — SSE Connection Indicator

Understanding the live connection status

The SSE (Server-Sent Events) indicator in the toolbar shows the live connection to the engine:

StateAppearanceMeaning
LIVEGreen textEngine is reachable; node status updates stream in real time during pipeline runs
OFFLINEDim textCannot reach the engine. Check that uvicorn is running on the configured port. API calls will also fail.
RECONNECTINGAmber textConnection lost; canvas is attempting to reconnect every 5 seconds

17 — Troubleshooting

Common issues and solutions

ProblemCauseSolution
App selector shows "0 org(s) loaded"Engine not running or API key invalidStart uvicorn: .venv\Scripts\uvicorn wormwood.api.app:app --port 8011. Verify key in URL.
Pipeline loads but canvas is blankPipeline has no nodes saved yetThis is correct for a new pipeline. Add nodes from the palette.
SAVE fails with 401API key missing or expiredAdd ?key=your-key to the URL and reload.
Node drag is jerky / node teleportsBrowser compositor issueDisable browser extensions. Try in a different browser. Ensure GPU acceleration is enabled in browser settings.
SSE shows OFFLINE despite engine runningEngine on wrong port, or CORS issueConfirm engine URL in the canvas source (ENGINE_API constant). Default is http://localhost:8011.
DEMO button not visiblePipeline slug is not in DEMO_SLUGS setDemo is only available for specific pre-configured pipelines. The current demo pipeline is nesto-worker-onboard-full.
Skin not applyinglocalStorage blocked, or sessionStorage clearedWhen launched from NeXus Hub, skin arrives via sessionStorage['na-session-skin'] (PROD-SKIN-002). For direct links, use ?skin=glass-ember URL param. Enable localStorage or clear site data.
Edge not connectingReleased mouse outside target pinStart drag precisely on the output pin circle. Release precisely on the input pin circle. Zoom in if pins are too small.