Module Boundary: apps/nrf52

How to read the diagram

This Package Diagram is centered on apps/nrf52_node, showing the file size, symbol size, and cross-module dependencies observed when it serves as a project module boundary.
The arrows in the figure represent the cross-module relationships observed by the local warehouse evidence, which are mainly used to understand the direction of technical dependencies; it is not the business process sequence, nor the runtime message timing.
The main external dependencies currently observed include: apps/esp32_lvgl, apps/linux_uconsole_gtk, apps/linux_cardputer_zero, boards.

Technical complexity analysis

apps/nrf52_node currently contains 23 files and 287 symbols belonging to the technical organization boundaries identified by the software architecture model.
The cross-module relationship is as follows: it is referenced or called by other modules 20 times, and it actively depends on or calls external modules 72 times, so it depends on external modules more.
More external dependencies may indicate that this module is responsible for orchestrating, aggregating or bridging multiple capabilities; it is currently handled as a candidate technology coupling center.

Relationship with business complexity

apps/nrf52_node is not the business story itself, but the technical boundaries that may be passed when business capabilities are implemented.
If the evidence, entry or drill-down diagram of a Use Case in the organization/process model falls on apps/nrf52_node, the Use Case should be linked back to this Package Diagram to indicate which engineering module the business story is hosted by.
The current association is still CANDIDATE: the technical boundaries can only be explained here based on warehouse evidence and cannot replace the confirmation of the business story, actors and business goals of the organizational/process model.

Governance Suggestions

When adding a new function, give priority to confirming that it belongs to the stable responsibility of the module, rather than falling into this module because of the convenience of calling.
If multiple changes in the future increase the external dependencies of this module, you should consider splitting the port, adapter or application service boundary.
When the business Use Case document refers to this module, the specific entry, call chain or configuration evidence should be recorded in the Use Case drill-down document.

UML/Technical Diagram

flowchart LR
  package_node["apps/nrf52_node"]
  dependency_1["apps/esp32_lvgl"]
  package_node --> dependency_1
  dependency_2["apps/linux_uconsole_gtk"]
  package_node --> dependency_2
  dependency_3["apps/linux_cardputer_zero"]
  package_node --> dependency_3
  dependency_4["boards"]
  package_node --> dependency_4

Coverage

Module path: apps/nrf52_node
Number of files: 23
Number of symbols: 287
Depends on or called by other modules: 20
Depends on or calls external modules: 72

Drill-down of semantic elements in the diagram

apps/nrf52_node package
apps/nrf52_node is the central project boundary of the current Package Diagram, used to observe its own scale, dependency direction and drill-down technical complexity.

Technical role
Technical organization boundary: It aggregates files, symbols and cross-module relationships under apps/nrf52_node into a discussable engineering unit.

Why it appears
The local repository evidence observes enough files, symbols, or cross-module relationships under apps/nrf52_node that it deserves to be promoted to a package-level entry in the software structure model.

Relationship meaning
The arrows pointing from apps/nrf52_node to other nodes in the figure indicate that the current boundary depends on external package/module; it is dependent or called 20 times by other modules and depends on or called external modules 72 times, which is used to determine whether it is more like a stable reuse boundary or an orchestration/bridging boundary.

Drill-down intention
Drilling down into this node can continue to view the key components, structural collaboration slices, running links, deployment nodes and complexity hotspots within apps/nrf52_node to understand how this engineering boundary carries functional changes.

Business association
This node is not the business story itself, but the Use Case that falls into apps/nrf52_node in the organization/process model can refer to this as the technology bearing boundary. The current association is still CANDIDATE.

Impact of change
Modifying the public entry, dependency direction, or directory boundary of apps/nrf52_node may affect the verification paths of component diagrams, sequence fragments, deployment configurations, and related business stories that reference it.

Confidence
high
Evidence
- package scope: apps/nrf52_node
- Module path: apps/nrf52_node
- Number of files: 23
- Number of symbols: 287
- Depends on or called by other modules: 20
- Depends on or calls external modules: 72
- apps/nrf52_node/APP_SHELL_MANIFEST.md
- apps/nrf52_node/library.json
Risk
- If you only regard this node as a directory name, you will miss its responsibility as a stable project boundary.
- If signs of dependency on external modules continue to increase, it may be a sign that the boundary is taking on too much orchestration or bridging responsibility.
Problem
- The current warehouse evidence has not yet explicitly traced the package to a Use Case; therefore, the business association remains a candidate.
apps/esp32_lvgl package
apps/esp32_lvgl is the currently observed external technical boundary dependency of apps/nrf52_node; it indicates that the current module is not implemented in isolation, but requires the help of another set of engineering capabilities to complete its responsibilities.

Technical role
Cross-module technology dependency boundary: The current package requires another package/module to provide capabilities, contracts, configuration or operation support.

Why it appears
Local repository evidence observed a cross-module factual relationship between apps/nrf52_node and apps/esp32_lvgl, so the dependency was put into the Package Diagram instead of just hidden in the code import/call.

Relationship meaning
apps/nrf52_node -> apps/esp32_lvgl indicates that local warehouse evidence observes cross-module relationships; it explains the technical dependency direction, but does not directly prove the business process.

Drill-down intention
Drill down into apps/esp32_lvgl to view its own Package Diagram, and then continue to enter its components, structures, sequences or hotspots to determine whether the current dependency falls on the entry, runtime, tool registration, model adaptation or infrastructure boundary.

Business association
apps/nrf52_node If hosting a user-visible capability, the dependency on apps/esp32_lvgl may be a runtime mechanism, an extension point, or a governance constraint for that capability. This business association needs to be confirmed by the Use Case evidence of the organization/process model.

Impact of change
Modifying the public interface, path or running mode of apps/esp32_lvgl may cause chain changes in the call chain, packaging entry, agent workflow or UI behavior of apps/nrf52_node.

Confidence
high
Evidence
- dependency edge: apps/nrf52_node -> apps/esp32_lvgl
- apps/esp32_lvgl/APP_SHELL_MANIFEST.md
- apps/esp32_lvgl/CMakeLists.txt
- apps/esp32_lvgl/library.json
- apps/esp32_lvgl/README.md
- apps/esp32_lvgl/src/esp32_lvgl_app_shell.cpp
- apps/esp32_lvgl/src/esp32_lvgl_app_shell.h
- apps/esp32_lvgl/src/esp32_lvgl_arduino_app_registry.cpp
Risk
- Cross-module dependencies can only prove technical relationships, but cannot directly prove business relationships.
- If this dependency only exists for implementation convenience, future changes may cause boundary drift or implicit public toolboxes.
Problem
- Current evidence does not demonstrate that apps/nrf52_node's dependence on apps/esp32_lvgl is directly related to a Use Case, runtime command, or configuration decision.
- The current dependency direction is a candidate according to the warehouse fact record, and no architectural decision document has been found to prove that it is a stable boundary.
apps/linux_uconsole_gtk package
apps/linux_uconsole_gtk is the currently observed external technology boundary dependency of apps/nrf52_node; it indicates that the current module is not implemented in isolation, but requires the help of another set of engineering capabilities to complete its responsibilities.

Technical role
Cross-module technology dependency boundary: The current package requires another package/module to provide capabilities, contracts, configuration or operation support.

Why it appears
Local repository evidence observed a cross-module factual relationship between apps/nrf52_node and apps/linux_uconsole_gtk, so the dependency was put into the Package Diagram instead of just hidden in the code import/call.

Relationship meaning
apps/nrf52_node -> apps/linux_uconsole_gtk represents local repository evidence of observed cross-module relationships; it explains the technical dependency direction, but does not directly prove the business process.

