Skip to content

[Gastown] Patrol assigns triage beads to polecats causing repeated escalations #4038

@kilo-code-bot

Description

@kilo-code-bot

What happened?

High-priority role misconfiguration in rig schedulr (f0e6f31a): patrol system assigns triage-labeled beads to polecat agents (Shadow, etc.) which lack triage permissions. This creates failed beads and repeated escalations. The patrol-sent triage requests bypass the proper agent role routing and should be assigned to triage-capable agents only. Current workaround is resetting the polecat and acknowledging escalations, but the root cause is in patrol's bead assignment logic.

Area

Agent Dispatch / Scheduling

Context

  • Town ID: 28dd334d-e31d-4f2f-b9cd-305323830c95
  • Agent: Mayor (826a7e64-6cfb-40bb-8487-d3c9ef4a1fb3)
  • Rig ID: f0e6f31a-2237-4c48-bbdc-c707bff7d732

Recent Errors

Role misconfiguration: polecat cannot resolve triage requests — repeated high-severity escalations on rig f0e6f31a-2237-4c48-bbdc-c707bff7d732

Filed automatically by the Mayor via gt_report_bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions