orkcore-subsystem

Subsystem initialization order is managed using dependency-driven startup that orchestrates initialization topologically. This ensures subsystems are initialized in the correct order and safely shut down, preventing startup failures and deadlocks.

FSM-based lifecycle management uses UNINITIALIZED, INITIALIZING, READY, SHUTTING_DOWN, and TERMINATED states. These states enforce robust transitions, ensuring predictable startup order and safe shutdown for core subsystems.

Wave-based parallel initialization executes multithreaded subsystems across waves with enforced thread affinity. This orchestrates core subsystems like GPU and AUDIO to initialize concurrently while respecting dependency constraints.

Core subsystems are registered using factory patterns that provide clear wiring for OPQ, CORE, CATALOG, GPU, AUDIO, and LEV2 components. This enforces predictable creation, thread affinity assignment, and lifecycle registration.

Diagnosing initialization sequences is a core use case enabled by lifecycle FSMs and subsystem registration. By validating state transitions and dependency-driven startup order, you can identify and resolve conflicting dependencies during development and testing.

Topological ordering for subsystem shutdown is not suitable when core subsystems lack clearly defined dependency relationships or require non-deterministic termination timing. Safe shutdown requires strict, predictable dependency graphs to avoid violating lifecycle FSMs.