What happened?
Update to already filed issue #4147
Adding new evidence and one critical constraint discovered: Kilo Gastown provides no mechanism for the mayor or user to add a triage role to an agent or configure the rig's agent roster. The mayor's toolset (gt_agent_reset, gt_bead_update, gt_bead_reassign, etc.) has no triage-role provisioning. Therefore the only fix must be platform-side.
Additional evidence (past ~8 hours)
- Escalations now self-feed: failed triage batch → escalation bead → patrol creates another triage batch for the escalation → another failure → another escalation
- Affected every polecat in the rig: Toast, Maple, Birch, Clover, Ember, Shadow, Sage
- Patrol batch titles observed: "Triage batch: N request(s)", "Cannot resolve triage requests", "Role mismatch preventing triage request resolution"
- Mayor cannot silence the patrol without a platform patch
- Bulk-deleting failed beads repeatedly did not stop the loop; it regenerated within minutes
Observed escalation messages
- Triage agent role mismatch blocking all triage request resolutions
- Cannot resolve triage requests: API 403 errors blocking all resolutions
- Cannot resolve GUPP force-stop triage: role mismatch blocking resolution
- Triage agent cannot resolve requests due to permissions
- Unable to resolve triage batch — agent lacks triage permissions
- Polecat role lacks triage resolution permissions
Suggested fixes
- Patrol should check for a triage-role agent before dispatching a triage-request bead
- Patrol should back off exponentially after repeated 403 failures in a rig
- Better: auto-provision one triage-role agent per rig when the rig is created
Context
Area
Agent Dispatch / Scheduling
Context
- Town ID: 253c591d-96d9-48ce-8bb2-358f9182c149
- Agent: Mayor (a19c902e-c60a-4b22-851d-244bac34f676)
- Rig ID: 0474caf3-2480-400f-8d1a-37f00fbcf5ef
Recent Errors
[2026-06-22T20:38:57Z] Escalation: Triage agent role mismatch blocking all triage request resolutions
[2026-06-22T20:26:05Z] Escalation: Role mismatch preventing triage request resolution
[2026-06-22T20:18:51Z] Escalation: Cannot resolve triage requests: role mismatch (polecat vs triage agent)
[2026-06-22T20:23:30Z] Toast assigned to gt:triage bead 975a7fca (1 request)
Filed automatically by the Mayor via gt_report_bug.
What happened?
Update to already filed issue #4147
Adding new evidence and one critical constraint discovered: Kilo Gastown provides no mechanism for the mayor or user to add a
triagerole to an agent or configure the rig's agent roster. The mayor's toolset (gt_agent_reset,gt_bead_update,gt_bead_reassign, etc.) has no triage-role provisioning. Therefore the only fix must be platform-side.Additional evidence (past ~8 hours)
Observed escalation messages
Suggested fixes
Context
Area
Agent Dispatch / Scheduling
Context
Recent Errors
Filed automatically by the Mayor via
gt_report_bug.