Drill-down intention
Drilling down into apps/linux_uconsole_gtk, you can view its own Package Diagram, and then continue to enter its components, structures, sequences or hotspots to determine whether the current dependency falls on the entry, runtime, tool registration, model adaptation or infrastructure boundary.

Business association
apps/nrf52_node If hosting a user-visible capability, the dependency on apps/linux_uconsole_gtk may be the operating mechanism, extension point, or governance constraint of that capability. This business association needs to be confirmed by the Use Case evidence of the organization/process model.

Impact of change
Modifying the public interface, path or running mode of apps/linux_uconsole_gtk may cause chain changes in the call chain, packaging entry, agent workflow or UI behavior of apps/nrf52_node.

Confidence
high
Evidence
- dependency edge: apps/nrf52_node -> apps/linux_uconsole_gtk
- apps/linux_uconsole_gtk/APP_SHELL_MANIFEST.md
- apps/linux_uconsole_gtk/CMakeLists.txt
- apps/linux_uconsole_gtk/packaging/trailmate-uconsole.desktop
- apps/linux_uconsole_gtk/packaging/trailmate-uconsole.png
- apps/linux_uconsole_gtk/README.md
- apps/linux_uconsole_gtk/src/linux_uconsole_gtk_app_shell.cpp
- apps/linux_uconsole_gtk/src/linux_uconsole_gtk_app_shell.h
Risk
- Cross-module dependencies can only prove technical relationships, but cannot directly prove business relationships.
- If this dependency only exists for implementation convenience, future changes may cause boundary drift or implicit public toolboxes.
Problem
- Current evidence does not demonstrate that apps/nrf52_node's dependence on apps/linux_uconsole_gtk is directly related to a Use Case, runtime command, or configuration decision.
- The current dependency direction is a candidate according to the warehouse fact record, and no architectural decision document has been found to prove that it is a stable boundary.
apps/linux_cardputer_zero package
apps/linux_cardputer_zero is the currently observed external technical boundary dependency of apps/nrf52_node; it indicates that the current module is not implemented in isolation, but requires the help of another set of engineering capabilities to complete its responsibilities.

Technical role
Cross-module technology dependency boundary: The current package requires another package/module to provide capabilities, contracts, configuration or operation support.

Why it appears
Local repository evidence observed a cross-module factual relationship between apps/nrf52_node and apps/linux_cardputer_zero, so the dependency was put into the Package Diagram instead of just hidden in the code import/call.

Relationship meaning
apps/nrf52_node -> apps/linux_cardputer_zero indicates that local warehouse evidence observes cross-module relationships; it explains the technical dependency direction, but does not directly prove the business process.

Drill-down intention
Drilling down apps/linux_cardputer_zero, you can view its own Package Diagram, and then continue to enter its components, structures, sequences or hotspots to determine whether the current dependency falls on the entrance, runtime, tool registration, model adaptation or infrastructure boundary.

Business association
apps/nrf52_node If hosting a user-visible capability, the dependency on apps/linux_cardputer_zero may be a runtime mechanism, an extension point, or a governance constraint for that capability. This business association needs to be confirmed by the Use Case evidence of the organization/process model.

Impact of change
Modifying the public interface, path or running mode of apps/linux_cardputer_zero may cause chain changes in the call chain, packaging entry, agent workflow or UI behavior of apps/nrf52_node.

