Open the function node: main to confirm which specific object within apps/linux_cardputer_zero is responsible for entry, orchestration, adaptation, contract or sharing responsibilities. Focus on checking the code anchor apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, and whether its referenced/calling relationship and external dependency/calling relationship mean that changes will propagate.
function is located in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp#L49, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact.Praxis Software Structure Model
Module Boundaries: apps/linux_cardputer_zero
Explain the package/module boundaries, number of files, number of symbols and cross-module dependencies of apps/linux_cardputer_zero.
How to read pictures
- This Package Diagram is centered on apps/linux_cardputer_zero, 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, boards.
Technical complexity analysis
- apps/linux_cardputer_zero currently contains 24 files and 230 symbols belonging to technical organizational boundaries identified by the software architecture model.
- The cross-module relationship is as follows: it is referenced or called 40 times by other modules, and it actively depends on or calls external modules 11 times, so it is more dependent on other modules.
- Currently there is no obvious abnormality in external dependence, but specific business entrances should still be used to determine whether the direction of dependence is stable.
Relationship with business complexity
- apps/linux_cardputer_zero is not the business story itself, but the technical boundaries that may pass when business capabilities are implemented.
- If the evidence, entry or drill-down diagram of a Use Case in the organization/process model falls in apps/linux_cardputer_zero, 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 responsibilities of the module, rather than falling into this module because of the convenience of calling.
- Keep the module's dependency direction explainable to avoid forming an implicit public toolbox.
- When the business Use Case document references 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/linux_cardputer_zero"] dependency_1["apps/esp32_lvgl"] package_node --> dependency_1 dependency_2["boards"] package_node --> dependency_2
Coverage
- Module path: apps/linux_cardputer_zero
- Number of files: 24
- Number of symbols: 230
- Depends on or called by other modules: 40
- Depends on or calls external modules: 11
Drill down on semantic elements in the diagram
-
apps/linux_cardputer_zero
package
apps/linux_cardputer_zero is the central project boundary of the current Package Diagram, used to observe its own scale, dependency direction, and drill-down technical complexity.
- Technical roles
- Technical organization boundary: It aggregates the files, symbols and cross-module relationships under apps/linux_cardputer_zero into a discussable engineering unit.
- Why it appears
- The local repository evidence observes enough files, symbols, or cross-module relationships under apps/linux_cardputer_zero that it deserves to be promoted to a package-level entry in the software structure model.
- Relationship meaning
- The arrows pointing from apps/linux_cardputer_zero to other nodes in the figure indicate that the current boundary relies on external packages/modules; it is dependent or called 40 times by other modules and depends on or called external modules 11 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 on this node can continue to view the key components, structural collaboration slices, running links, deployment nodes and complexity hotspots within apps/linux_cardputer_zero to understand how this project boundary carries functional changes.
- Business correlation
- This node is not the business story itself, but the Use Case that falls into apps/linux_cardputer_zero in the organization/process model can refer to this as the technology bearing boundary. The current association is still CANDIDATE.
- Change impact
- Modifying the public entry, dependency direction or directory boundary of apps/linux_cardputer_zero 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/linux_cardputer_zero
- Module path: apps/linux_cardputer_zero
- Number of files: 24
- Number of symbols: 230
- Depends on or called by other modules: 40
- Depends on or calls external modules: 11
- apps/linux_cardputer_zero/APP_SHELL_MANIFEST.md
- apps/linux_cardputer_zero/CMakeLists.txt
Risk
- If you only regard this node as a directory name, you will miss its responsibility as a stable project boundary.
- If signs of dependence 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 technology boundary dependency of apps/linux_cardputer_zero; 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 roles
- 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/linux_cardputer_zero 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/linux_cardputer_zero -> apps/esp32_lvgl indicates that local repository evidence observes cross-module relationships; it explains the technical dependency direction, but does not directly prove the business process.
- Drill-down intention
- Drilling down into apps/esp32_lvgl, 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 correlation
- apps/linux_cardputer_zero 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.
- Change impact
- 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/linux_cardputer_zero.
- Confidence
- high
Evidence
- dependency edge: apps/linux_cardputer_zero -> 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 exists only for implementation convenience, future changes may cause boundary drift or implicit public toolboxes.
Problem
- Current evidence does not prove that apps/linux_cardputer_zero'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.
-
boards
package
boards is the currently observed external technology boundary dependency of apps/linux_cardputer_zero; 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 roles
- 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/linux_cardputer_zero and boards, so the dependency was put into the Package Diagram instead of just hidden in the code import/call.
- Relationship meaning
- apps/linux_cardputer_zero -> 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 dependency falls on the entry, runtime, tool registration, model adaptation or infrastructure boundary.
- Business correlation
- apps/linux_cardputer_zero If hosting 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.
- Change impact
- Modifying the public interface, path or operation mode of boards may cause chain changes in the call chain, packaging entry, agent workflow or UI behavior of apps/linux_cardputer_zero.
- Confidence
- high
Evidence
- dependency edge: apps/linux_cardputer_zero -> 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 exists only for implementation convenience, future changes may cause boundary drift or implicit public toolboxes.
Problem
- Current evidence does not demonstrate that apps/linux_cardputer_zero 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
Open the function node: contains to confirm which specific object within apps/linux_cardputer_zero is responsible for entry, orchestration, adaptation, contract or sharing responsibilities. Focus on checking the code anchor apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, and whether its referenced/calling relationship and external dependency/calling relationship mean that changes will propagate.
function is located in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp#L19. It is reused or relied on by multiple objects and is used to explain technical collaboration and change impact.Open the function node: not_contains to confirm which specific object within apps/linux_cardputer_zero is responsible for entry, orchestration, adaptation, contract or sharing responsibilities. Focus on checking the code anchor apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, and whether its referenced/calling relationship and external dependency/calling relationship mean that changes will propagate.
function is located in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp#L24. It is reused or relied on by multiple objects and is used to explain technical collaboration and the impact of changes.Open the function node: read_file to confirm which specific object within apps/linux_cardputer_zero is responsible for entry, orchestration, adaptation, contract or sharing responsibilities. Focus on checking the code anchor apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp, and whether its referenced/calling relationship and external dependency/calling relationship mean that changes will propagate.
function is located in apps/linux_cardputer_zero/tests/linux_cardputer_zero_business_wiring_smoke.cpp#L10. It is reused or relied on by multiple objects and is used to explain technical collaboration and change impact.View Candidates for External Collaboration: main Technology Hotspot Whether this complexity signal will increase the cost of reading, modifying, testing or regression of apps/linux_cardputer_zero.
This symbol connects multiple external objects or capabilities and may bear orchestration, aggregation, or overreach responsibilities.View widely reused candidates: contains Technical Hotspots Whether this complexity signal will increase the cost of reading, modifying, testing or regression of apps/linux_cardputer_zero.
This symbol is referenced or called by multiple codes, which may be a shared core, implicit interface or change diffusion point.Evidence
- 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
- apps/linux_cardputer_zero/src/cardputer_zero_input_method_port.h
Problem
- There are no open issues yet.