nexConductor

Shared routine orchestration runtime for the nex* Nexus ecosystem.

nexConductor owns the cross-package machinery for long-running routines:

• XState v5 routine setup helpers
• one owned destination-travel actor plus wait actors for Nexus observations, triggers, GMCP updates, and delays
• command actions for send and queue
• standard combinators and sequence launching
• cross-package routine composition by registry id (runRoutine, sequence-routines)
• top-level routine runner with foreground/interrupt lifecycle
• standing supervisor manager
• package registration at globalThis.nexConductor

Domain routine content belongs to package-owned packs. nex* packages should define their own routines (a reusable tour is a { sequence } routine), then register them with this runtime.

Install

npm install nexconductor

The published artifact is dist/nexconductor.min.js, an IIFE bundle built for the Nexus client. Loading it installs the runtime at globalThis.nexConductor; it does not export an ES module surface.

Host dependencies stay external and are resolved from Nexus runtime globals rather than bundled, so the host must provide them:

| Peer | Runtime global | | ----------- | ------------------- | | nexevent | eventStream | | nexaction | nexAction | | nexsys | nexSys | | xstate | nexRuntime.xstate |

Package Shape

The central runtime lives under src/base/conductor and exports the core API. The Nexus IIFE bundle entry is src/nexconductor.bundle.js, which installs globalThis.nexConductor.

Domain routines are not shipped from this package. Package-owned routine packs register their machines and supervisors through the runtime API.

Commands

npm run lint
npm run test:run
npm run build
npm run build:dev
npm run verify

npm run verify runs lint, tests, both bundle builds, and npm pack --dry-run.

Docs

Start at docs/README.md. Current operating docs live in docs/Conductor. Older concept/FSM documents are preserved as design history.