patrol-monitoring

Solid

Continuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery.

AI & Automation 814 stars 53 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
53
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Patrol Monitoring ## Overview Continuous monitoring using Gas Town's Deacon/Witness pattern. The Deacon supervises overall health, the Witness manages per-rig agent lifecycle, and the Boot (Dog) watches the Deacon itself. ## When to Use - During active convoy execution - When agents may become stuck or unresponsive - For long-running multi-agent workflows - When automated recovery is desired ## Process 1. **Health check** all active agents and convoys 2. **Detect** stuck or unresponsive agents via heartbeats 3. **Recover** - restart, reassign, or escalate as needed 4. **Report** patrol findings with trend analysis ## Monitoring Roles - **Deacon**: Daemon supervisor, monitors overall health - **Witness**: Per-rig lifecycle manager for workers - **Boot (Dog)**: Watches the Deacon every 5 minutes ## Recovery Modes - **restart**: Restart the stuck agent session - **reassign**: Move beads to a different agent - **escalate**: Alert human for manual intervention ## Tool Use Invoke via babysitter process: `methodologies/gastown/gastown-patrol`

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Related Skills