1.6 KiB
1.6 KiB
Startup, Shell, and Content
Primary atlas source:
- control-loop-atlas.md#crt-and-process-startup
- control-loop-atlas.md#bootstrap-and-shell-service-bring-up
- control-loop-atlas.md#shell-ui-command-and-deferred-work-flow
- control-loop-atlas.md#presentation-overlay-and-frame-timing
- control-loop-atlas.md#map-and-scenario-content-load
Current grounded owners:
entry-> CRT bring-up ->app_bootstrap_mainbootstrap_init_shell_window_servicesshell_install_global_controllershell_service_pump_iterationshell_dispatch_ui_commandshell_service_frame_cycleshell_map_file_entry_coordinatorshell_map_file_world_bundle_coordinatorworld_entry_transition_and_runtime_bringup
What this note is for:
- Startup and bootstrap ownership questions
- Shell controller bring-up and frame-cycle ownership
- Shell command or deferred-work routing
- File-flow and content-load boundaries
- World bring-up versus shell-owned cadence questions
Current bounded conclusion:
- No later long-lived gameplay cadence is currently grounded outside the bootstrap-owned shell service loop; the local evidence still supports the nested-under-shell reading.