Sequencer Lifecycle

Sequencer lifecycle controls startup ordering for service and scene initialization.

In the current architecture, service setup is commonly executed by sequencer nodes such as RegisterServiceRegistryNodeSO.

Recommended Ordering

1. Register core services and catalogs
2. Run dependent startup systems
3. Load/transition scenes as needed

If order is wrong, catalog-based lookups can fail even when data is valid.

Dispose / Re-run Notes

When sequence runs are disposed or restarted, unregister behavior depends on node configuration (for example _unregisterOnDispose).

Related Pages

• Service Registry
• Service Locator