← Operations

📊 Org Chart

graph TD ROOT[Orchestrator
Stitch] ROOT --> PLAN[Planner
Research & Strategy] ROOT --> EXEC[Executor
Production] ROOT --> CRIT[Critic
Quality] PLAN --> R1[Researcher A
Web] PLAN --> R2[Researcher B
Memory] PLAN --> R3[Researcher C
Files] PLAN --> R4[Researcher D
Academic] PLAN --> SYN[Synthesizer
Agentic RAG] PLAN --> DREF[Deep Reflector
CoD Loop] EXEC --> E1[Code Executor] EXEC --> E2[Content Executor] EXEC --> E3[Design Executor] EXEC --> E4[Analysis Executor] CRIT --> FG[Fast Guardrails] ROOT -.-> MEM[Memory Manager] PLAN -.-> MEM EXEC -.-> MEM classDef root fill:#f4d03f,stroke:#3d2817,stroke-width:3px,color:#3d2817 classDef manager fill:#58a6ff,stroke:#3d2817,stroke-width:2px,color:#fff classDef worker fill:#21262d,stroke:#c9a227,stroke-width:1px,color:#c9d1d9 classDef quality fill:#d29922,stroke:#3d2817,stroke-width:2px,color:#fff classDef support fill:#6e7681,stroke:#3d2817,stroke-width:1px,color:#fff class ROOT root class PLAN,EXEC,CRIT manager class R1,R2,R3,R4,SYN,DREF,E1,E2,E3,E4 worker class FG quality class MEM support
flowchart LR K[Kyle Request] --> O[Orchestrator] O --> P[Planner] P --> D[Research Team] D -->|Raw Data| S[Synthesizer] S <-->|Chain of Debates| R[Deep Reflector] S -->|Structured Data| P P -->|Briefing Artifact
JSON| E[Executor] E --> F[Fast Guardrails] F -->|Approved| O O -->|Response| K2[Kyle] P -.-> M[(Memory)] E -.-> M O -.-> M
sequenceDiagram participant K as Kyle participant O as Orchestrator participant P as Planner participant R1 as Researcher A participant R2 as Researcher B participant S as Synthesizer participant D as Deep Reflector participant E as Executor participant F as Fast Guardrails K->>O: "Plan Tokyo trip" O->>P: Assign goal par Parallel Research P->>R1: Web search P->>R2: Memory search end R1->>S: Raw data R2->>S: Raw data loop Chain of Debates S->>D: Conflict found D->>S: Resolution end S->>P: Structured data P->>P: Create Briefing Artifact (JSON) P->>E: Approved plan E->>E: Execute (produce itinerary) E->>F: Fast guardrails check F->>O: Approved O->>K: Final itinerary
flowchart TB subgraph Input REQ[Kyle Request] end subgraph Orchestration ORCH[Orchestrator
Intent Classification] end subgraph Research["🔬 Research Phase (Parallel)"] WEB[Web Researcher] MEM[Memory Researcher] FILE[File Researcher] ACAD[Academic Researcher] end subgraph Synthesis["🧠 Synthesis Phase"] SYN[Synthesizer] CODEREF[Chain of Debates
with Deep Reflector] BRIEF[Briefing Artifact
JSON Schema] end subgraph Execution["⚡ Execution Phase"] EXEC[Content/Code Executor] GUARD[Fast Guardrails] end subgraph Output DELIVER[Final Output] end subgraph Memory DB[(Long-term Memory)] end REQ --> ORCH ORCH --> Research WEB --> SYN MEM --> SYN FILE --> SYN ACAD --> SYN SYN <---> CODEREF CODEREF --> BRIEF BRIEF --> EXEC EXEC --> GUARD GUARD --> ORCH ORCH --> DELIVER ORCH -.-> DB SYN -.-> DB EXEC -.-> DB

📖 How to Read These Diagrams

Hierarchy: Shows the 3-level structure — Root Coordinator manages Sub-Managers who manage Specialist Workers.

Workflow: Simplified data flow from request through processing to output.

Sequence: Step-by-step interaction between agents (Tokyo trip example).

Data Flow: Detailed phases showing parallel research, synthesis with Chain of Debates, and execution.

Dashed lines (-.->) indicate memory logging. Solid lines indicate primary data flow.