docs(mux-loop): add multi-agent architecture consensus & review reports for CLI redesign

2026-08-26 14:03:16 +09:00
parent 80c9e37b77
commit d56f60bbc6
14 changed files with 1280 additions and 0 deletions
@@ -0,0 +1,37 @@
+# 📋 Review & Opinion on CLI Option Redesign Proposal (Job 10a3201c)
+
+- **Reviewer**: planner-reviewer-claude-01
+- **Job ID**: 10a3201c
+- **Role**: Planner & Reviewer
+- **Target Proposal**: CLI Option Redesign (`--creator`, `--planner`, `--reviewer`)
+
+---
+
+## 1. Executive Summary & Verdict
+- **Verdict**: **STRONGLY ENDORSED (100% PASS)**
+- **Rationale**: The proposal resolves an asymmetry in the CLI design where the three fundamental roles were represented inconsistently (`--target-agent` vs `--plan` vs `--reviewer`). Transitioning to `--creator`, `--planner`, and `--reviewer` provides high ergonomic clarity and intuitive alignment with the architecture.
+
+---
+
+## 2. Key Architectural Strengths
+
+1. **Role Symmetry (3-Tier Alignment)**:
+   - `--planner <name>`: Explicitly binds the Planner session and implicitly sets `PLAN_MODE=true`.
+   - `--creator <name>`: Explicitly binds the primary Creator session.
+   - `--reviewer "A,B"` / `--all-reviewer`: Binds the Reviewer pool.
+
+2. **Zero-Breaking-Change Guarantee**:
+   - Preserving `--target-agent` as an alias for `--creator` guarantees complete backward compatibility for all existing scripts, tests, and wrapper invocations.
+
+3. **Multi-Agent Disambiguation**:
+   - In environments with multiple running Planner-capable agents (e.g. Claude + Grok + AGY), `--planner <name>` eliminates ambiguity and allows precise orchestration targeting.
+
+---
+
+## 3. Recommended Edge Case Defenses for Implementation
+
+1. **Flag Mutual Consistency**: If both `--creator <name1>` and `--target-agent <name2>` are provided with conflicting names, `run_loop.sh` should fail-fast with a clear validation error.
+2. **Implicit `--plan` Handling**: Providing `--planner <session>` should automatically set `PLAN_MODE=true`, but passing `--planner <session>` while simultaneously passing a hypothetical `--no-plan` should be rejected as contradictory.
+3. **Session Liveness Validation**: When `--planner <session>` is explicitly supplied, `run_loop.sh` should verify that the specified session exists and has `status: running` in `agent-sessions.yaml`.
+
+[VERDICT: PASS]