Nexus Demo Vision

The demo must traverse all four orchestration levels in sequence, creating entities at each level before descending to the next. A viewer watching the demo should understand, without narration, that Nexus handles organisational structure, team structure, user assignment, and execution flow as a unified hierarchy.

Each step is performed by the autonomous mode controller via real UI interactions (programmatic click, focus, input events). The canvas and all panels remain visible and interactive throughout. The sequence runs at a pace optimised for comprehension, not speed — roughly 18–25 seconds per level, 90 seconds total end-to-end.

1. Reset to blank state

   AUTO Canvas is cleared. Any existing nodes are removed. Org selector resets. A progress indicator appears in the toolbar: AUTO MODE — STEP 1 / 9. This communicates to any observer that an autonomous sequence is running.
2. Create Organisation — Nesto Industries

   USER PANELAUTO-FILLED A slide-in panel opens (using the existing #class-panel infrastructure or a new entity panel). Title: NEW ORGANISATION. Fields animate in with the data template intellisense pattern: system detects "organisation" type, pre-proposes: Name, Industry, Jurisdiction, Status, Primary Contact. Fields are filled character-by-character. Values: Nesto Industries LLC / UAE Compliance / AE / Active / m.khalil@nesto.ae. Panel saves. Org appears in the org selector dropdown.
3. Create Team — Compliance Operations

   USER PANELAUTO-FILLED New entity panel: NEW TEAM under Nesto Industries. Template-suggested fields: Team Name, Parent Org, Function, Member Cap. Filled: Compliance Operations / Nesto Industries LLC / Worker Compliance / 12. Saved. Team node appears as a data card on the canvas at Level 1 position (top-left region).
4. Create Three Users with Roles

   USER PANELRBACAUTO-FILLED Three sequential user creation panels open and close. For each user, the system detects "person + role" data shape and proposes: Full Name, Email, Nationality, Role, Team. Roles are selected from the pre-defined role registry (Submitter / Validator / HR Manager). The RBAC matrix is automatically populated from the role definition — field visibility, editability, and required status for every schema field is auto-derived without manual configuration. Three user cards appear in the canvas Level 2 region.
5. Select Data Template — Worker Onboarding

   DATA MODELINTELLISENSE A template picker opens. Categories shown: Personal Data / Compliance Documents / Financial / Logistics / Custom. User selects Worker Onboarding (UAE). System immediately proposes the canonical field list: First Name, Last Name, Nationality, Passport Number, Emirates ID, Occupation, Employer, Medical Status, POLO Exemption Flag, Compliance Status. Each field has a pre-assigned data type. User can add, remove, or rename fields — but in auto mode, the default set is confirmed in 1.2 seconds. Schema is created. Node type palette updates with a new WorkerProfile type available for placement.
6. Build Pipeline on Canvas

   AUTOCANVAS Nodes are placed one by one with smooth position animations. Each node appears, its config panel briefly opens, key fields are shown, then closes. Sequence: form_ingest (Submitter role, WorkerProfile schema) → ocr_verify (document check) → validate_compliance (rule set: nesto_worker_docs) → store_worker (writes to registry) → hr_gate (HR Manager role, Reviewer form) → sms_notify (compliance confirmation) → api_forward (MoHRE + GDRFA endpoints). Edges drawn between nodes one at a time. Pipeline structure matches the Nesto use case spec.
7. Run Pipeline — One Click

   EXECUTEAUTO The RUN button is clicked programmatically. The engine receives the pipeline definition and begins execution. Progress dots activate on each node as it runs. This is a real engine call, not simulated.
8. Form Execution — RBAC-Styled Forms Per Role

   RBACFORMSAUTO-FILLED As each HumanGate or FormNode fires during execution, a form panel opens inline (not as a modal overlay — as a side panel or canvas-attached panel). The form is generated from the data schema. Its visual style variant is derived from the RBAC role: Submitter forms use a minimal entry variant; Validator forms use a review/readonly variant with diff highlighting; HR Manager forms use a decision authority variant with approve/reject controls. All forms are filled autonomously with Mohammed Al Rashidi's pre-seeded data. Each form submits itself. Node goes green.
9. Completion State — Exportable Result

   COMPLETEEXPORT All 7 nodes are green. Run log shows full execution trace. A result summary card appears: Worker ID assigned, Compliance Status ACTIVE, API refs from MoHRE and GDRFA, SMS delivery confirmed. An EXPORT button is present (outputs the pipeline definition as JSON). The auto mode controller stops. The interface returns to normal interactive state. The data created during the demo is real and persists in the canvas state.

Forms are not hand-designed. They are generated from the data schema + the RBAC matrix for the role of the current user. The result is that the same underlying data entity produces a fundamentally different form surface for each role — without any per-form design work.

The Pyrometrix autonomous demo is the model for style and execution philosophy. Key attributes to replicate: