trail-mate/docs/engineering/engineering-maps.md

Engineering Maps

Positioning

The root index of the software structure model. This is only responsible for navigation, aggregation and version timelines; specific UML and engineering explanations must fall in various diagram directories and specific diagram documents.

Metadata

Project version: 0.1.30-alpha Git branch: main Git commit: 34aad0bffa Git workspace status: dirty Updated on: 2026-06-25T09:19:20.669Z

Diagram index

Diagram type	Quantity	Maps	Description
Package Diagrams	18	docs/engineering/package-diagrams/package-diagrams-maps.md	Enter the package/module boundary dashboard and view by project directory how the 18 modules bear entry, contract, adaptation, shared capabilities, running assembly or infrastructure responsibilities, and continue to drill down to components, structures, sequences, deployment nodes and technology hotspots.
Component Diagrams	22	docs/engineering/component-diagrams/component-diagrams-maps.md	Enter the component dashboard to view 22 key classes, functions, React Responsibilities, referenced/calling relationships, external dependencies/calling relationships, belonging modules and drill-down risks of components, command entry or interface objects.
Deployment Diagrams	0	docs/engineering/deployment-diagrams/deployment-diagrams-maps.md	Enter the running/deployment node dashboard to view the build configuration, desktop shell, CLI, package management, CI Or how the local running entrance affects the startup, packaging and delivery path of the project.
Class / Structural Diagrams	10	docs/engineering/class-structural-diagrams/class-structural-diagrams-maps.md	Enter the Structure Collaboration Dashboard to see how classes, interfaces, and value objects form domain models, policies, ports, adaptations, or shared supports by nameable business/technical context; it is not a list of class names generated by the number of top-level layers or relationships.
Sequence Diagrams	18	docs/engineering/sequence-diagrams/sequence-diagrams-maps.md	Enter the Sequence dashboard to view 18 real call fragments observed by local warehouse evidence, complementing the static structure diagram with a dynamic collaboration perspective. Static import/reference will not be treated as a sequence diagram.
State Machine Diagrams	0	docs/engineering/state-machine-diagrams/state-machine-diagrams-maps.md	Enter the state machine dashboard; only generated when there is evidence that key state fields, enumerations, or migration semantics exist to avoid scraping UML Fictional state machine.
Technical Hotspots	16	docs/engineering/technical-hotspots/technical-hotspots-maps.md	Enter the technical hotspot dashboard to see why large files, widely reused objects, external collaboration objects, dependency clusters or scan alarms increase the cost of reading, modifying, testing and regression.

UML drill-down level rules

package

• Drill-down diagram types: component, class_structural, sequence, deployment, technical_hotspot
• Reason: Package Diagram is the top-level engineering boundary of technical complexity; it can drill down to key components, structural collaborations, running links, running configurations and complexity hotspots within the boundary.

class_structural

• Drill-down diagram types: component, sequence, technical_hotspot
• Reason: Class / Structural Diagram explains structural collaboration in a nameable business/technical context; it can continue to drill down to specific components, dynamic interaction fragments and structural risks.

component

• Drill-down diagram types: sequence, class_structural, technical_hotspot
• Reason: Component Diagram is the key technical object perspective; it can drill down to the call fragments, structural slices and related hotspots in which the object participates.

sequence

• Drill-down diagram types: component, class_structural, technical_hotspot
• Reason: Sequence Diagram is a dynamic collaboration perspective; it can reversely locate participating components, structural boundaries and possible operational risks.

deployment

• Drill-down diagram types: package, component, technical_hotspot
• Reason: Deployment Diagram is a run/build node perspective; it can drill down to the corresponding package, entry component and run configuration hotspot.

technical_hotspot

• Drill-down diagram types: package, component, class_structural, sequence
• Reason: Technical Hotspot is a risk perspective; it needs to be linked back to the boundaries, components, structures or call fragments that create complexity.

Directory tree

Package Diagrams