Confidence
high
Evidence
- dependency edge: apps/nrf52_node -> apps/linux_cardputer_zero
- apps/linux_cardputer_zero/APP_SHELL_MANIFEST.md
- apps/linux_cardputer_zero/CMakeLists.txt
- apps/linux_cardputer_zero/packaging/trailmate-cardputer-zero-applaunch
- apps/linux_cardputer_zero/packaging/trailmate-cardputer-zero.desktop
- apps/linux_cardputer_zero/packaging/trailmate-cardputer-zero.png
- apps/linux_cardputer_zero/README.md
- apps/linux_cardputer_zero/src/cardputer_zero_input_method_port.cpp
Risk
- Cross-module dependencies can only prove technical relationships, but cannot directly prove business relationships.
- If this dependency only exists for implementation convenience, future changes may cause boundary drift or implicit public toolboxes.
Problem
- Current evidence does not demonstrate that apps/nrf52_node's dependence on apps/linux_cardputer_zero is directly related to a Use Case, runtime command, or configuration decision.
- The current dependency direction is a candidate according to the warehouse fact record, and no architectural decision document has been found to prove that it is a stable boundary.
boards package
boards is the currently observed external technical boundary dependency of apps/nrf52_node; it indicates that the current module is not implemented in isolation, but requires the help of another set of engineering capabilities to complete its responsibilities.

Technical role
Cross-module technology dependency boundary: The current package requires another package/module to provide capabilities, contracts, configuration or operation support.

Why it appears
Local repository evidence observes a cross-module factual relationship between apps/nrf52_node and boards, so the dependency is put into the Package Diagram instead of just hidden in the code import/call.

Relationship meaning
apps/nrf52_node -> boards represents local repository evidence of observed cross-module relationships; it explains technical dependency direction, but does not directly prove business processes.

Drill-down intention
Drill down into boards to view its own Package Diagram, and then continue to enter its components, structures, sequences or hotspots to determine whether the current dependencies fall on the entrance, runtime, tool registration, model adaptation or infrastructure boundary.

Business association
apps/nrf52_node If it carries a user-visible capability, the dependency on boards may be the operating mechanism, extension point, or governance constraint of the capability. This business association needs to be confirmed by the Use Case evidence of the organization/process model.

Impact of change
Modifying the public interface, path or operation mode of boards may cause chain changes in the calling chain, packaging entry, agent workflow or UI behavior of apps/nrf52_node.

Confidence
high
Evidence
- dependency edge: apps/nrf52_node -> boards
- boards/cardputerzero/board_facts.h
- boards/cardputerzero/BOARD.md
- boards/gat562_mesh_evb_pro.json
- boards/gat562_mesh_evb_pro/board_facts.h
- boards/gat562_mesh_evb_pro/BOARD.md
- boards/gat562_mesh_evb_pro/include/boards/gat562_mesh_evb_pro/board_profile.h
- boards/gat562_mesh_evb_pro/include/boards/gat562_mesh_evb_pro/gat562_board.h
Risk
- Cross-module dependencies can only prove technical relationships, but cannot directly prove business relationships.
- If this dependency only exists for implementation convenience, future changes may cause boundary drift or implicit public toolboxes.
Problem
- Current evidence does not demonstrate that apps/nrf52_node dependency boards are directly related to a Use Case, runtime command, or configuration decision.
- The current dependency direction is a candidate according to the warehouse fact record, and no architectural decision document has been found to prove that it is a stable boundary.

Drill-down UML

There is currently no evidence-based link to a finer picture.

Evidence

apps/nrf52_node/APP_SHELL_MANIFEST.md
apps/nrf52_node/library.json
apps/nrf52_node/README.md
apps/nrf52_node/src/nrf52_node_app_facade_runtime.cpp
apps/nrf52_node/src/nrf52_node_app_facade_runtime.h
apps/nrf52_node/src/nrf52_node_app_runtime_access.cpp
apps/nrf52_node/src/nrf52_node_app_runtime_access.h
apps/nrf52_node/src/nrf52_node_app_shell.cpp

Problem

There are no open issues yet.

How to read the diagram

Technical complexity analysis

Relationship with business complexity

Governance Suggestions

UML/Technical Diagram

Coverage

Drill-down of semantic elements in the diagram

Evidence

Risk

Problem

Evidence

Risk

Problem

Evidence

Risk

Problem

Evidence

Risk

Problem

Evidence

Risk

Problem

Drill-down UML

Evidence

Problem