Skip to content

27 Butler and Delegation

KepCup 开发助理 edited this page Oct 24, 2026 · 1 revision

27 Butler and Delegation

Source: docs/design/27-butler-and-delegation.md

Butler (D70)

Unique system_role='butler': pinned, undeletable. After interview, propose_bots / propose_project / suggest_route approval cards (kind butler_proposal, non-blocking, never auto in unattended). Routing heuristic: unknown → Butler; single domain → DM; multi-role → project; stay here → delegate.

Butler never joins project teams (not lead/member; candidates and propose_project reject Butler).

A→B delegation (D71)

delegate_to_bot / cancel_delegation + delegations table. Intents: request (default, may follow B’s tasks), question (B’s turn reply), fyi (deliver-and-done). UI stays on A; B sees a user-origin message “sent on your behalf by A”. Single-hop only; no A→B→A; cannot delegate to Butler; same-project prefers @ (D4). Not SubAgent (23-MCP-and-SubAgent).

Clone this wiki locally