rrt/docs/atlas/startup-shell-and-content.md

Startup, Shell, and Content

Primary atlas source:

• crt-and-process-startup.md
• bootstrap-and-shell-service-bring-up.md
• shell-ui-command-and-deferred-work-flow.md
• presentation-overlay-and-frame-timing.md
• map-and-scenario-content-load.md

Current grounded owners:

• entry -> CRT bring-up -> app_bootstrap_main
• bootstrap_init_shell_window_services
• shell_install_global_controller
• shell_service_pump_iteration
• shell_dispatch_ui_command
• shell_service_frame_cycle
• shell_map_file_entry_coordinator
• shell_map_file_world_bundle_coordinator
• world_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.