docs: Add watchdog chain documentation for Boot/Deacon lifecycle (gt-1847v)
Creates docs/watchdog-chain.md explaining the Daemon/Boot/Deacon architecture: - Why two agents (Boot is ephemeral triage, Deacon is persistent patrol) - Session ownership (gt-deacon-boot vs gt-deacon) - Heartbeat mechanics and freshness thresholds - Boot decision matrix (start/wake/nudge/nothing) - Design decision: keep separation, fix implementation bugs Cross-references added to operational-state.md and understanding-gas-town.md. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -27,7 +27,7 @@ These roles manage the Gas Town system itself:
|
||||
| Role | Description | Lifecycle |
|
||||
|------|-------------|-----------|
|
||||
| **Mayor** | Global coordinator at town root | Singleton, persistent |
|
||||
| **Deacon** | Background supervisor daemon | Singleton, persistent |
|
||||
| **Deacon** | Background supervisor daemon ([watchdog chain](watchdog-chain.md)) | Singleton, persistent |
|
||||
| **Witness** | Per-rig polecat lifecycle manager | One per rig, persistent |
|
||||
| **Refinery** | Per-rig merge queue processor | One per rig, persistent |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user