• Module boundary: managed_components - Open the package-level diagram of managed_components, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is the entry module, shared capability, runtime Support or infrastructure boundaries. You can continue to drill down to 4 Technical Hotspots.
• Module boundary: build.t_display_p4_tft - Open build.t_display_p4_tft For the package-level diagram, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 1 Technical Hotspot.
• Module boundary: build.tdisplayp4_tft - Open the package-level diagram of build.tdisplayp4_tft, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is the entry module, shared capability, runtime Support or infrastructure boundaries. You can continue to drill down to 1 Technical Hotspot.
• Module boundary: boards - Open the package-level diagram of boards, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 2 Component Diagrams, 5 Class/Structural Diagrams, and 2 Technical Hotspots.
• Module boundary: build.tdisplayp4_amoled - Open the package-level diagram of build.tdisplayp4_amoled, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is the entry module, shared capability, runtime Support or infrastructure boundaries. You can continue to drill down to 1 Technical Hotspot.
• Module boundary: build.c6_companion - Open the package-level diagram of build.c6_companion, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 1 Technical Hotspot.
• Module boundary: apps/linux_uconsole_gtk - Open apps/linux_uconsole_gtk For the package-level diagram, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 8 Component Diagrams and 3 Technical Hotspots.
• Module boundary: apps/esp32_lvgl - Open the package-level diagram of apps/esp32_lvgl, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is the entry module, shared capability, runtime Support or infrastructure boundaries. You can continue to drill down to 3 Component Diagrams and 6 Sequence Diagrams.
• Module boundary: firmware - Open the package-level diagram of firmware, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 2 Component Diagrams.
• Module boundary: apps/nrf52_node - Open the package-level diagram of apps/nrf52_node, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is the entry module, shared capability, runtime Support or infrastructure boundaries.
• Module boundary: apps/linux_cardputer_zero - Open apps/linux_cardputer_zero For the package-level diagram, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down diagram to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary. You can continue to drill down to 4 Component Diagrams and 2 Technical Hotspots.
• Module boundary: apps/linux_sim_shell - Open the package-level diagram of apps/linux_sim_shell, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
• Module boundary: builds - Open the package-level diagram of builds, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
• Module boundary: images - Open the package-level diagram of images, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
• Module boundary: cmake - Open cmake's package-level diagram, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
• Module boundary: apps/README.md - Open the package-level diagram of apps/README.md, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
• Module boundary: COPYRIGHT - Open the package-level diagram of COPYRIGHT, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.
• Module boundary: LICENSE - Open the package-level diagram of LICENSE, first confirm what project boundary it is, and then use the file size, symbol size, cross-module reference direction and drill-down map to determine whether it is an entry module, shared capability, runtime support or infrastructure boundary.

Component Diagrams

