docs: rename project reference from advanced_multi_agent to tmux_agent_orchestration

2026-06-21 11:32:57 +00:00
parent d21d419a7c
commit a414158864
6 changed files with 9 additions and 9 deletions
@@ -1,6 +1,6 @@
 # BOOTSTRAP.md

-본 문서는 `advanced_multi_agent` 오케스트레이션 및 메시징 백플레인 워크플로우를 새로운 프로젝트에 도입하여 이식하고, 새로운 개발자/에이전트가 초기 가동을 시작할 때 수행해야 하는 환경 설정 및 구축 절차를 안내합니다.
+본 문서는 `tmux_agent_orchestration` 오케스트레이션 및 메시징 백플레인 워크플로우를 새로운 프로젝트에 도입하여 이식하고, 새로운 개발자/에이전트가 초기 가동을 시작할 때 수행해야 하는 환경 설정 및 구축 절차를 안내합니다.

 새로운 에이전트는 이 안내서에 기술된 절차를 순차적으로 실행하여 초기 환경을 안정적으로 설정할 수 있습니다.

@@ -1,6 +1,6 @@
 # BOOTSTRAP.md

-This document guides you through the setup and initialization procedures required to adopt the `advanced_multi_agent` orchestration and messaging backplane workflow in a new project, enabling a new developer or agent to get up and running quickly.
+This document guides you through the setup and initialization procedures required to adopt the `tmux_agent_orchestration` orchestration and messaging backplane workflow in a new project, enabling a new developer or agent to get up and running quickly.

 A new agent can follow the steps in this guide sequentially to establish a stable and reliable initial environment.

@@ -1,6 +1,6 @@
 # FUTURE_WORKS.md

-> **목적**: `advanced_multi_agent` 프로젝트의 향후 작업 후보를 추적한다.
+> **목적**: `tmux_agent_orchestration` 프로젝트의 향후 작업 후보를 추적한다.
 > 완료된 항목은 `DONE.ko.md`를 참조.
 > **최종 갱신**: 2026-06-21

@@ -1,6 +1,6 @@
 # FUTURE_WORKS.md

-> **Purpose**: Track future work candidates for the `advanced_multi_agent` project.
+> **Purpose**: Track future work candidates for the `tmux_agent_orchestration` project.
 > For completed items, see `DONE.md`.
 > **Last Updated**: 2026-06-21

@@ -1,6 +1,6 @@
 # Understand-Anything: Project & Architecture Analysis Report

-This report presents a comprehensive architectural analysis and security verification of the `advanced_multi_agent` orchestration workspace. Using the static analysis principles inspired by the `Understand-Anything` pipeline, we map out the codebase structure, evaluate the integrity of the design, identify critical defects/inconsistencies between implementation and documentation, and provide concrete technical recommendations.
+This report presents a comprehensive architectural analysis and security verification of the `tmux_agent_orchestration` orchestration workspace. Using the static analysis principles inspired by the `Understand-Anything` pipeline, we map out the codebase structure, evaluate the integrity of the design, identify critical defects/inconsistencies between implementation and documentation, and provide concrete technical recommendations.

 ---

@@ -3,8 +3,8 @@
 <head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <title>Understand-Anything: advanced_multi_agent Dashboard</title>
-    <meta name="description" content="Understand-Anything architecture and security dashboard for the advanced_multi_agent project.">
+    <title>Understand-Anything: tmux_agent_orchestration Dashboard</title>
+    <meta name="description" content="Understand-Anything architecture and security dashboard for the tmux_agent_orchestration project.">
    <!-- Google Fonts -->
    <link rel="preconnect" href="https://fonts.googleapis.com">
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
@@ -779,7 +779,7 @@
    <header>
        <div class="header-left">
            <div class="logo">U</div>
-            <div class="project-title">advanced_multi_agent</div>
+            <div class="project-title">tmux_agent_orchestration</div>
            <div class="project-subtitle">Understand-Anything Dashboard</div>
        </div>

@@ -813,7 +813,7 @@
            <div class="nav-group">
                <div class="nav-section-title">Project Tree</div>
                <div class="file-tree">
-                    <div class="tree-node tree-folder">📁 advanced_multi_agent</div>
+                    <div class="tree-node tree-folder">📁 tmux_agent_orchestration</div>
                    <div class="tree-node" id="tree-registry" onclick="clickNode('registry')">📄 registry.py <span class="dot-indicator dot-green"></span></div>
                    <div class="tree-node" id="tree-subscriber" onclick="clickNode('subscriber')">📄 job_subscriber.py <span class="dot-yellow"></span></div>
                    <div class="tree-node" id="tree-mqtt" onclick="clickNode('mqtt')">📄 mqtt_common.py <span class="dot-green"></span></div>