Concepts
These pages explain the cross-cutting ideas behind Neops — how a workflow turns into work, how the platform stays safe under failure, and how testing fits in. Component-specific concepts (definitions, lifecycle, scheduling, etc.) live inside each component’s own section.
-
System overview
A single diagram showing how a workflow definition, the engine, the CMS, the blackboard, and zone-aware workers fit together.
-
How Neops operates
Read-path, write-path, and full execution-flow sequence diagrams across User, CMS, engine, blackboard, and worker.
-
Workflows as transactions
Why every workflow run is a transaction: locking, atomic updates, and FAILED_SAFE vs FAILED_UNSAFE failure classification.
-
Function blocks
Versioned, typed Python units that the engine schedules and workers execute. See also: purity & idempotency.
-
Blackboard & execution model
How jobs flow from engine to workers and back. Pairs with the execution model page.
-
Remote lab testing
Session queue, lab lifecycle, and the one-lab-per-host invariant that makes shared testing safe.