• Function Node: main - Open the component diagram of Function Node: main and view it at apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Technical Hotspots.
• Function Node: contains - Open the component diagram of Function Node: contains and view it at apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Technical Hotspots.
• Function Node: launchSettingsLayout - Open the component diagram of Function Node: launchSettingsLayout and see where it is located What type of technical objects are in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp, what responsibilities they bear, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: makeLabel - Open the component diagram of Function Node: makeLabel and view it at What type of technical objects are in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_widgets.cpp, what responsibilities they bear, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: makeSettingsRow - Open the component diagram of Function Node: makeSettingsRow and view it at What type of technical objects are in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp, what responsibilities they bear, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: main - Open the component diagram for Function Node: main and view it at apps/esp32_lvgl/tests/esp32_lvgl_sd_coredump_contract_smoke.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 5 Sequence Diagrams.
• Function Node: not_contains - Open the component diagram of Function Node: not_contains and see where it is Which type of technical objects in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, what responsibilities they bear, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Technical Hotspots.
• Service Object: main - Open the component diagram of Service Object: main and view it at firmware/c6_companion/tests/test_tm_services_functional.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots.
• Function node: contains - Open the component diagram of function node: contains and see where it is located What type of technical objects are in apps/esp32_lvgl/tests/esp32_lvgl_sd_coredump_contract_smoke.cpp, what responsibilities they bear, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 5 Sequence Diagrams.
• Function Node: makeBoardProfile - Open the component diagram of Function Node: makeBoardProfile and view it at boards/t_echo_lite/include/boards/t_echo_lite/board_profile.h Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Class/Structural Diagrams and 2 Technical Hotspots.
• Function Node: pinNum - Open the component diagram of Function Node: pinNum and view it at boards/t_echo_lite/include/boards/t_echo_lite/board_profile.h Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Class/Structural Diagrams and 2 Technical Hotspots.
• Function Node: refreshUi - Open the component diagram of Function Node: refreshUi and view it at apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_shell.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function node: refreshMap - Open the component diagram of function node: refreshMap and view it at What type of technical objects are in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_map_logic.cpp, what responsibilities they bear, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: read_file - Open the component diagram of Function Node: read_file and view it at apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 2 Technical Hotspots.
• Interface Component: tm_services_record_error - Open the component diagram for Interface Component: tm_services_record_error and view it at firmware/c6_companion/components/tm_services/tm_services.c Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots.
• Function Node: main - Open the component diagram of Function Node: main and view it at apps/linux_uconsole_gtk/tests/uconsole_meshtastic_node_payload_smoke.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: launchMapLayout - Open the component diagram of Function Node: launchMapLayout and view it at What type of technical objects are in apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_map_layout.cpp, what responsibilities they bear, whether the reference/call relationship and external dependency/call relationship create change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: companion_enter - Open the component diagram for Function Node: companion_enter and view it at apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 5 Sequence Diagrams.
• Function Node: expect - Open the component diagram of Function Node: expect and view it at apps/linux_uconsole_gtk/tests/uconsole_meshtastic_node_payload_smoke.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: makeSwitch - Open the component diagram of Function Node: makeSwitch and view it at apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: setLabel - Open the component diagram of Function Node: setLabel and view it at apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_widgets.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.
• Function Node: makeSpin - Open the component diagram of Function Node: makeSpin and view it at apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp Which type of technical object, what responsibilities it has, whether the reference/call relationship and external dependency/call relationship cause change pressure, and its relationship with the structure diagram, sequence and hotspots. You can continue to drill down to 3 Technical Hotspots.

Deployment Diagrams

• There are currently no specific maps generated based on the evidence.

Class / Structural Diagrams

