Escalation Protocol

What problem does it solve?

Route a conversation to a human (artist or admin) when the bot can't resolve, must respect Bug F escalation gates, and notify via SAGE channel (Regla #45).

Core Features & Use Cases

• Tools owned: escalate_to_human, escalate_to_artist, request_artist_travel_availability.
• When to invoke: ALWAYS available — this skill is appended to every eligible set by the resolver. The specific escalation tools to use: escalate_to_human for general 'I want a person' requests; escalate_to_artist for style/budget/timing decisions only the artist can make; request_artist_travel_availability for cross-city / guest-spot inquiries (Doctrine #14 multi-maquila). Bug F gate (Regla #45 + S#77 hardening): only escalate ONCE per pending escalation TTL window (24h). Resolver enforces this via FSM context.
• Anti-patterns: Escalating in EVERY turn after the first one (spam to artist's SAGE channel). Escalating without summarizing the brief — the artist needs context, not a 'client wants tattoo' ping.
• Wired by: Resolver selects eligible skills into the set based on FSM state + intent classifier + workspace config (when CONCIERGE_SKILLS_V1_ENABLED=true). The tools listed under capabilities get unioned by harness/skill-tool-union.ts::unionAllowedTools and passed to the LLM as the active palette for the turn. Anything not in the union is invisible to the LLM that turn (progressive disclosure — fixes the 46-tool firehose problem from S#79 P1.quater).

Quick Start

Ask the bot to escalate to a human when automation cannot resolve the user request.