Files

134 lines
29 KiB
HTML

<!doctype html>
<html lang="en">
<head><meta charset="utf-8" /><title>Container boundary: apps/linux_sim_shell</title></head>
<body>
<main class="praxis-architecture-map" data-praxis-anchor="architecture:c4:container:apps-linux_sim_shell" data-praxis-kind="architecture_c4_container" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-path="docs/architecture/c4/containers/apps-linux_sim_shell/container.html" data-praxis-drilldowns="{&quot;id&quot;:&quot;architecture:c4:code:apps-linux_sim_shell&quot;,&quot;level&quot;:&quot;code&quot;,&quot;title&quot;:&quot;Code anchor: apps/linux_sim_shell&quot;,&quot;summary&quot;:&quot;Explain a few key code anchors in apps/linux_sim_shell from the C4 Code layer. The Code layer is not a code browser and is only used when you need to understand how architectural components fall into specific files/symbols.&quot;,&quot;docPath&quot;:&quot;docs/architecture/c4/code/apps-linux_sim_shell/code.md&quot;,&quot;htmlPath&quot;:&quot;docs/architecture/c4/code/apps-linux_sim_shell/code.html&quot;,&quot;anchor&quot;:&quot;architecture:c4:code:apps-linux_sim_shell&quot;,&quot;relation&quot;:&quot;details&quot;,&quot;reason&quot;:&quot;Enter the code anchor point: apps/linux_sim_shell to trace the architectural responsibilities of the container boundary: apps/linux_sim_shell to the specific file/symbol anchor point; only when you need to determine the implementation entry or the impact of the change, you should drill down to Code.&quot;}">
<header class="praxis-design-map-header">
<p>Praxis Architecture View</p>
<h1>Container boundary: apps/linux_sim_shell</h1>
<p>apps/linux_sim_shell is a candidate boundary for the C4 Container layer: it must behave as an application, service, data store, runnable unit, or independently deployable/executable system part, rather than a normal directory, code layering, or shared collection of tools.</p>
<div class="meta-row">
<span>Container</span>
<span>candidate / high</span>
<span>0.1.30-alpha · 34aad0bffa2f / main</span>
</div>
</header>
<section class="semantic-layer" data-praxis-anchor="architecture:c4:layer-path" data-praxis-kind="architecture_c4_list">
<h2>C4 hierarchical path</h2>
<ul>
<li>Current layer: Container, which explains an independently understandable application, service, data storage or running unit within the target system.</li>
<li>Upper layer: System Context, indicating which target software system the Container belongs to.</li>
<li>Lower layer: Component, explaining the entrance, interface, orchestration, adaptation, contract or shared object inside the Container.</li>
</ul>
</section>
<section class="semantic-layer" data-praxis-anchor="architecture:c4:responsibility" data-praxis-kind="architecture_c4_text">
<h2>Responsibility</h2>
<p>apps/linux_sim_shell is an application-level Container candidate: warehouse evidence shows it is close to a runnable entry, a desktop/front-end/back-end application shell, or user-perceivable system capabilities.</p>
</section>
<section class="semantic-layer" data-praxis-anchor="architecture:c4:boundary" data-praxis-kind="architecture_c4_text">
<h2>Boundaries</h2>
<p>The boundary comes from the warehouse path apps/linux_sim_shell. C4 Container is not equal to any package or code layer; only boundaries with applications, services, data storage, runtime portals, deployment units, external interfaces or independent execution semantics enter this layer. Ordinary configuration files, document directories, CI directories, warehouse management files and pure code layering can only be used as evidence or software structure model objects, not as Containers.</p>
</section>
<section class="semantic-layer" data-praxis-anchor="architecture:c4:relationships" data-praxis-kind="architecture_c4_list">
<h2>Relationship</h2>
<ul>
<li>Depends on other Containers: apps/esp32_lvgl.</li>
<li>Contains 0 candidate component view objects, 0 run/collaboration links, and 0 run or build nodes.</li>
</ul>
</section>
<section class="semantic-layer" data-praxis-anchor="architecture:c4:business-relation" data-praxis-kind="architecture_c4_list">
<h2>Relationship with business complexity</h2>
<ul>
<li>This Container is not the business use case itself; it only explains the internal application/service/data storage/operation unit of the software system through which the business capability enters or passes.</li>
<li>If the Use Case in the organization/process model refers to this boundary, how it enters this Container should be explained in the Use Case drill-down document instead of writing the business process into the C4 Container diagram.</li>
</ul>
</section>
<section class="semantic-layer" data-praxis-anchor="architecture:c4:engineering-relation" data-praxis-kind="architecture_c4_list">
<h2>Correlation with technical complexity</h2>
<ul>
<li>Corresponds to the software structure model Package Diagram: docs/engineering/package-diagrams/apps-linux_sim_shell/package-diagram.html.</li>
<li>Continue to enter the software structure model to view drill-down UML, structural collaboration, running links and complexity candidate points.</li>
</ul>
</section>
<section class="semantic-layer diagram-section" data-praxis-anchor="architecture:c4:diagram" data-praxis-kind="architecture_c4_diagram">
<h2>C4 Container diagram</h2>
<pre class="mermaid" data-praxis-anchor="architecture:c4:container:apps-linux_sim_shell:c4" data-praxis-c4-current-level="container" data-praxis-c4-layer-views="[{&quot;level&quot;:&quot;system_context&quot;,&quot;label&quot;:&quot;System Context&quot;,&quot;title&quot;:&quot;System Context: trail-mate&quot;,&quot;diagramTitle&quot;:&quot;C4 System Context Diagram&quot;,&quot;summary&quot;:&quot;System Context only shows the relationship between the target software system and external people/systems, and does not directly expand the internal Container; what is highlighted here is the boundary of the software system to which \&quot;apps/linux_sim_shell\&quot; belongs.&quot;,&quot;docPath&quot;:&quot;docs/architecture/c4/system-context/system-context.md&quot;,&quot;htmlPath&quot;:&quot;docs/architecture/c4/system-context/system-context.html&quot;,&quot;mermaid&quot;:&quot;flowchart LR\n actor[\&quot;Unnamed external actor\&quot;]\n system[\&quot;trail-mate\&quot;]\n external[\&quot;Unnamed external system\&quot;]\n actor --&gt;|Use / Call| system\n system -.-&gt;|Candidate Integration| external&quot;,&quot;highlightLabels&quot;:[&quot;apps/linux_sim_shell&quot;,&quot;apps/linux_sim_shell Container&quot;,&quot;apps/linux_sim_shell (system internal Container)&quot;,&quot;linux_sim_shell&quot;,&quot;trail-mate&quot;],&quot;current&quot;:false,&quot;missing&quot;:false},{&quot;level&quot;:&quot;container&quot;,&quot;label&quot;:&quot;Container&quot;,&quot;title&quot;:&quot;Container boundary: apps/linux_sim_shell&quot;,&quot;diagramTitle&quot;:&quot;C4 Container diagram&quot;,&quot;summary&quot;:&quot;Currently reading the Container layer; the formal diagram below is the architectural projection of this layer.&quot;,&quot;docPath&quot;:&quot;docs/architecture/c4/containers/apps-linux_sim_shell/container.md&quot;,&quot;htmlPath&quot;:&quot;docs/architecture/c4/containers/apps-linux_sim_shell/container.html&quot;,&quot;mermaid&quot;:&quot;flowchart LR\n container[\&quot;apps/linux_sim_shell\&quot;]\n dependency_1[\&quot;apps/esp32_lvgl\&quot;]\n container --&gt; dependency_1&quot;,&quot;highlightLabels&quot;:[&quot;apps/linux_sim_shell&quot;,&quot;apps/linux_sim_shell Container&quot;,&quot;apps/linux_sim_shell (system internal Container)&quot;,&quot;linux_sim_shell&quot;],&quot;current&quot;:true,&quot;missing&quot;:false},{&quot;level&quot;:&quot;component&quot;,&quot;label&quot;:&quot;Component&quot;,&quot;title&quot;:&quot;apps/linux_sim_shell &#183; Component not generated&quot;,&quot;diagramTitle&quot;:&quot;C4 Component diagram&quot;,&quot;summary&quot;:&quot;The current object does not have a separate Component document; the generation process does not draw the level of insufficient evidence into a formal C4 diagram.&quot;,&quot;mermaid&quot;:&quot;flowchart LR\n focus[\&quot;apps/linux_sim_shell\&quot;]\n missing[\&quot;T\&quot;]\n focus -.-&gt; missing&quot;,&quot;highlightLabels&quot;:[&quot;apps/linux_sim_shell&quot;,&quot;apps/linux_sim_shell Container&quot;,&quot;apps/linux_sim_shell (system internal Container)&quot;,&quot;linux_sim_shell&quot;],&quot;current&quot;:false,&quot;missing&quot;:true},{&quot;level&quot;:&quot;code&quot;,&quot;label&quot;:&quot;Code&quot;,&quot;title&quot;:&quot;Code anchor: apps/linux_sim_shell&quot;,&quot;diagramTitle&quot;:&quot;C4 Code View diagram&quot;,&quot;summary&quot;:&quot;When switching to the Code layer, the corresponding position of \&quot;apps/linux_sim_shell\&quot; in the official document of this layer will be highlighted.&quot;,&quot;docPath&quot;:&quot;docs/architecture/c4/code/apps-linux_sim_shell/code.md&quot;,&quot;htmlPath&quot;:&quot;docs/architecture/c4/code/apps-linux_sim_shell/code.html&quot;,&quot;mermaid&quot;:&quot;flowchart TB\n package[\&quot;apps/linux_sim_shell\&quot;]\n file_1[\&quot;apps/linux_sim_shell/src/linux_sim_app_shell.h\&quot;]\n code_1[\&quot;LinuxSimAppShellConfig\&quot;]\n package --&gt; file_1\n file_1 --&gt; code_1\n file_2[\&quot;apps/linux_sim_shell/src/linux_sim_runtime_entry.h\&quot;]\n code_2[\&quot;LinuxSimRuntimeSource::ScreenGraphAdoption\&quot;]\n package --&gt; file_2\n file_2 --&gt; code_2\n file_3[\&quot;apps/linux_sim_shell/src/linux_sim_app_shell.cpp\&quot;]\n code_3[\&quot;&amp; LinuxSimAppShell::config() const\&quot;]\n package --&gt; file_3\n file_3 --&gt; code_3\n file_4[\&quot;apps/linux_sim_shell/src/linux_sim_runtime_entry.cpp\&quot;]\n code_4[\&quot;LinuxSimRuntimeEntry::screenCount\&quot;]\n package --&gt; file_4\n file_4 --&gt; code_4\n file_5[\&quot;apps/linux_sim_shell/src/linux_sim_runtime_entry.cpp\&quot;]\n code_5[\&quot;LinuxSimRuntimeEntry::usingPrimaryScreenGraph\&quot;]\n package --&gt; file_5\n file_5 --&gt; code_5\n file_6[\&quot;apps/linux_sim_shell/src/linux_sim_runtime_entry_adoption_probe.cpp\&quot;]\n code_6[\&quot;LinuxSimRuntimeEntryAdoptionProbe::screenCount\&quot;]\n package --&gt; file_6\n file_6 --&gt; code_6\n file_7[\&quot;apps/linux_sim_shell/src/linux_sim_runtime_renderer.cpp\&quot;]\n code_7[\&quot;LinuxSimRuntimeRenderer::usedPrimaryScreenGraph\&quot;]\n package --&gt; file_7\n file_7 --&gt; code_7\n file_8[\&quot;apps/linux_sim_shell/src/linux_sim_runtime_renderer.cpp\&quot;]\n code_8[\&quot;LinuxSimRuntimeRenderer::usingPrimaryScreenGraph\&quot;]\n package --&gt; file_8\n file_8 --&gt; code_8&quot;,&quot;highlightLabels&quot;:[&quot;apps/linux_sim_shell&quot;,&quot;apps/linux_sim_shell Container&quot;,&quot;apps/linux_sim_shell (system internal Container)&quot;,&quot;linux_sim_shell&quot;],&quot;current&quot;:false,&quot;missing&quot;:false}]">flowchart LR
container[&quot;apps/linux_sim_shell&quot;]
dependency_1[&quot;apps/esp32_lvgl&quot;]
container --&gt; dependency_1</pre>
</section>
<section class="semantic-layer architecture-c4-elements" data-praxis-anchor="architecture:c4:container:apps-linux_sim_shell:elements" data-praxis-kind="architecture_c4_elements">
<h2>Explanation of elements in the diagram</h2>
<div class="layer-grid">
<article class="layer-card" data-praxis-anchor="architecture:c4:container:apps-linux_sim_shell:self" data-praxis-kind="architecture_c4_element" data-praxis-confidence="high" data-praxis-drilldowns="{&quot;id&quot;:&quot;architecture:c4:code:apps-linux_sim_shell&quot;,&quot;level&quot;:&quot;code&quot;,&quot;title&quot;:&quot;Code anchor: apps/linux_sim_shell&quot;,&quot;summary&quot;:&quot;Explain a few key code anchors in apps/linux_sim_shell from the C4 Code layer. The Code layer is not a code browser and is only used when you need to understand how architectural components fall into specific files/symbols.&quot;,&quot;docPath&quot;:&quot;docs/architecture/c4/code/apps-linux_sim_shell/code.md&quot;,&quot;htmlPath&quot;:&quot;docs/architecture/c4/code/apps-linux_sim_shell/code.html&quot;,&quot;anchor&quot;:&quot;architecture:c4:code:apps-linux_sim_shell&quot;,&quot;relation&quot;:&quot;details&quot;,&quot;reason&quot;:&quot;Enter the code anchor point: apps/linux_sim_shell to trace the architectural responsibilities of the container boundary: apps/linux_sim_shell to the specific file/symbol anchor point; only when you need to determine the implementation entry or the impact of the change, you should drill down to Code.&quot;}">
<h3>apps/linux_sim_shell</h3>
<p>Container · high</p>
<p>This node in the diagram represents the C4 Container of apps/linux_sim_shell; the current document records 0 component drill-down entries, 0 running collaboration threads and 0 running or build nodes.</p>
<dl>
<div><dt>Responsibility</dt><dd>apps/linux_sim_shell is an application-level Container candidate: warehouse evidence shows it is close to a runnable entry, a desktop/front-end/back-end application shell, or user-perceivable system capabilities.</dd></div>
<div><dt>Boundaries</dt><dd>The boundary comes from the warehouse path apps/linux_sim_shell; the entry, service interface, application code, running configuration and deployment evidence under this path jointly support it to enter the Container layer. Ordinary configuration files, document directories or pure code layers will not form a Container alone.</dd></div>
<div><dt>Relationship meaning</dt><dd>The figure points from apps/linux_sim_shell to the external boundary, indicating that this runnable boundary will call, reference or depend on other Containers; these relationships are used to determine deployment, interfaces and change impacts.</dd></div>
<div><dt>Why it belongs to this layer</dt><dd>The node enters the Container layer because the local warehouse evidence shows that it has applications, services, data storage, running portals, deployment units, external interfaces, or independent execution semantics; not because it is just a directory or package.</dd></div>
<div><dt>Drill-down intention</dt><dd>Drill down from apps/linux_sim_shell to Component to view the decomposition of responsibilities within the boundary.</dd></div>
</dl>
</article>
<article class="layer-card" data-praxis-anchor="architecture:c4:container:apps-linux_sim_shell:dep:apps-esp32_lvgl" data-praxis-kind="architecture_c4_element" data-praxis-confidence="medium" data-praxis-drilldowns="[]">
<h3>apps/esp32_lvgl</h3>
<p>Container · medium</p>
<p>apps/linux_sim_shell depends on apps/esp32_lvgl.</p>
<dl>
<div><dt>Responsibility</dt><dd>apps/linux_sim_shell depends on apps/esp32_lvgl.</dd></div>
<div><dt>Boundaries</dt><dd>apps/esp32_lvgl does not belong to the internal boundaries of apps/linux_sim_shell; it is just a dependent adjacent module in the current graph.</dd></div>
<div><dt>Relationship meaning</dt><dd>apps/linux_sim_shell -> apps/esp32_lvgl indicates that there are cross-border calls, references or configuration dependencies in the local warehouse evidence; it illustrates the direction of technical collaboration, but cannot independently prove the business process relationship.</dd></div>
<div><dt>Why it belongs to this layer</dt><dd>apps/esp32_lvgl is projected as an adjacent Container candidate by path ownership, rather than apps/linux_sim_shell internal Component.</dd></div>
<div><dt>Drill-down intention</dt><dd>Enter the independent Container document of apps/esp32_lvgl to view its own responsibilities and evidence; if there is no independent document, it will only be regarded as an external dependency fact.</dd></div>
</dl>
</article>
</div>
</section>
<section class="semantic-layer architecture-c4-links" data-praxis-anchor="architecture:c4:drilldowns" data-praxis-kind="architecture_c4_links">
<h2>Can drill down to C4</h2>
<div class="layer-grid">
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="architecture:c4:code:apps-linux_sim_shell" data-praxis-kind="architecture_c4_link" data-praxis-document-title="Code anchor point: apps/linux_sim_shell" data-praxis-document-summary="Enter the code anchor point: apps/linux_sim_shell to trace the architectural responsibilities of the container boundary: apps/linux_sim_shell to the specific file/symbol anchor point; only when you need to determine the implementation entry or the impact of the change, you should drill down to Code." data-praxis-document-md="docs/architecture/c4/code/apps-linux_sim_shell/code.md" data-praxis-document-html="docs/architecture/c4/code/apps-linux_sim_shell/code.html">
<strong>Code anchor: apps/linux_sim_shell</strong>
<span>details</span>
<p>Enter the code anchor point: apps/linux_sim_shell to trace the architectural responsibilities of the container boundary: apps/linux_sim_shell to the specific file/symbol anchor point; only when you need to determine the implementation entry or the impact of the change, you should drill down to Code.</p>
<small>Explain a few key code anchors in apps/linux_sim_shell from the C4 Code layer. The Code layer is not a code browser and is only used when you need to understand how architectural components fall into specific files/symbols.</small>
</article>
</div>
</section>
<section class="semantic-layer architecture-c4-links" data-praxis-anchor="architecture:c4:engineering-links" data-praxis-kind="architecture_c4_links">
<h2>Associated software structure model</h2>
<div class="layer-grid">
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="architecture:c4:engineering-link:docs-engineering-package-diagrams-apps-linux_sim_shell-package-diagram" data-praxis-kind="architecture_c4_link" data-praxis-document-title="apps/linux_sim_shell Package Diagram" data-praxis-document-summary="View the boundaries, dependencies and complexity candidates of the software structure package/module to which the Container belongs." data-praxis-document-md="docs/engineering/package-diagrams/apps-linux_sim_shell/package-diagram.md" data-praxis-document-html="docs/engineering/package-diagrams/apps-linux_sim_shell/package-diagram.html">
<strong>apps/linux_sim_shell Package Diagram</strong>
<span>related_engineering</span>
<p>View the boundaries, dependencies and complexity candidates of the software structure package/module to which the Container belongs.</p>
<small>View the boundaries, dependencies and complexity candidates of the software structure package/module to which the Container belongs.</small>
</article>
</div>
</section>
<section class="semantic-layer" data-praxis-anchor="architecture:c4:evidence" data-praxis-kind="architecture_c4_list">
<h2>Evidence</h2>
<ul>
<li>apps/linux_sim_shell/APP_SHELL_MANIFEST.md</li>
<li>apps/linux_sim_shell/CMakeLists.txt</li>
<li>apps/linux_sim_shell/README.md</li>
<li>apps/linux_sim_shell/src/linux_sim_app_shell.cpp</li>
<li>apps/linux_sim_shell/src/linux_sim_app_shell.h</li>
<li>apps/linux_sim_shell/src/linux_sim_runtime_entry_adoption_probe.cpp</li>
<li>apps/linux_sim_shell/src/linux_sim_runtime_entry_adoption_probe.h</li>
<li>apps/linux_sim_shell/src/linux_sim_runtime_entry.cpp</li>
</ul>
</section>
<section class="semantic-layer" data-praxis-anchor="architecture:c4:questions" data-praxis-kind="architecture_c4_list">
<h2>Judgment basis</h2>
<ul>
<li>This boundary must be supported by running entry, build/deployment configuration, service interface, application entry, data storage or independent execution evidence; directory name, number of files or number of dependencies alone are not enough to establish.</li>
<li>When there is a lack of running, deployment, interface or data storage evidence, the generation process will reduce the confidence or not generate independent Containers.</li>
</ul>
</section>
<script type="application/json" id="praxis-architecture-c4-document">{"id":"architecture:c4:container:apps-linux_sim_shell","level":"container","title":"Container boundary: apps/linux_sim_shell","summary":"apps/linux_sim_shell is a candidate boundary for the C4 Container layer: it must behave as an application, service, data store, runnable unit, or independently deployable/executable system part, rather than a normal directory, code layering, or shared collection of tools.","docPath":"docs/architecture/c4/containers/apps-linux_sim_shell/container.md","htmlPath":"docs/architecture/c4/containers/apps-linux_sim_shell/container.html","anchor":"architecture:c4:container:apps-linux_sim_shell","status":"candidate","confidence":"high","mermaid":"flowchart LR\n container[\"apps/linux_sim_shell\"]\n dependency_1[\"apps/esp32_lvgl\"]\n container --> dependency_1","responsibility":"apps/linux_sim_shell is an application-level Container candidate: warehouse evidence shows it is close to a runnable entry, a desktop/front-end/back-end application shell, or user-perceivable system capabilities.","boundary":"The boundary comes from the warehouse path apps/linux_sim_shell. C4 Container is not equal to any package or code layer; only boundaries with applications, services, data storage, runtime portals, deployment units, external interfaces or independent execution semantics enter this layer. Ordinary configuration files, document directories, CI directories, warehouse management files and pure code layering can only be used as evidence or software structure model objects, not as Containers.","relationships":["Depends on other Containers: apps/esp32_lvgl.","Contains 0 candidate component view objects, 0 run/collaboration links, and 0 run or build nodes."],"businessRelation":["This Container is not the business use case itself; it only explains the internal application/service/data storage/operation unit of the software system through which the business capability enters or passes.","If the Use Case in the organization/process model refers to this boundary, how it enters this Container should be explained in the Use Case drill-down document instead of writing the business process into the C4 Container diagram."],"engineeringRelation":["Corresponds to the software structure model Package Diagram: docs/engineering/package-diagrams/apps-linux_sim_shell/package-diagram.html.","Continue to enter the software structure model to view drill-down UML, structural collaboration, running links and complexity candidate points."],"evidencePaths":["apps/linux_sim_shell/APP_SHELL_MANIFEST.md","apps/linux_sim_shell/CMakeLists.txt","apps/linux_sim_shell/README.md","apps/linux_sim_shell/src/linux_sim_app_shell.cpp","apps/linux_sim_shell/src/linux_sim_app_shell.h","apps/linux_sim_shell/src/linux_sim_runtime_entry_adoption_probe.cpp","apps/linux_sim_shell/src/linux_sim_runtime_entry_adoption_probe.h","apps/linux_sim_shell/src/linux_sim_runtime_entry.cpp"],"questions":["This boundary must be supported by running entry, build/deployment configuration, service interface, application entry, data storage or independent execution evidence; directory name, number of files or number of dependencies alone are not enough to establish.","When there is a lack of running, deployment, interface or data storage evidence, the generation process will reduce the confidence or not generate independent Containers."],"scope":{"packageId":"apps/linux_sim_shell","filePath":"apps/linux_sim_shell"},"elements":[{"id":"architecture:c4:container:apps-linux_sim_shell:self","label":"apps/linux_sim_shell","level":"container","anchor":"architecture:c4:container:apps-linux_sim_shell:self","summary":"This node in the diagram represents the C4 Container of apps/linux_sim_shell; the current document records 0 component drill-down entries, 0 running collaboration threads and 0 running or build nodes.","responsibility":"apps/linux_sim_shell is an application-level Container candidate: warehouse evidence shows it is close to a runnable entry, a desktop/front-end/back-end application shell, or user-perceivable system capabilities.","boundary":"The boundary comes from the warehouse path apps/linux_sim_shell; the entry, service interface, application code, running configuration and deployment evidence under this path jointly support it to enter the Container layer. Ordinary configuration files, document directories or pure code layers will not form a Container alone.","relationshipMeaning":"The figure points from apps/linux_sim_shell to the external boundary, indicating that this runnable boundary will call, reference or depend on other Containers; these relationships are used to determine deployment, interfaces and change impacts.","whyThisLevel":"The node enters the Container layer because the local warehouse evidence shows that it has applications, services, data storage, running portals, deployment units, external interfaces, or independent execution semantics; not because it is just a directory or package.","drilldownIntent":"Drill down from apps/linux_sim_shell to Component to view the decomposition of responsibilities within the boundary.","evidence":["apps/linux_sim_shell/APP_SHELL_MANIFEST.md","apps/linux_sim_shell/CMakeLists.txt","apps/linux_sim_shell/README.md","apps/linux_sim_shell/src/linux_sim_app_shell.cpp","apps/linux_sim_shell/src/linux_sim_app_shell.h","apps/linux_sim_shell/src/linux_sim_runtime_entry_adoption_probe.cpp","apps/linux_sim_shell/src/linux_sim_runtime_entry_adoption_probe.h","apps/linux_sim_shell/src/linux_sim_runtime_entry.cpp"],"confidence":"high","drilldowns":[{"id":"architecture:c4:code:apps-linux_sim_shell","level":"code","title":"Code anchor: apps/linux_sim_shell","summary":"Explain a few key code anchors in apps/linux_sim_shell from the C4 Code layer. The Code layer is not a code browser and is only used when you need to understand how architectural components fall into specific files/symbols.","docPath":"docs/architecture/c4/code/apps-linux_sim_shell/code.md","htmlPath":"docs/architecture/c4/code/apps-linux_sim_shell/code.html","anchor":"architecture:c4:code:apps-linux_sim_shell","relation":"details","reason":"Enter the code anchor point: apps/linux_sim_shell to trace the architectural responsibilities of the container boundary: apps/linux_sim_shell to the specific file/symbol anchor point; only when you need to determine the implementation entry or the impact of the change, you should drill down to Code."}]},{"id":"architecture:c4:container:apps-linux_sim_shell:dep:apps-esp32_lvgl","label":"apps/esp32_lvgl","level":"container","anchor":"architecture:c4:container:apps-linux_sim_shell:dep:apps-esp32_lvgl","summary":"apps/linux_sim_shell depends on apps/esp32_lvgl.","responsibility":"apps/linux_sim_shell depends on apps/esp32_lvgl.","boundary":"apps/esp32_lvgl does not belong to the internal boundaries of apps/linux_sim_shell; it is just a dependent adjacent module in the current graph.","relationshipMeaning":"apps/linux_sim_shell -> apps/esp32_lvgl indicates that there are cross-boundary calls, references or configuration dependencies in the local warehouse evidence; it illustrates the direction of technical collaboration, but cannot independently prove the business process relationship.","whyThisLevel":"apps/esp32_lvgl is projected as an adjacent Container candidate by path ownership, rather than apps/linux_sim_shell internal Component.","drilldownIntent":"Enter the independent Container document of apps/esp32_lvgl to view its own responsibilities and evidence; if there is no independent document, it will only be regarded as an external dependency fact.","evidence":["dependency edge: apps/linux_sim_shell -> apps/esp32_lvgl"],"confidence":"medium","drilldowns":[]}],"drilldowns":[{"id":"architecture:c4:code:apps-linux_sim_shell","level":"code","title":"Code anchor: apps/linux_sim_shell","summary":"Explain a few key code anchors in apps/linux_sim_shell from the C4 Code layer. The Code layer is not a code browser and is only used when you need to understand how architectural components fall into specific files/symbols.","docPath":"docs/architecture/c4/code/apps-linux_sim_shell/code.md","htmlPath":"docs/architecture/c4/code/apps-linux_sim_shell/code.html","anchor":"architecture:c4:code:apps-linux_sim_shell","relation":"details","reason":"Enter the code anchor point: apps/linux_sim_shell to trace the architectural responsibilities of the container boundary: apps/linux_sim_shell to the specific file/symbol anchor point; only when you need to determine the implementation entry or the impact of the change, you should drill down to Code."}],"relatedEngineeringDocs":[{"id":"architecture:c4:engineering-link:docs-engineering-package-diagrams-apps-linux_sim_shell-package-diagram","level":"code","title":"apps/linux_sim_shell Package Diagram","summary":"View the boundaries, dependencies and complexity candidates of the software structure package/module to which the Container belongs.","docPath":"docs/engineering/package-diagrams/apps-linux_sim_shell/package-diagram.md","htmlPath":"docs/engineering/package-diagrams/apps-linux_sim_shell/package-diagram.html","anchor":"architecture:c4:engineering-link:docs-engineering-package-diagrams-apps-linux_sim_shell-package-diagram","relation":"related_engineering","reason":"View the boundaries, dependencies and complexity candidates of the software structure package/module to which the Container belongs."}]}</script>
</main>
</body>
</html>