• Structure Collaboration: Structural Slice boards · gat562_mesh_evb_pro/include/boards - Open Structural Collaboration: Structural Slice boards · gat562_mesh_evb_pro/include/boards, check whether the classes, interfaces and value objects in boards/gat562_mesh_evb_pro/include/boards jointly explain a business capability, shared support mechanism or adaptation boundary; if the common context cannot be explained, this diagram should be split or downgraded. You can continue to drill down to 1 Technical Hotspot.
• Structural collaboration: structural slice boards · t_echo_lite/include/boards - Open structural collaboration: structural slice boards · t_echo_lite/include/boards, view Whether the classes, interfaces and value objects in boards/t_echo_lite/include/boards jointly explain a business capability, shared support mechanism or adaptation boundary; if the common context cannot be explained, this diagram should be split or downgraded. You can continue to drill down to 2 Component Diagrams and 1 Technical Hotspot.
• Structural Collaboration: Structural Slicing boards · tab5/include/boards - Open Structural Collaboration: Structural Slicing boards · tab5/include/boards, view boards/tab5/include/boards Whether the classes, interfaces and value objects jointly explain a business capability, shared support mechanism or adaptation boundary; if they cannot explain the common context, this diagram should be split or downgraded. You can continue to drill down to 1 Technical Hotspot.
• Structural Collaboration: Structural Slicing boards · t_display_p4/include/boards - Open Structural Collaboration: Structural Slicing boards · t_display_p4/include/boards, view Whether the classes, interfaces and value objects in boards/t_display_p4/include/boards jointly explain a business capability, shared support mechanism or adaptation boundary; if the common context cannot be explained, this diagram should be split or downgraded. You can continue to drill down to 1 Technical Hotspot.
• Structural Collaboration: Structural Slicing boards · tlora_pager/include/boards - Open Structural Collaboration: Structural Slicing boards · tlora_pager/include/boards, view Do the classes, interfaces and value objects in boards/tlora_pager/include/boards jointly explain a business capability, shared support mechanism or adaptation boundary? If the common context cannot be explained, this diagram should be split or downgraded. You can continue to drill down to 1 Technical Hotspot.
• Structural Collaboration: Structural Slicing boards · tdeck/include/boards - Open Structural Collaboration: Structural Slicing boards · tdeck/include/boards, view boards/tdeck/include/boards Whether the classes, interfaces and value objects jointly explain a business capability, shared support mechanism or adaptation boundary; if they cannot explain the common context, this diagram should be split or downgraded. You can continue to drill down to 1 Technical Hotspot.
• Structure Collaboration: Structural Slice boards · tdeck_pro/include/boards - Open Structural Collaboration: Structural Slice boards · tdeck_pro/include/boards, view boards/tdeck_pro/include/boards Whether the classes, interfaces and value objects jointly explain a business capability, shared support mechanism or adaptation boundary; if they cannot explain the common context, this diagram should be split or downgraded. You can continue to drill down to 1 Technical Hotspot.
• Structural Collaboration: Structural Slicing boards · twatchs3/include/boards - Open Structural Collaboration: Structural Slicing boards · twatchs3/include/boards, view boards/twatchs3/include/boards Whether the classes, interfaces and value objects jointly explain a business capability, shared support mechanism or adaptation boundary; if they cannot explain the common context, this diagram should be split or downgraded. You can continue to drill down to 1 Technical Hotspot.
• Structure Collaboration: Structural Slices gat562_mesh_evb_pro · gat562_mesh_evb_pro - Open Structural Collaboration: Structural Slices gat562_mesh_evb_pro · gat562_mesh_evb_pro, check whether the classes, interfaces and value objects in boards/gat562_mesh_evb_pro jointly explain a business capability, shared support mechanism or adaptation boundary; if the common context cannot be explained, this diagram should be split or downgraded. You can continue to drill down to 1 Technical Hotspot.
• Structure Collaboration: Structural Slices t_echo_lite · t_echo_lite - Open Structural Collaboration: Structural Slices t_echo_lite · t_echo_lite, see boards/t_echo_lite Whether the classes, interfaces and value objects jointly explain a business capability, shared support mechanism or adaptation boundary; if they cannot explain the common context, this diagram should be split or downgraded. You can continue to drill down to 2 Component Diagrams and 1 Technical Hotspot.

Sequence Diagrams

