@@ -111,14 +111,14 @@ The blog-team demonstrates a **pipeline actor topology** — actors are chained
111111│ Orchestrator (coordinator — not an actor) │
112112│ examples/blog-team/orchestrator.ts │
113113│ │
114- │ 1. publish(researcherQueue, {taskId, agentId:'researcher',...}) │
114+ │ 1. publish(researcherQueue, {taskId, agentId:'researcher',...})│
115115│ 2. await CompletionRouter.wait(researchTaskId) │
116116│ 3. publish(writerQueue, {taskId, agentId:'writer', context:…}) │
117117│ 4. await CompletionRouter.wait(writeTaskId) │
118118│ 5. publish(editorQueue, {taskId, agentId:'editor', context:…}) │
119119│ 6. await CompletionRouter.wait(editTaskId) │
120- │ 7. waitForHITLDecision(editTaskId, rl, redis) ← human input │
121- └──────┬───────────────────┬──────────────────────┬──────────────┘
120+ │ 7. waitForHITLDecision(editTaskId, rl, redis) ← human input │
121+ └──────┬───────────────────┬──────────────────────┬─────────────── ┘
122122 │ │ │
123123 ▼ queue ▼ queue ▼ queue
124124┌──────────────┐ ┌────────────────┐ ┌───────────────────────┐
@@ -129,13 +129,13 @@ The blog-team demonstrates a **pipeline actor topology** — actors are chained
129129│ process: │ │ process: │ │ process: │
130130│ researcher- │ │ writer- │ │ editor- │
131131│ node.ts │ │ node.ts │ │ node.ts │
132- └──────┬───────┘ └────────┬───────┘ └────────────┬─ ─────────┘
132+ └──────┬───────┘ └────────┬───────┘ └─────────────┬ ─────────┘
133133 │ │ │
134134 └───────────────────┴────────────────────────┘
135135 │ publish(COMPLETED_CHANNEL, result)
136136 ▼
137137 ┌─────────────────┐
138- │ CompletionRouter │
138+ │ CompletionRouter│
139139 │ (orchestrator) │
140140 └─────────────────┘
141141```
0 commit comments