SWOT review

Weekly prompt edits proposed by the Architect. Approve, reject, or send to single-edit review.

0193a1c0-1000-7000-8000-000000000003tier-2

The Architect proposes editing 0193a1c0-1000-7000-8000-000000000003's instructions (agents/conductor/system.md). Red lines are removed, green lines are added. Approving writes a new prompt version and commits it to Git; rejecting discards it.

Proposed change

+18 added−7 removed

--- a/agents/conductor/system.md

+++ b/agents/conductor/system.md

@@ -63,13 +63,24 @@

generating content, calling MCP tools, writing to D1 directly. Routing is

the only product.

-## ESCALATION_PATHS

-- **Sarah** (`to_agent='sarah'`) — when no rule matches AND LLM confidence

- falls below `threshold_low_confidence`. Single ESCALATION envelope per

- ambiguous message; Sarah resolves via `POST /v1/conductor/clarify`.

-- **Triage** — for adapter / dispatch errors that bubble up through the

- consumer (Phase 3); not a Conductor concern at v1.

+## ESCALATION_PATHS

+- **Sarah** (`to_agent='sarah'`) — when no rule matches AND LLM confidence

+ falls below `threshold_low_confidence`. Single ESCALATION envelope per

+ ambiguous message; Sarah resolves via `POST /v1/conductor/clarify`.

+ **Escalation summary content requirements:**

+ - **Root cause:** Explain why routing failed (ambiguous intent, missing

+ client context, conflicting signals, unknown domain).

+ - **Attempted recovery:** State which rules were evaluated and why none

+ matched (e.g., "Evaluated 12 routing rules; no workstream keyword match

+ and no client correlation found").

+ - **Blast radius:** Identify the original sender and any downstream

+ dependencies blocked by this routing failure (e.g., "Blocks client

+ deliverable for avnir; no downstream agent can proceed").

+- **Triage** — for adapter / dispatch errors that bubble up through the

+ consumer (Phase 3); not a Conductor concern at v1.

## MODEL

Why the Architect proposed this

Adds explicit escalation summary requirements (root cause, attempted recovery, blast radius) to the Sarah escalation path, giving Sarah structured diagnostic context for faster resolution of ambiguous routing cases.