Update docs

Author: ThomasFarstrike

docs/architecture/boot-sequence.md

@@ -0,0 +1,22 @@
+# Boot sequence
+
+MicroPythonOS consists of several core components that initialize and manage the system.
+
+- **MicroPythonOS/lvgl_micropython/lib/micropython/ports/esp32/modules/_boot.py**: attempts to mount the internal storage partition to / and if it fails, formats it
+
+- **internal_filesystem/main.py**: Hands off execution to /lib/mpos/main.py by importing it
+
+- **/lib/mpos/main.py**:
+    - Detects the hardware board
+    - Initializes the filesystem driver
+    - Mounts the freezefs into /builtin/
+    - Loads the com.micropythonos.settings
+    - Initializes the user interface.
+    - Starts the WiFi autoconnect thread
+    - Launches the `launcher` app that shows the icons
+    - Starts the asyncio REPL
+    - Marks the current boot as successful (cancel rollback)
+    - Starts the TaskManager
+
+See [Filesystem Layout](filesystem.md) for where apps and data are stored.
+

docs/architecture/frameworks.md

@@ -463,6 +463,5 @@ class TestMyFramework(unittest.TestCase):
 ## See Also
 
 - [AppManager](../frameworks/app-manager.md): App discovery, installation, and launching
-- [System Components](system-components.md): Overview of all system components
 - [Architecture Overview](overview.md): High-level design principles
 - [App Development Guide](../apps/index.md): How to use frameworks in apps

docs/architecture/index.md

@@ -3,6 +3,6 @@
 Learn about the design and structure of MicroPythonOS, inspired by Android's "thin" OS model.
 
 - [Overview](overview.md): High-level architecture and design principles.
-- [System Components](system-components.md): Key files and their roles.
+- [Boot Sequence](boot-sequence.md): What happens when MicroPythonOS starts up
 - [Frameworks](frameworks.md): Unified framework pattern for system services.
 - [Filesystem Layout](filesystem.md): Directory structure for apps and data.