escalation-router

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

升级路由器

Escalation Router

所有者: 仅子协调器
Owner: Sub-coordinators only

职责

Responsibilities

  1. 分析error_report的复杂度
  2. 决策:研究员可以解决 或 需要人工
  3. 为选定路径格式化交接
  4. 向主协调器发送状态信号
  1. Analyze the complexity of the error_report
  2. Decision: solvable by Researcher or requires Human intervention
  3. Format the handoff for the selected path
  4. Send status signal to the main coordinator

决策标准

Decision Criteria

路由到研究员的情况:
  • 错误是技术/知识缺口(缺少库使用、API混淆)
  • 类似问题在线存在(可搜索)
  • 不需要架构决策
路由到人工的情况:
  • 需求模糊(PRD不清晰)
  • 需要架构权衡
  • 外部依赖阻塞(API密钥、服务)
  • 研究员已经失败
Route to Researcher:
  • The error is a technical/knowledge gap (missing library usage, API confusion)
  • Similar issues exist online (searchable)
  • No architectural decisions required
Route to Human:
  • Ambiguous requirements (unclear PRD)
  • Architectural trade-offs needed
  • Blocked by external dependencies (API keys, services)
  • Researcher has failed

研究员交接

Researcher Handoff

yaml
research_request:
  problem_summary: "邮箱验证返回500而非400"
  error_report: {来自fix-engine的完整error_report}
  search_hints:
    - "express错误处理中间件"
    - "验证库自定义错误"
  constraints:
    - 不得更改API契约
    - 必须保留现有测试
yaml
research_request:
  problem_summary: "邮箱验证返回500而非400"
  error_report: {来自fix-engine的完整error_report}
  search_hints:
    - "express错误处理中间件"
    - "验证库自定义错误"
  constraints:
    - 不得更改API契约
    - 必须保留现有测试

人工交接

Human Handoff

信号documenter子代理生成PRD,然后:
信号到主协调器: WAITING
原因: human_intervention_required
交接文档: ./handoff-prd-{section-id}.md
Signal the documenter sub-agent to generate a PRD, then:
Signal to main coordinator: WAITING
Reason: human_intervention_required
Handoff document: ./handoff-prd-{section-id}.md