• Dynamic collaboration: tick calls log_loop_interval - Open the dynamic collaboration fragment from tick to log_loop_interval and check what operational responsibilities this call has in related components, structural slices and business drill-downs.
• Dynamic collaboration: add_status_line calls add_label - Open the dynamic collaboration fragment from add_status_line to add_label and check what operational responsibilities this call has in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.
• Dynamic collaboration: add_u32_line calls add_label - Open the dynamic collaboration fragment from add_u32_line to add_label and check what operational responsibilities this call has in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.
• Dynamic collaboration: add_hex_line calls add_status_line - Open the dynamic collaboration fragment from add_hex_line to add_status_line and check what operational responsibilities this call has in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.
• Dynamic collaboration: companion_enter calls add_label - Open the dynamic collaboration fragment from companion_enter to add_label and check what operational responsibilities this call has in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.
• Dynamic collaboration: companion_enter calls add_status_line - Open the dynamic collaboration fragment from companion_enter to add_status_line and check what operational responsibilities this call has in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.
• Dynamic collaboration: companion_enter calls add_u32_line - Open the dynamic collaboration fragment from companion_enter to add_u32_line and check what operational responsibilities this call has in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.
• Dynamic collaboration: companion_enter calls add_hex_line - Open the dynamic collaboration fragment from companion_enter to add_hex_line and check what operational responsibilities this call has in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.
• Dynamic collaboration: startEsp32LvglLoopRuntime calls canStartEsp32LvglLoopRuntime - Open startEsp32LvglLoopRuntime to The dynamic collaboration fragment of canStartEsp32LvglLoopRuntime checks what running responsibilities this call assumes in related components, structural slices and business drill-downs.
• Dynamic collaboration: hasEsp32LvglRuntimeTargetProfile calls esp32LvglRuntimeTargetProfile - Open hasEsp32LvglRuntimeTargetProfile Dynamic collaboration fragment to esp32LvglRuntimeTargetProfile to check what running responsibilities this call has in related components, structural slices and business drill-downs.
• Dynamic collaboration: showBootUi calls lockUi - Open the dynamic collaboration fragment from showBootUi to lockUi and check what running responsibilities this call has in related components, structural slices, and business drill-downs. -Dynamic collaboration: showBootUi calls unlockUi - Open the dynamic collaboration fragment from showBootUi to unlockUi, and check what running responsibilities this call has in related components, structural slices, and business drill-downs.
• Dynamic collaboration: setBootLog calls lockUi - Open the dynamic collaboration fragment from setBootLog to lockUi and check what running responsibilities this call has in related components, structural slices, and business drill-downs. -Dynamic collaboration: setBootLog calls unlockUi - Open the dynamic collaboration fragment from setBootLog to unlockUi and check what running responsibilities this call has in related components, structural slices, and business drill-downs.
• Dynamic collaboration: canRunEsp32LvglStartupRuntime calls canStartEsp32LvglLoopRuntime - Open Dynamic collaboration fragment from canRunEsp32LvglStartupRuntime to canStartEsp32LvglLoopRuntime to check what running responsibilities this call assumes in related components, structural slices and business drill-downs.
• Dynamic collaboration: runEsp32LvglStartupRuntime calls canRunEsp32LvglStartupRuntime - Open Dynamic collaboration fragment from runEsp32LvglStartupRuntime to canRunEsp32LvglStartupRuntime to check what running responsibilities this call assumes in related components, structural slices and business drill-downs.
• Dynamic collaboration: runEsp32LvglStartupRuntime calls showBootUi - Open runEsp32LvglStartupRuntime to showBootUi Dynamic collaboration fragment, check what operational responsibilities this call has in related components, structural slices, and business drill-downs.
• Dynamic collaboration: runEsp32LvglStartupRuntime calls setBootLog - Open runEsp32LvglStartupRuntime to setBootLog Dynamic collaboration fragment, check what operational responsibilities this call has in related components, structural slices, and business drill-downs.

State Machine Diagrams

• There are currently no specific maps generated based on the evidence.

Technical Hotspots

