mirror of
https://github.com/vicliu624/trail-mate.git
synced 2026-08-28 13:34:07 +00:00
111 lines
207 KiB
HTML
111 lines
207 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<title>Sequence Diagrams</title>
|
|
</head>
|
|
<body>
|
|
<main class="praxis-engineering-map" data-praxis-anchor="engineering:category:sequence" data-praxis-kind="engineering_category_map" data-praxis-status="candidate" data-praxis-confidence="high">
|
|
<header class="praxis-design-map-header">
|
|
<p>Praxis Software Structure Model</p>
|
|
<h1>Sequence Diagrams</h1>
|
|
<p>A runtime collaboration fragment restored by a real call relationship.</p>
|
|
</header>
|
|
<section class="semantic-layer engineering-category-items" data-praxis-anchor="engineering:category-items" data-praxis-kind="engineering_category_items">
|
|
<div class="layer-grid">
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:tick:log_loop_interval:apps-esp32_lvgl-src-esp32_lvgl_arduino_loop_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_arduino_loop_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: tick calls log_loop_interval" data-praxis-document-summary="Open the dynamic collaboration fragment from tick to log_loop_interval, and check what running responsibilities this call assumes in related components, structure slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/tick-calls-log_loop_interval/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/tick-calls-log_loop_interval/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: tick calls log_loop_interval</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from tick to log_loop_interval, and check what running responsibilities this call assumes in related components, structure slices, and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:add_status_line:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: add_status_line calls add_label" data-praxis-document-summary="Open the dynamic collaboration fragment from add_status_line to add_label and check what operational responsibilities this call has in related components, structure slices and business drill-downs. You can continue to drill down to 1 Component Diagram." data-praxis-document-md="docs/engineering/sequence-diagrams/add_status_line-calls-add_label/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/add_status_line-calls-add_label/sequence-diagram.html" data-praxis-drilldowns="{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}">
|
|
<h3>Dynamic collaboration: add_status_line calls add_label</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from add_status_line to add_label, and check what operational responsibilities this call has in related components, structure slices, and business drill-downs. You can continue to drill down to 1 Component Diagram.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:add_u32_line:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: add_u32_line calls add_label" data-praxis-document-summary="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." data-praxis-document-md="docs/engineering/sequence-diagrams/add_u32_line-calls-add_label/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/add_u32_line-calls-add_label/sequence-diagram.html" data-praxis-drilldowns="{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}">
|
|
<h3>Dynamic collaboration: add_u32_line calls add_label</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>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.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:add_hex_line:add_status_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: add_hex_line calls add_status_line" data-praxis-document-summary="Open the dynamic collaboration fragment from add_hex_line to add_status_line and check what running responsibilities this call assumes in related components, structure slices and business drill-downs. You can continue to drill down to 1 Component Diagram." data-praxis-document-md="docs/engineering/sequence-diagrams/add_hex_line-calls-add_status_line/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/add_hex_line-calls-add_status_line/sequence-diagram.html" data-praxis-drilldowns="{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}">
|
|
<h3>Dynamic collaboration: add_hex_line calls add_status_line</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from add_hex_line to add_status_line and check what running responsibilities this call has in related components, structure slices and business drill-downs. You can continue to drill down to 1 Component Diagram.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:companion_enter:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: companion_enter calls add_label" data-praxis-document-summary="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." data-praxis-document-md="docs/engineering/sequence-diagrams/companion_enter-calls-add_label/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/companion_enter-calls-add_label/sequence-diagram.html" data-praxis-drilldowns="{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}">
|
|
<h3>Dynamic collaboration: companion_enter calls add_label</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from companion_enter to add_label, and check what running responsibilities this call has in related components, structural slices, and business drill-downs. You can continue to drill down to 1 Component Diagram.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:companion_enter:add_status_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: companion_enter calls add_status_line" data-praxis-document-summary="Open the dynamic collaboration fragment from companion_enter to add_status_line, and check what running responsibilities this call assumes in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram." data-praxis-document-md="docs/engineering/sequence-diagrams/companion_enter-calls-add_status_line/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/companion_enter-calls-add_status_line/sequence-diagram.html" data-praxis-drilldowns="{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}">
|
|
<h3>Dynamic collaboration: companion_enter calls add_status_line</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from companion_enter to add_status_line, and check what running responsibilities this call assumes in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:companion_enter:add_u32_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: companion_enter calls add_u32_line" data-praxis-document-summary="Open the dynamic collaboration fragment from companion_enter to add_u32_line, and check what running responsibilities this call assumes in related components, structural slices, and business drill-downs. You can continue to drill down to 1 Component Diagram." data-praxis-document-md="docs/engineering/sequence-diagrams/companion_enter-calls-add_u32_line/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/companion_enter-calls-add_u32_line/sequence-diagram.html" data-praxis-drilldowns="{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}">
|
|
<h3>Dynamic collaboration: companion_enter calls add_u32_line</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from companion_enter to add_u32_line, and check what running responsibilities this call assumes in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:companion_enter:add_hex_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: companion_enter calls add_hex_line" data-praxis-document-summary="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." data-praxis-document-md="docs/engineering/sequence-diagrams/companion_enter-calls-add_hex_line/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/companion_enter-calls-add_hex_line/sequence-diagram.html" data-praxis-drilldowns="{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}">
|
|
<h3>Dynamic collaboration: companion_enter calls add_hex_line</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from companion_enter to add_hex_line and check what running responsibilities this call has in related components, structural slices and business drill-downs. You can continue to drill down to 1 Component Diagram.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:startesp32lvglloopruntime:canstartesp32lvglloopruntime:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: startEsp32LvglLoopRuntime calls canStartEsp32LvglLoopRuntime" data-praxis-document-summary="Open the dynamic collaboration fragment from startEsp32LvglLoopRuntime to canStartEsp32LvglLoopRuntime, and check what running responsibilities this call assumes in related components, structural slices and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/startesp32lvglloopruntime-calls-canstartesp32lvglloopruntime/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/startesp32lvglloopruntime-calls-canstartesp32lvglloopruntime/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: startEsp32LvglLoopRuntime calls canStartEsp32LvglLoopRuntime</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from startEsp32LvglLoopRuntime to canStartEsp32LvglLoopRuntime, and check what running responsibilities this call assumes in related components, structural slices and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:hasesp32lvglruntimetargetprofile:esp32lvglruntimetargetprofile:apps-esp32_lvgl-src-esp32_lvgl_runtime_config.cpp:apps-esp32_lvgl-src-esp32_lvgl_runtime_config.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: hasEsp32LvglRuntimeTargetProfile calls esp32LvglRuntimeTargetProfile" data-praxis-document-summary="Open the dynamic collaboration fragment from hasEsp32LvglRuntimeTargetProfile to esp32LvglRuntimeTargetProfile, and check what running responsibilities this call assumes in related components, structural slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/hasesp32lvglruntimetargetprofile-calls-esp32lvglruntimetargetprofile/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/hasesp32lvglruntimetargetprofile-calls-esp32lvglruntimetargetprofile/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: hasEsp32LvglRuntimeTargetProfile calls esp32LvglRuntimeTargetProfile</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open hasEsp32LvglRuntimeTargetProfile to esp32LvglRuntimeTargetProfile Dynamic collaboration fragment, check what operational responsibilities this call has in related components, structural slices, and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:showbootui:lockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: showBootUi calls lockUi" data-praxis-document-summary="Open the dynamic collaboration fragment from showBootUi to lockUi, and check what running responsibilities this call assumes in related components, structural slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/showbootui-calls-lockui/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/showbootui-calls-lockui/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: showBootUi calls lockUi</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from showBootUi to lockUi, and check what running responsibilities this call assumes in related components, structure slices, and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:showbootui:unlockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: showBootUi calls unlockUi" data-praxis-document-summary="Open the dynamic collaboration fragment from showBootUi to unlockUi, and check what running responsibilities this call assumes in related components, structure slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/showbootui-calls-unlockui/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/showbootui-calls-unlockui/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: showBootUi calls unlockUi</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from showBootUi to unlockUi, and check what running responsibilities this call assumes in related components, structure slices, and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:setbootlog:lockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: setBootLog calls lockUi" data-praxis-document-summary="Open the dynamic collaboration fragment from setBootLog to lockUi, and check what running responsibilities this call assumes in related components, structural slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/setbootlog-calls-lockui/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/setbootlog-calls-lockui/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: setBootLog calls lockUi</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from setBootLog to lockUi, and check what running responsibilities this call assumes in related components, structural slices, and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:setbootlog:unlockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: setBootLog calls unlockUi" data-praxis-document-summary="Open the dynamic collaboration fragment from setBootLog to unlockUi, and check what running responsibilities this call assumes in related components, structural slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/setbootlog-calls-unlockui/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/setbootlog-calls-unlockui/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: setBootLog calls unlockUi</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from setBootLog to unlockUi, and check what running responsibilities this call assumes in related components, structural slices, and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:canrunesp32lvglstartupruntime:canstartesp32lvglloopruntime:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: canRunEsp32LvglStartupRuntime calls canStartEsp32LvglLoopRuntime" data-praxis-document-summary="Open canRunEsp32LvglStartupRuntime to canStartEsp32LvglLoopRuntime Dynamic collaboration fragment, check what operational responsibilities this call has in related components, structural slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/canrunesp32lvglstartupruntime-calls-canstartesp32lvglloopruntime/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/canrunesp32lvglstartupruntime-calls-canstartesp32lvglloopruntime/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: canRunEsp32LvglStartupRuntime calls canStartEsp32LvglLoopRuntime</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open canRunEsp32LvglStartupRuntime to canStartEsp32LvglLoopRuntime Dynamic collaboration fragment, check what operational responsibilities this call has in related components, structural slices, and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:runesp32lvglstartupruntime:canrunesp32lvglstartupruntime:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: runEsp32LvglStartupRuntime calls canRunEsp32LvglStartupRuntime" data-praxis-document-summary="Open the dynamic collaboration fragment from runEsp32LvglStartupRuntime to canRunEsp32LvglStartupRuntime, and check what running responsibilities this call assumes in related components, structure slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-canrunesp32lvglstartupruntime/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-canrunesp32lvglstartupruntime/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: runEsp32LvglStartupRuntime calls canRunEsp32LvglStartupRuntime</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from runEsp32LvglStartupRuntime to canRunEsp32LvglStartupRuntime and check what running responsibilities this call assumes in related components, structural slices and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:runesp32lvglstartupruntime:showbootui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: runEsp32LvglStartupRuntime calls showBootUi" data-praxis-document-summary="Open the dynamic collaboration fragment from runEsp32LvglStartupRuntime to showBootUi, and check what running responsibilities this call assumes in related components, structure slices, and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-showbootui/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-showbootui/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: runEsp32LvglStartupRuntime calls showBootUi</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>Open the dynamic collaboration fragment from runEsp32LvglStartupRuntime to showBootUi, and check what running responsibilities this call assumes in related components, structural slices, and business drill-downs.</p>
|
|
</article>
|
|
<article class="layer-card document-entry-card" role="link" tabindex="0" data-praxis-anchor="engineering:runtime-flow:runesp32lvglstartupruntime:setbootlog:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp" data-praxis-kind="engineering_sequence_diagram" data-praxis-status="candidate" data-praxis-confidence="high" data-praxis-document-title="Dynamic collaboration: runEsp32LvglStartupRuntime calls setBootLog" data-praxis-document-summary="Open the dynamic collaboration fragment from runEsp32LvglStartupRuntime to setBootLog, and check what running responsibilities this call assumes in related components, structural slices and business drill-downs." data-praxis-document-md="docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-setbootlog/sequence-diagram.md" data-praxis-document-html="docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-setbootlog/sequence-diagram.html" data-praxis-drilldowns="[]">
|
|
<h3>Dynamic collaboration: runEsp32LvglStartupRuntime calls setBootLog</h3>
|
|
<p>high · Sequence Diagram</p>
|
|
<p>O</p>
|
|
</article>
|
|
</div>
|
|
</section>
|
|
<script type="application/json" id="praxis-engineering-map-index">{"schemaVersion":"praxis.engineeringMapIndex.v1","generatedAt":"2026-06-25T09:19:20.669Z","projectVersion":"0.1.0","git":{"branch":"main","commit":"34aad0bffa2f6450192f655f248a94b6c3cbd767","shortCommit":"34aad0bffa2f","dirty":true},"rootDocPath":"docs/engineering/engineering-maps.md","rootHtmlPath":"docs/engineering/engineering-maps.html","compatibilityDocPath":"docs/engineering/technical-complexity-maps.md","compatibilityHtmlPath":"docs/engineering/technical-complexity-maps.html","summary":{"fileCount":11735,"nodeCount":15063,"edgeCount":12150,"packageCount":18,"componentCount":24,"runtimeFlowCount":18,"deploymentNodeCount":0,"hotspotCount":18},"hierarchy":[{"parentKind":"package","childKinds":["component","class_structural","sequence","deployment","technical_hotspot"],"rationale":"The Package Diagram is a top-level engineering boundary for technical complexity; it drills down to key components, structural collaborations, operational links, operational configurations, and complexity hotspots within that boundary."},{"parentKind":"class_structural","childKinds":["component","sequence","technical_hotspot"],"rationale":"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."},{"parentKind":"component","childKinds":["sequence","class_structural","technical_hotspot"],"rationale":"Component Diagram is the perspective of key technical objects; it can drill down to the call fragments in which the object participates, the structural slices where it is located, and related hot spots."},{"parentKind":"sequence","childKinds":["component","class_structural","technical_hotspot"],"rationale":"Sequence Diagram is a dynamic collaboration perspective; it can reversely locate participating components, structural boundaries and possible operational risks."},{"parentKind":"deployment","childKinds":["package","component","technical_hotspot"],"rationale":"Deployment Diagram is the perspective of running/building nodes; it can drill down to the corresponding packages, entry components and running configuration hotspots."},{"parentKind":"technical_hotspot","childKinds":["package","component","class_structural","sequence"],"rationale":"Technical Hotspot is the risk perspective; it requires linking back to the boundaries, components, structures, or call fragments that create complexity."}],"categories":[{"id":"engineering:category:sequence","kind":"sequence","title":"Sequence Diagrams","directory":"docs/engineering/sequence-diagrams","mapDocPath":"docs/engineering/sequence-diagrams/sequence-diagrams-maps.md","mapHtmlPath":"docs/engineering/sequence-diagrams/sequence-diagrams-maps.html","summary":"A runtime collaboration fragment restored by a real call relationship.","count":18,"items":[{"id":"engineering:diagram:sequence:tick-calls-log_loop_interval","kind":"sequence","title":"Dynamic collaboration: tick calls log_loop_interval","summary":"Tick calls in apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp log_loop_interval in apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/tick-calls-log_loop_interval/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/tick-calls-log_loop_interval/sequence-diagram.html","anchor":"engineering:runtime-flow:tick:log_loop_interval:apps-esp32_lvgl-src-esp32_lvgl_arduino_loop_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_arduino_loop_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as tick\n participant Target as log_loop_interval\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of tick calling log_loop_interval.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"tick","targetName":"log_loop_interval"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:tick-calls-log_loop_interval:element:tick","mermaidId":"Source","label":"tick","kind":"component","anchor":"engineering:runtime-flow:tick:log_loop_interval:apps-esp32_lvgl-src-esp32_lvgl_arduino_loop_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_arduino_loop_runtime.cpp:source","summary":"tick is the source participant of the current Sequence Diagram, used to explain the tick calls in apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp log_loop_interval in apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp, so the tick was put into sequence.","relationshipMeaning":"tick -> log_loop_interval indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drill-down tick can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:tick-calls-log_loop_interval:element:log_loop_interval","mermaidId":"Target","label":"log_loop_interval","kind":"component","anchor":"engineering:runtime-flow:tick:log_loop_interval:apps-esp32_lvgl-src-esp32_lvgl_arduino_loop_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_arduino_loop_runtime.cpp:target","summary":"log_loop_interval is the target actor of the current Sequence Diagram and is used to interpret tick calls log_loop_interval in apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp, so log_loop_interval was put into sequence.","relationshipMeaning":"tick -> log_loop_interval indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down log_loop_interval can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_arduino_loop_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:add_status_line-calls-add_label","kind":"sequence","title":"Dynamic collaboration: add_status_line calls add_label","summary":"The add_status_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_label in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","docPath":"docs/engineering/sequence-diagrams/add_status_line-calls-add_label/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/add_status_line-calls-add_label/sequence-diagram.html","anchor":"engineering:runtime-flow:add_status_line:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as add_status_line\n participant Target as add_label\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of add_status_line calling add_label.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"add_status_line","targetName":"add_label"},"drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}],"elements":[{"id":"engineering:diagram:sequence:add_status_line-calls-add_label:element:add_status_line","mermaidId":"Source","label":"add_status_line","kind":"component","anchor":"engineering:runtime-flow:add_status_line:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:source","summary":"add_status_line is the source participant of the current Sequence Diagram and is used to interpret add_status_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_label in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_status_line was put into sequence.","relationshipMeaning":"add_status_line -> add_label indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down add_status_line can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]},{"id":"engineering:diagram:sequence:add_status_line-calls-add_label:element:add_label","mermaidId":"Target","label":"add_label","kind":"component","anchor":"engineering:runtime-flow:add_status_line:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:target","summary":"add_label is the target actor of the current Sequence Diagram and is used to interpret add_status_line calls in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_label was put into sequence.","relationshipMeaning":"add_status_line -> add_label indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drill down add_label to view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]}]},{"id":"engineering:diagram:sequence:add_u32_line-calls-add_label","kind":"sequence","title":"Dynamic collaboration: add_u32_line calls add_label","summary":"add_u32_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_label in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","docPath":"docs/engineering/sequence-diagrams/add_u32_line-calls-add_label/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/add_u32_line-calls-add_label/sequence-diagram.html","anchor":"engineering:runtime-flow:add_u32_line:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as add_u32_line\n participant Target as add_label\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of add_u32_line calling add_label.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"add_u32_line","targetName":"add_label"},"drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}],"elements":[{"id":"engineering:diagram:sequence:add_u32_line-calls-add_label:element:add_u32_line","mermaidId":"Source","label":"add_u32_line","kind":"component","anchor":"engineering:runtime-flow:add_u32_line:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:source","summary":"add_u32_line is the source participant of the current Sequence Diagram and is used to interpret add_u32_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_label in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_u32_line was put into sequence.","relationshipMeaning":"add_u32_line -> add_label indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down add_u32_line can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]},{"id":"engineering:diagram:sequence:add_u32_line-calls-add_label:element:add_label","mermaidId":"Target","label":"add_label","kind":"component","anchor":"engineering:runtime-flow:add_u32_line:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:target","summary":"add_label is the target participant of the current Sequence Diagram and is used to interpret add_u32_line calls in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_label was put into sequence.","relationshipMeaning":"add_u32_line -> add_label indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drill down add_label to view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]}]},{"id":"engineering:diagram:sequence:add_hex_line-calls-add_status_line","kind":"sequence","title":"Dynamic collaboration: add_hex_line calls add_status_line","summary":"add_hex_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_status_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","docPath":"docs/engineering/sequence-diagrams/add_hex_line-calls-add_status_line/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/add_hex_line-calls-add_status_line/sequence-diagram.html","anchor":"engineering:runtime-flow:add_hex_line:add_status_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as add_hex_line\n participant Target as add_status_line\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of add_hex_line calling add_status_line.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"add_hex_line","targetName":"add_status_line"},"drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}],"elements":[{"id":"engineering:diagram:sequence:add_hex_line-calls-add_status_line:element:add_hex_line","mermaidId":"Source","label":"add_hex_line","kind":"component","anchor":"engineering:runtime-flow:add_hex_line:add_status_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:source","summary":"add_hex_line is the source participant of the current Sequence Diagram and is used to interpret add_hex_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_status_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_hex_line was put into sequence.","relationshipMeaning":"add_hex_line -> add_status_line indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down add_hex_line can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]},{"id":"engineering:diagram:sequence:add_hex_line-calls-add_status_line:element:add_status_line","mermaidId":"Target","label":"add_status_line","kind":"component","anchor":"engineering:runtime-flow:add_hex_line:add_status_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:target","summary":"add_status_line is the target actor of the current Sequence Diagram and is used to interpret add_hex_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_status_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_status_line was put into sequence.","relationshipMeaning":"add_hex_line -> add_status_line indicates that the target capability is dependent on the current fragment; it is necessary to combine the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down add_status_line can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]}]},{"id":"engineering:diagram:sequence:companion_enter-calls-add_label","kind":"sequence","title":"Dynamic collaboration: companion_enter calls add_label","summary":" companion_enter in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_label in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","docPath":"docs/engineering/sequence-diagrams/companion_enter-calls-add_label/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/companion_enter-calls-add_label/sequence-diagram.html","anchor":"engineering:runtime-flow:companion_enter:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as companion_enter\n participant Target as add_label\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment where companion_enter calls add_label.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"companion_enter","targetName":"add_label"},"drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}],"elements":[{"id":"engineering:diagram:sequence:companion_enter-calls-add_label:element:companion_enter","mermaidId":"Source","label":"companion_enter","kind":"component","anchor":"engineering:runtime-flow:companion_enter:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:source","summary":"companion_enter is the source participant for the current Sequence Diagram and is used to interpret companion_enter in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calling add_label in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so companion_enter was put into sequence.","relationshipMeaning":"companion_enter -> add_label indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down companion_enter can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]},{"id":"engineering:diagram:sequence:companion_enter-calls-add_label:element:add_label","mermaidId":"Target","label":"add_label","kind":"component","anchor":"engineering:runtime-flow:companion_enter:add_label:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:target","summary":"add_label is the target actor of the current Sequence Diagram and is used to interpret companion_enter calls in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_label was put into sequence.","relationshipMeaning":"companion_enter -> add_label indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drill down add_label to view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]}]},{"id":"engineering:diagram:sequence:companion_enter-calls-add_status_line","kind":"sequence","title":"Dynamic collaboration: companion_enter calls add_status_line","summary":" companion_enter in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_status_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","docPath":"docs/engineering/sequence-diagrams/companion_enter-calls-add_status_line/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/companion_enter-calls-add_status_line/sequence-diagram.html","anchor":"engineering:runtime-flow:companion_enter:add_status_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as companion_enter\n participant Target as add_status_line\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment where companion_enter calls add_status_line.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"companion_enter","targetName":"add_status_line"},"drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}],"elements":[{"id":"engineering:diagram:sequence:companion_enter-calls-add_status_line:element:companion_enter","mermaidId":"Source","label":"companion_enter","kind":"component","anchor":"engineering:runtime-flow:companion_enter:add_status_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:source","summary":"companion_enter is the source actor for the current Sequence Diagram and is used to interpret companion_enter in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_status_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so companion_enter was put into sequence.","relationshipMeaning":"companion_enter -> add_status_line indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down companion_enter can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]},{"id":"engineering:diagram:sequence:companion_enter-calls-add_status_line:element:add_status_line","mermaidId":"Target","label":"add_status_line","kind":"component","anchor":"engineering:runtime-flow:companion_enter:add_status_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:target","summary":"add_status_line is the target actor of the current Sequence Diagram and is used to interpret companion_enter calls add_status_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_status_line was put into sequence.","relationshipMeaning":"companion_enter -> add_status_line indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down add_status_line can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]}]},{"id":"engineering:diagram:sequence:companion_enter-calls-add_u32_line","kind":"sequence","title":"Dynamic collaboration: companion_enter calls add_u32_line","summary":" companion_enter in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_u32_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","docPath":"docs/engineering/sequence-diagrams/companion_enter-calls-add_u32_line/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/companion_enter-calls-add_u32_line/sequence-diagram.html","anchor":"engineering:runtime-flow:companion_enter:add_u32_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as companion_enter\n participant Target as add_u32_line\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment where companion_enter calls add_u32_line.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"companion_enter","targetName":"add_u32_line"},"drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}],"elements":[{"id":"engineering:diagram:sequence:companion_enter-calls-add_u32_line:element:companion_enter","mermaidId":"Source","label":"companion_enter","kind":"component","anchor":"engineering:runtime-flow:companion_enter:add_u32_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:source","summary":"companion_enter is the source actor for the current Sequence Diagram and is used to interpret companion_enter in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calling add_u32_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so companion_enter was put into sequence.","relationshipMeaning":"companion_enter -> add_u32_line indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down companion_enter can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]},{"id":"engineering:diagram:sequence:companion_enter-calls-add_u32_line:element:add_u32_line","mermaidId":"Target","label":"add_u32_line","kind":"component","anchor":"engineering:runtime-flow:companion_enter:add_u32_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:target","summary":"add_u32_line is the target actor of the current Sequence Diagram and is used to interpret companion_enter calls add_u32_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_u32_line was put into sequence.","relationshipMeaning":"companion_enter -> add_u32_line indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down add_u32_line can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]}]},{"id":"engineering:diagram:sequence:companion_enter-calls-add_hex_line","kind":"sequence","title":"Dynamic collaboration: companion_enter calls add_hex_line","summary":" companion_enter in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calls add_hex_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","docPath":"docs/engineering/sequence-diagrams/companion_enter-calls-add_hex_line/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/companion_enter-calls-add_hex_line/sequence-diagram.html","anchor":"engineering:runtime-flow:companion_enter:add_hex_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as companion_enter\n participant Target as add_hex_line\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of companion_enter calling add_hex_line.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"companion_enter","targetName":"add_hex_line"},"drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}],"elements":[{"id":"engineering:diagram:sequence:companion_enter-calls-add_hex_line:element:companion_enter","mermaidId":"Source","label":"companion_enter","kind":"component","anchor":"engineering:runtime-flow:companion_enter:add_hex_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:source","summary":"companion_enter is the source actor for the current Sequence Diagram and is used to interpret companion_enter in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp calling add_hex_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so companion_enter was put into sequence.","relationshipMeaning":"companion_enter -> add_hex_line indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down companion_enter can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]},{"id":"engineering:diagram:sequence:companion_enter-calls-add_hex_line:element:add_hex_line","mermaidId":"Target","label":"add_hex_line","kind":"component","anchor":"engineering:runtime-flow:companion_enter:add_hex_line:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:target","summary":"add_hex_line is the target actor of the current Sequence Diagram and is used to interpret companion_enter calls add_hex_line in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp and apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp, so add_hex_line was put into sequence.","relationshipMeaning":"companion_enter -> add_hex_line indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down add_hex_line can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp may change the sequence's dependencies, call evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Destination: apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[{"id":"engineering:diagram:component:apps-esp32_lvgl-companion_enter","kind":"component","title":"Function node: companion_enter","summary":"function is located in apps/esp32_lvgl/src/esp32_lvgl_idf_app_registry.cpp#L72, which coordinates multiple external objects or capabilities and is used to explain technical collaboration and change impact areas.","docPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.md","htmlPath":"docs/engineering/component-diagrams/apps-esp32_lvgl-companion_enter/component-diagram.html","anchor":"engineering:component:function:companion_enter:apps-esp32_lvgl-src-esp32_lvgl_idf_app_registry.cpp:72","relation":"source_or_target","reason":"Open the component diagram of function node: companion_enter to view the real responsibilities, file anchors and relationship pressure of the current sequence participants."}]}]},{"id":"engineering:diagram:sequence:startesp32lvglloopruntime-calls-canstartesp32lvglloopruntime","kind":"sequence","title":"Dynamic collaboration: startEsp32LvglLoopRuntime calls canStartEsp32LvglLoopRuntime","summary":" startEsp32LvglLoopRuntime in apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp calls canStartEsp32LvglLoopRuntime in apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/startesp32lvglloopruntime-calls-canstartesp32lvglloopruntime/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/startesp32lvglloopruntime-calls-canstartesp32lvglloopruntime/sequence-diagram.html","anchor":"engineering:runtime-flow:startesp32lvglloopruntime:canstartesp32lvglloopruntime:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as startEsp32LvglLoopRuntime\n participant Target as canStartEsp32LvglLoopRuntime\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of startEsp32LvglLoopRuntime calling canStartEsp32LvglLoopRuntime.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"startEsp32LvglLoopRuntime","targetName":"canStartEsp32LvglLoopRuntime"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:startesp32lvglloopruntime-calls-canstartesp32lvglloopruntime:element:startesp32lvglloopruntime","mermaidId":"Source","label":"startEsp32LvglLoopRuntime","kind":"component","anchor":"engineering:runtime-flow:startesp32lvglloopruntime:canstartesp32lvglloopruntime:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp:source","summary":"startEsp32LvglLoopRuntime is the source participant of the current Sequence Diagram, used to explain apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp. startEsp32LvglLoopRuntime calls canStartEsp32LvglLoopRuntime in apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local warehouse evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp, so startEsp32LvglLoopRuntime was put into sequence.","relationshipMeaning":"startEsp32LvglLoopRuntime -> canStartEsp32LvglLoopRuntime indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down startEsp32LvglLoopRuntime can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:startesp32lvglloopruntime-calls-canstartesp32lvglloopruntime:element:canstartesp32lvglloopruntime","mermaidId":"Target","label":"canStartEsp32LvglLoopRuntime","kind":"component","anchor":"engineering:runtime-flow:startesp32lvglloopruntime:canstartesp32lvglloopruntime:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp:target","summary":"canStartEsp32LvglLoopRuntime is the target participant of the current Sequence Diagram, used to interpret startEsp32LvglLoopRuntime calls in apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp canStartEsp32LvglLoopRuntime.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local warehouse evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp, so canStartEsp32LvglLoopRuntime was put into sequence.","relationshipMeaning":"startEsp32LvglLoopRuntime -> canStartEsp32LvglLoopRuntime indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down canStartEsp32LvglLoopRuntime can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:hasesp32lvglruntimetargetprofile-calls-esp32lvglruntimetargetprofile","kind":"sequence","title":"Dynamic collaboration: hasEsp32LvglRuntimeTargetProfile calls esp32LvglRuntimeTargetProfile","summary":"hasEsp32LvglRuntimeTargetProfile in apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp calls esp32LvglRuntimeTargetProfile in apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp.","docPath":"docs/engineering/sequence-diagrams/hasesp32lvglruntimetargetprofile-calls-esp32lvglruntimetargetprofile/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/hasesp32lvglruntimetargetprofile-calls-esp32lvglruntimetargetprofile/sequence-diagram.html","anchor":"engineering:runtime-flow:hasesp32lvglruntimetargetprofile:esp32lvglruntimetargetprofile:apps-esp32_lvgl-src-esp32_lvgl_runtime_config.cpp:apps-esp32_lvgl-src-esp32_lvgl_runtime_config.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as hasEsp32LvglRuntimeTargetProfile\n participant Target as esp32LvglRuntimeTargetProfile\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of hasEsp32LvglRuntimeTargetProfile calling esp32LvglRuntimeTargetProfile.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp and apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"hasEsp32LvglRuntimeTargetProfile","targetName":"esp32LvglRuntimeTargetProfile"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:hasesp32lvglruntimetargetprofile-calls-esp32lvglruntimetargetprofile:element:hasesp32lvglruntimetargetprofile","mermaidId":"Source","label":"hasEsp32LvglRuntimeTargetProfile","kind":"component","anchor":"engineering:runtime-flow:hasesp32lvglruntimetargetprofile:esp32lvglruntimetargetprofile:apps-esp32_lvgl-src-esp32_lvgl_runtime_config.cpp:apps-esp32_lvgl-src-esp32_lvgl_runtime_config.cpp:source","summary":"hasEsp32LvglRuntimeTargetProfile is the current Sequence Diagram The source actor used to interpret hasEsp32LvglRuntimeTargetProfile in apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp calls esp32LvglRuntimeTargetProfile in apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp and apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp, so hasEsp32LvglRuntimeTargetProfile was put into sequence.","relationshipMeaning":"hasEsp32LvglRuntimeTargetProfile -> esp32LvglRuntimeTargetProfile indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down hasEsp32LvglRuntimeTargetProfile can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:hasesp32lvglruntimetargetprofile-calls-esp32lvglruntimetargetprofile:element:esp32lvglruntimetargetprofile","mermaidId":"Target","label":"esp32LvglRuntimeTargetProfile","kind":"component","anchor":"engineering:runtime-flow:hasesp32lvglruntimetargetprofile:esp32lvglruntimetargetprofile:apps-esp32_lvgl-src-esp32_lvgl_runtime_config.cpp:apps-esp32_lvgl-src-esp32_lvgl_runtime_config.cpp:target","summary":"esp32LvglRuntimeTargetProfile is the target participant of the current Sequence Diagram and is used to interpret hasEsp32LvglRuntimeTargetProfile calls apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp in apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp esp32LvglRuntimeTargetProfile in.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp and apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp, so esp32LvglRuntimeTargetProfile was put into sequence.","relationshipMeaning":"hasEsp32LvglRuntimeTargetProfile -> esp32LvglRuntimeTargetProfile indicates that the target capability is dependent on the current fragment; it is necessary to combine the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down esp32LvglRuntimeTargetProfile can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_runtime_config.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:showbootui-calls-lockui","kind":"sequence","title":"Dynamic collaboration: showBootUi calls lockUi","summary":" showBootUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls lockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/showbootui-calls-lockui/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/showbootui-calls-lockui/sequence-diagram.html","anchor":"engineering:runtime-flow:showbootui:lockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as showBootUi\n participant Target as lockUi\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of showBootUi calling lockUi.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"showBootUi","targetName":"lockUi"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:showbootui-calls-lockui:element:showbootui","mermaidId":"Source","label":"showBootUi","kind":"component","anchor":"engineering:runtime-flow:showbootui:lockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:source","summary":"showBootUi is the source participant of the current Sequence Diagram and is used to interpret showBootUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls lockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so showBootUi was put into sequence.","relationshipMeaning":"showBootUi -> lockUi indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependency and cannot directly prove the runtime order.","drilldownIntent":"Drilling down showBootUi can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:showbootui-calls-lockui:element:lockui","mermaidId":"Target","label":"lockUi","kind":"component","anchor":"engineering:runtime-flow:showbootui:lockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:target","summary":"lockUi is the target actor of the current Sequence Diagram and is used to interpret showBootUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls lockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so lockUi was put into sequence.","relationshipMeaning":"showBootUi -> lockUi indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down into lockUi can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:showbootui-calls-unlockui","kind":"sequence","title":"Dynamic collaboration: showBootUi calls unlockUi","summary":"showBootUi calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp unlockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/showbootui-calls-unlockui/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/showbootui-calls-unlockui/sequence-diagram.html","anchor":"engineering:runtime-flow:showbootui:unlockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as showBootUi\n participant Target as unlockUi\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of showBootUi calling unlockUi.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"showBootUi","targetName":"unlockUi"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:showbootui-calls-unlockui:element:showbootui","mermaidId":"Source","label":"showBootUi","kind":"component","anchor":"engineering:runtime-flow:showbootui:unlockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:source","summary":"showBootUi is the source participant of the current Sequence Diagram, used to interpret showBootUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls unlockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so showBootUi was put into sequence.","relationshipMeaning":"showBootUi -> unlockUi indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down showBootUi can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:showbootui-calls-unlockui:element:unlockui","mermaidId":"Target","label":"unlockUi","kind":"component","anchor":"engineering:runtime-flow:showbootui:unlockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:target","summary":"unlockUi is the target actor of the current Sequence Diagram and is used to interpret showBootUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls unlockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so unlockUi was put into sequence.","relationshipMeaning":"showBootUi -> unlockUi indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down unlockUi can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:setbootlog-calls-lockui","kind":"sequence","title":"Dynamic collaboration: setBootLog calls lockUi","summary":"setBootLog in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls lockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/setbootlog-calls-lockui/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/setbootlog-calls-lockui/sequence-diagram.html","anchor":"engineering:runtime-flow:setbootlog:lockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as setBootLog\n participant Target as lockUi\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of setBootLog calling lockUi.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"setBootLog","targetName":"lockUi"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:setbootlog-calls-lockui:element:setbootlog","mermaidId":"Source","label":"setBootLog","kind":"component","anchor":"engineering:runtime-flow:setbootlog:lockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:source","summary":"setBootLog is the source participant of the current Sequence Diagram and is used to interpret setBootLog calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and lockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so setBootLog was put into sequence.","relationshipMeaning":"setBootLog -> lockUi indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependency and cannot directly prove the runtime order.","drilldownIntent":"Drill down setBootLog to view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:setbootlog-calls-lockui:element:lockui","mermaidId":"Target","label":"lockUi","kind":"component","anchor":"engineering:runtime-flow:setbootlog:lockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:target","summary":"lockUi is the target actor of the current Sequence Diagram and is used to interpret setBootLog calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so lockUi was put into sequence.","relationshipMeaning":"setBootLog -> lockUi indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down into lockUi can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:setbootlog-calls-unlockui","kind":"sequence","title":"Dynamic collaboration: setBootLog calls unlockUi","summary":"setBootLog calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp unlockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/setbootlog-calls-unlockui/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/setbootlog-calls-unlockui/sequence-diagram.html","anchor":"engineering:runtime-flow:setbootlog:unlockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as setBootLog\n participant Target as unlockUi\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of setBootLog calling unlockUi.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"setBootLog","targetName":"unlockUi"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:setbootlog-calls-unlockui:element:setbootlog","mermaidId":"Source","label":"setBootLog","kind":"component","anchor":"engineering:runtime-flow:setbootlog:unlockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:source","summary":"setBootLog is the source participant of the current Sequence Diagram and is used to interpret setBootLog calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and unlockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so setBootLog was put into sequence.","relationshipMeaning":"setBootLog -> unlockUi indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drill down setBootLog to view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:setbootlog-calls-unlockui:element:unlockui","mermaidId":"Target","label":"unlockUi","kind":"component","anchor":"engineering:runtime-flow:setbootlog:unlockui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:target","summary":"unlockUi is the target actor of the current Sequence Diagram and is used to interpret setBootLog calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp for unlockUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so unlockUi was put into sequence.","relationshipMeaning":"setBootLog -> unlockUi indicates that the target capability is dependent on the current fragment; it needs to be combined with the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down unlockUi can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:canrunesp32lvglstartupruntime-calls-canstartesp32lvglloopruntime","kind":"sequence","title":"Dynamic collaboration: canRunEsp32LvglStartupRuntime calls canStartEsp32LvglLoopRuntime","summary":"canRunEsp32LvglStartupRuntime in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls canStartEsp32LvglLoopRuntime in apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/canrunesp32lvglstartupruntime-calls-canstartesp32lvglloopruntime/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/canrunesp32lvglstartupruntime-calls-canstartesp32lvglloopruntime/sequence-diagram.html","anchor":"engineering:runtime-flow:canrunesp32lvglstartupruntime:canstartesp32lvglloopruntime:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as canRunEsp32LvglStartupRuntime\n participant Target as canStartEsp32LvglLoopRuntime\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of canRunEsp32LvglStartupRuntime calling canStartEsp32LvglLoopRuntime.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"canRunEsp32LvglStartupRuntime","targetName":"canStartEsp32LvglLoopRuntime"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:canrunesp32lvglstartupruntime-calls-canstartesp32lvglloopruntime:element:canrunesp32lvglstartupruntime","mermaidId":"Source","label":"canRunEsp32LvglStartupRuntime","kind":"component","anchor":"engineering:runtime-flow:canrunesp32lvglstartupruntime:canstartesp32lvglloopruntime:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp:source","summary":"canRunEsp32LvglStartupRuntime is the source participant of the current Sequence Diagram, used to explain canRunEsp32LvglStartupRuntime calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp canStartEsp32LvglLoopRuntime in apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp, so canRunEsp32LvglStartupRuntime was put into sequence.","relationshipMeaning":"canRunEsp32LvglStartupRuntime -> canStartEsp32LvglLoopRuntime indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down canRunEsp32LvglStartupRuntime can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Official module: apps/esp32_lvgl","apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:canrunesp32lvglstartupruntime-calls-canstartesp32lvglloopruntime:element:canstartesp32lvglloopruntime","mermaidId":"Target","label":"canStartEsp32LvglLoopRuntime","kind":"component","anchor":"engineering:runtime-flow:canrunesp32lvglstartupruntime:canstartesp32lvglloopruntime:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_loop_runtime.cpp:target","summary":"canStartEsp32LvglLoopRuntime is the target participant of the current Sequence Diagram and is used to interpret canRunEsp32LvglStartupRuntime calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp canStartEsp32LvglLoopRuntime in apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp, so canStartEsp32LvglLoopRuntime was put into sequence.","relationshipMeaning":"canRunEsp32LvglStartupRuntime -> canStartEsp32LvglLoopRuntime indicates that the target capability is dependent on the current fragment; it is necessary to combine the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down canStartEsp32LvglLoopRuntime can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_loop_runtime.cpp","Official module: apps/esp32_lvgl","apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-canrunesp32lvglstartupruntime","kind":"sequence","title":"Dynamic collaboration: runEsp32LvglStartupRuntime calls canRunEsp32LvglStartupRuntime","summary":"runEsp32LvglStartupRuntime in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls canRunEsp32LvglStartupRuntime in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-canrunesp32lvglstartupruntime/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-canrunesp32lvglstartupruntime/sequence-diagram.html","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:canrunesp32lvglstartupruntime:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as runEsp32LvglStartupRuntime\n participant Target as canRunEsp32LvglStartupRuntime\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of runEsp32LvglStartupRuntime calling canRunEsp32LvglStartupRuntime.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"runEsp32LvglStartupRuntime","targetName":"canRunEsp32LvglStartupRuntime"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-canrunesp32lvglstartupruntime:element:runesp32lvglstartupruntime","mermaidId":"Source","label":"runEsp32LvglStartupRuntime","kind":"component","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:canrunesp32lvglstartupruntime:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:source","summary":"runEsp32LvglStartupRuntime is the source participant of the current Sequence Diagram, used to interpret runEsp32LvglStartupRuntime calls apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp canRunEsp32LvglStartupRuntime in.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so runEsp32LvglStartupRuntime was put into sequence.","relationshipMeaning":"runEsp32LvglStartupRuntime -> canRunEsp32LvglStartupRuntime indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependency and cannot directly prove the runtime order.","drilldownIntent":"Drilling down runEsp32LvglStartupRuntime can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-canrunesp32lvglstartupruntime:element:canrunesp32lvglstartupruntime","mermaidId":"Target","label":"canRunEsp32LvglStartupRuntime","kind":"component","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:canrunesp32lvglstartupruntime:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:target","summary":"canRunEsp32LvglStartupRuntime is the target participant of the current Sequence Diagram and is used to interpret runEsp32LvglStartupRuntime calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp canRunEsp32LvglStartupRuntime in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so canRunEsp32LvglStartupRuntime was put into sequence.","relationshipMeaning":"runEsp32LvglStartupRuntime -> canRunEsp32LvglStartupRuntime indicates that the target capability is dependent on the current fragment; it is necessary to combine the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down canRunEsp32LvglStartupRuntime can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-showbootui","kind":"sequence","title":"Dynamic collaboration: runEsp32LvglStartupRuntime calls showBootUi","summary":" runEsp32LvglStartupRuntime in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls showBootUi in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-showbootui/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-showbootui/sequence-diagram.html","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:showbootui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as runEsp32LvglStartupRuntime\n participant Target as showBootUi\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of runEsp32LvglStartupRuntime calling showBootUi.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"runEsp32LvglStartupRuntime","targetName":"showBootUi"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-showbootui:element:runesp32lvglstartupruntime","mermaidId":"Source","label":"runEsp32LvglStartupRuntime","kind":"component","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:showbootui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:source","summary":"runEsp32LvglStartupRuntime is the source participant of the current Sequence Diagram, used to interpret runEsp32LvglStartupRuntime calls apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp showBootUi in .","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so runEsp32LvglStartupRuntime was put into sequence.","relationshipMeaning":"runEsp32LvglStartupRuntime -> showBootUi indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependencies and cannot directly prove the runtime order.","drilldownIntent":"Drilling down runEsp32LvglStartupRuntime can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-showbootui:element:showbootui","mermaidId":"Target","label":"showBootUi","kind":"component","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:showbootui:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:target","summary":"showBootUi is the target actor of the current Sequence Diagram and is used to interpret runEsp32LvglStartupRuntime calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so showBootUi was put into sequence.","relationshipMeaning":"runEsp32LvglStartupRuntime -> showBootUi indicates that the target capability is dependent on the current fragment; it is necessary to combine the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drilling down showBootUi can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]},{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-setbootlog","kind":"sequence","title":"Dynamic collaboration: runEsp32LvglStartupRuntime calls setBootLog","summary":" runEsp32LvglStartupRuntime in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp calls setBootLog in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","docPath":"docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-setbootlog/sequence-diagram.md","htmlPath":"docs/engineering/sequence-diagrams/runesp32lvglstartupruntime-calls-setbootlog/sequence-diagram.html","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:setbootlog:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp","status":"candidate","confidence":"high","mermaidKind":"sequenceDiagram","mermaid":"sequenceDiagram\n participant Source as runEsp32LvglStartupRuntime\n participant Target as setBootLog\n Source->>Target: calls\n Note over Source,Target: apps/esp32_lvgl","readingGuide":["This Sequence Diagram focuses on the technical collaboration fragment of runEsp32LvglStartupRuntime calling setBootLog.","It describes a partial operation segment and is not necessarily equivalent to the complete business process.","The current relationship comes from local call evidence; without Use Case Trace, it only represents a local collaboration fragment and is not directly equivalent to the main success scenario, callback, compensation or failure path."],"technicalAnalysis":["There is a calls relationship between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, and the technical boundary is apps/esp32_lvgl.","Sequence Diagram is used to explain runtime or collaboration sequences, and is suitable for undertaking dynamic behaviors that are not clearly visible from the Package/Component diagram.","If future evidence shows that there are asynchronous messages, callbacks, timeouts or failure compensation, multiple sequences should be broken out for the same business/technical scenario rather than crammed into one big picture."],"businessRelation":["The main success path, failure path and callback path of the business Use Case will eventually fall on several technical sequence fragments.","The current fragment may explain the technical execution steps in a certain business story; if there is no Use Case Trace, it only serves as a local collaboration fragment in the software structure model.","If it is confirmed to belong to a Use Case, the project sequence document should be linked to the corresponding drill-down Sequence Diagram in docs/design."],"governanceNotes":["Don't just judge the complete call chain based on a single relationship; you need to combine the upstream and downstream relationships to complete the scenario.","When the sequence involves external systems, model calls, file writing, or Git operations, failure paths and retry/compensation instructions should be added.","If the sequence supports user-visible functions, the business drill-down diagram of the organization/process model should be maintained simultaneously."],"coverage":["Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"evidencePaths":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp"],"questions":[],"scope":{"packageId":"apps/esp32_lvgl","sourcePath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPath":"apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","targetPackageId":"apps/esp32_lvgl","sourceName":"runEsp32LvglStartupRuntime","targetName":"setBootLog"},"drilldowns":[],"elements":[{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-setbootlog:element:runesp32lvglstartupruntime","mermaidId":"Source","label":"runEsp32LvglStartupRuntime","kind":"component","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:setbootlog:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:source","summary":"runEsp32LvglStartupRuntime is the source participant of the current Sequence Diagram, used to interpret runEsp32LvglStartupRuntime calls apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp setBootLog in.","role":"Message originator/relying party: It triggers or references the target capability.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so runEsp32LvglStartupRuntime was put into sequence.","relationshipMeaning":"runEsp32LvglStartupRuntime -> setBootLog indicates the dependency direction of the current fragment; if the relationship is only import, it can only indicate static dependency and cannot directly prove the runtime order.","drilldownIntent":"Drilling down runEsp32LvglStartupRuntime can view the corresponding Component Diagram or structural context to determine the responsibilities of this participant in the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]},{"id":"engineering:diagram:sequence:runesp32lvglstartupruntime-calls-setbootlog:element:setbootlog","mermaidId":"Target","label":"setBootLog","kind":"component","anchor":"engineering:runtime-flow:runesp32lvglstartupruntime:setbootlog:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:apps-esp32_lvgl-src-esp32_lvgl_startup_runtime.cpp:target","summary":"setBootLog is the target actor of the current Sequence Diagram and is used to interpret runEsp32LvglStartupRuntime calls in apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp.","role":"Message receiving/relying party: It provides the ability to be referenced or called by the current fragment.","whyItExists":"Local repository evidence calls were observed between apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp and apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp, so setBootLog was put into sequence.","relationshipMeaning":"runEsp32LvglStartupRuntime -> setBootLog indicates that the target capability is dependent on the current fragment; it is necessary to combine the call evidence to confirm whether it is a runtime call, a type reference or a static import.","drilldownIntent":"Drill down setBootLog to view the corresponding Component Diagram or structural context to determine the responsibilities of this participant within the larger technical boundary.","businessRelevance":"The execution process of the business Use Case may fall on multiple sequence fragments; the current fragment is only a candidate technical step and requires organizational/process model evidence to confirm the business meaning.","changeImpact":"Modifying apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp may change the sequence's dependencies, calling evidence, and interpretation of related component/structure diagrams.","evidence":["apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Interaction type: calls","Source: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Target: apps/esp32_lvgl/src/esp32_lvgl_startup_runtime.cpp","Official module: apps/esp32_lvgl"],"risks":["A single sequence fragment is not enough to prove the complete call chain or the successful path of the business owner."],"questions":["The current relationship type needs to be distinguished by evidence between runtime calls, static imports, type references, or configuration references; if it is only a static relationship, this diagram should not be interpreted as a real calling sequence."],"confidence":"high","drilldowns":[]}]}]}]}</script>
|
|
</main>
|
|
</body>
|
|
</html> |