• Large file: build.t_display_p4_tft/bootloader/config/kconfig_menus.json Technical Hotspots - Open Large file: build.t_display_p4_tft/bootloader/config/kconfig_menus.json Heat map of technical hot spots, check why build.t_display_p4_tft/bootloader/config/kconfig_menus.json may increase the cost of reading, modification, testing or regression, and reversely locate related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram.
• Large file: build.tdisplayp4_amoled/bootloader/config/kconfig_menus.json Technical Hotspots - Open Large file: build.tdisplayp4_amoled/bootloader/config/kconfig_menus.json Heat map of technical hot spots, check why build.tdisplayp4_amoled/bootloader/config/kconfig_menus.json may increase the cost of reading, modification, testing or regression, and reversely locate related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram.
• Large file: build.tdisplayp4_tft/bootloader/config/kconfig_menus.json Technical Hotspots - Open Large file: build.tdisplayp4_tft/bootloader/config/kconfig_menus.json Heat map of technical hot spots, check why build.tdisplayp4_tft/bootloader/config/kconfig_menus.json may increase the cost of reading, modification, testing or regression, and reversely locate related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram.
• Large file: managed_components/lvgl__lvgl/src/font/lv_font_montserrat_48.c Technical Hotspots - Open the heat map of the large file: managed_components/lvgl__lvgl/src/font/lv_font_montserrat_48.c. Check the heat map of managed_components/lvgl__lvgl/src/font/lv_font_montserrat_48.c to see why it may increase the cost of reading, modifying, testing or regression, and reversely locate the relevant package, component, structure or sequence. You can continue to drill down to 1 Package Diagram.
• Large file: build.c6_companion/bootloader/config/kconfig_menus.json Technical Hotspots - Open Large file: build.c6_companion/bootloader/config/kconfig_menus.json Heat map of technical hot spots, check why build.c6_companion/bootloader/config/kconfig_menus.json may increase the cost of reading, modification, testing or regression, and reversely locate related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram.
• Large file: managed_components/lvgl__lvgl/src/font/lv_font_montserrat_46.c Technical Hotspots - Open the heat map of the large file: managed_components/lvgl__lvgl/src/font/lv_font_montserrat_46.c. Check the heat map of managed_components/lvgl__lvgl/src/font/lv_font_montserrat_46.c to see why it may increase the cost of reading, modifying, testing or regression, and reversely locate the relevant package, component, structure or sequence. You can continue to drill down to 1 Package Diagram.
• Large file: managed_components/lvgl__lvgl/src/font/lv_font_montserrat_44.c Technical Hotspots - Open the heat map of the large file: managed_components/lvgl__lvgl/src/font/lv_font_montserrat_44.c. Check the heat map of managed_components/lvgl__lvgl/src/font/lv_font_montserrat_44.c to see why it may increase the cost of reading, modifying, testing or regression, and reversely locate the relevant package, component, structure or sequence. You can continue to drill down to 1 Package Diagram.
• Large file: managed_components/lvgl__lvgl/src/font/lv_font_montserrat_42.c Technical Hotspots - Open Large file: managed_components/lvgl__lvgl/src/font/lv_font_montserrat_42.c Heat map of technology hot spots, view why managed_components/lvgl__lvgl/src/font/lv_font_montserrat_42.c may increase the cost of reading, modification, testing or regression, and reversely locate related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram.
• Candidates for external collaboration: main technology hotspot - Open the heat map of Candidates for external collaboration: main technology hotspot to view apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp Why it may increase the cost of reading, modifying, testing or regression, and reverse locating related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram and 4 Component Diagrams.
• Widely reused candidate: contains technical hotspots - Open the heat map of widely reused candidate: contains technical hotspot and view it apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp Why it may increase the cost of reading, modifying, testing or regression, and reverse locating related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram and 4 Component Diagrams.
• Candidates for external collaboration: launchSettingsLayout Technology Hotspots - Open the heat map of Candidates for external collaboration: launchSettingsLayout Technology Hotspot to view apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp Why it may increase the cost of reading, modifying, testing or regression, and reverse locating related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram and 4 Component Diagrams.
• Widely reused candidate: makeLabel technical hotspots - Open the heat map of widely reused candidate: makeLabel technical hotspot, view apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_widgets.cpp Why it may increase the cost of reading, modifying, testing or regression, and reverse locating related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram and 2 Component Diagrams.
• Widely reused candidates: ../../lv_examples.h technical hotspots - Open the heat map of widely reused candidates: ../../lv_examples.h technical hotspots to view managed_components/lvgl__lvgl/examples/layouts/flex/lv_example_flex_1.c Why it may increase the cost of reading, modifying, testing or regression, and reverse locating related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram.
• Dependency cluster: boards technology hotspots - Open the heat map of dependency cluster: boards technology hotspot, see why boards may increase the cost of reading, modifying, testing or regression, and reversely locate related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram and 2 Class/Structural Diagrams.
• Candidates for external collaboration: boards/tlora_pager/src/tlora_pager_board.cpp Technical Hotspots - Open Candidates for external collaboration: boards/tlora_pager/src/tlora_pager_board.cpp Heat map of technical hot spots, see why boards/tlora_pager/src/tlora_pager_board.cpp may increase the cost of reading, modification, testing or regression, and reversely locate related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram and 2 Class/Structural Diagrams.
• Widely reused candidate: makeSettingsRow technical hotspots - Open the heat map of widely reused candidate: makeSettingsRow technical hotspot to view apps/linux_uconsole_gtk/src/platform/gtk/gtk_uconsole_settings_layout.cpp Why it may increase the cost of reading, modifying, testing or regression, and reverse locating related packages, components, structures or sequences. You can continue to drill down to 1 Package Diagram and 4 Component Diagrams.

Map Change History

0.1.30-alpha - 2026-06-25T09:19:20.669Z

Change type: DISCOVERY Git branch: main Git commit: 34aad0bffa Git workspace status: dirty

• Updated software structural model root index and split 84 concrete drawing documents.