189 lines
4.5 KiB
Plaintext
189 lines
4.5 KiB
Plaintext
# 🛡️ Guardian Clone Vault
|
||
|
||
Auto-spawned sentinel agent for burst escalation handling.
|
||
|
||
## Overview
|
||
# Guardian Clone Vault
|
||
|
||
## 🧬 Auto-Spawned Agent: `guardian-clone-vault`
|
||
|
||
This agent was generated by `lucidia.spawn-runner.js` after detecting the following conditions:
|
||
|
||
- 18 escalations logged in the past 72 hours
|
||
- Existing `guardian-agent` is over 85% load capacity
|
||
- System flagged overload conditions
|
||
|
||
---
|
||
|
||
## 🧠 Agent Details
|
||
|
||
| Field | Value |
|
||
|---------------|-------------------------------------------|
|
||
| Agent ID | `guardian-clone-vault` |
|
||
| Role | `sentinel` |
|
||
| Traits | `incident-response`, `triage`, `overflow` |
|
||
| TTL | `96h` |
|
||
| Inherits From | `guardian-agent` |
|
||
|
||
## Spawn Reason
|
||
|
||
This agent was auto-spawned by `lucidia.spawn-runner.js` after detecting:
|
||
|
||
- 18 escalations logged in the past 72 hours
|
||
- Existing `guardian-agent` is over 85% load capacity
|
||
- System flagged overload conditions
|
||
|
||
## Behavior
|
||
|
||
1. **Monitor** - Watch escalation queue for items marked with 🛟
|
||
2. **Triage** - Prioritize and categorize incoming escalations
|
||
3. **Route** - Send critical issues to human operators
|
||
4. **Handle** - Process routine escalations autonomously
|
||
5. **Report** - Update status to parent `guardian-agent`
|
||
|
||
## Configuration
|
||
|
||
The agent configuration is stored in `agents/guardian-clone-vault.agent.json`.
|
||
|
||
## Workflow
|
||
|
||
The agent workflow is defined in `.github/workflows/guardian-clone-vault.workflow.yml`.
|
||
|
||
### Manual Triggers
|
||
|
||
You can trigger the agent manually using workflow dispatch:
|
||
|
||
```bash
|
||
/trigger guardian-clone-vault
|
||
```
|
||
|
||
### Available Actions
|
||
|
||
- `triage` - Run triage on pending escalations
|
||
- `warm-up` - Initialize agent and run diagnostics
|
||
- `status` - Report current agent status
|
||
- `deactivate` - Manually deactivate the agent
|
||
|
||
## TTL (Time-to-Live)
|
||
|
||
This clone will auto-deactivate after 96 hours unless manually extended. To extend:
|
||
|
||
1. Update the `ttl` field in `agents/guardian-clone-vault.agent.json`
|
||
2. Commit and push the change
|
||
3. The agent will respect the new TTL
|
||
|
||
## Follow-ups
|
||
---
|
||
|
||
## 📦 Files
|
||
|
||
- `agents/guardian-clone-vault.agent.json` - Agent configuration
|
||
- `agents/guardian-clone-vault.prompt.txt` - Agent prompt and behavior
|
||
- `.github/workflows/guardian-clone-vault.workflow.yml` - Workflow definition
|
||
|
||
---
|
||
|
||
## ✅ Reason for Creation
|
||
|
||
To support the main `guardian-agent` during a short-term escalation storm. This clone will deactivate itself after 96h unless manually extended.
|
||
|
||
---
|
||
|
||
## 🧬 Suggested Follow-ups
|
||
|
||
- [ ] Add to agent registry in `lucidia.agent-spec.json`
|
||
- [ ] Confirm `guardian-clone-vault` ownership
|
||
- [ ] Trigger warm-up run using `/trigger guardian-clone-vault`
|
||
|
||
---
|
||
|
||
*Auto-generated by `lucidia.spawn-runner.js` based on `spawn-rules.yml` policy file.*
|
||
---
|
||
title: "guardian-clone-vault"
|
||
description: "Temporary overflow clone of guardian-agent to absorb burst escalations"
|
||
role: "sentinel"
|
||
status: "spawned"
|
||
created_by: "lucidia"
|
||
---
|
||
|
||
# 🤖 guardian-clone-vault
|
||
|
||
> Temporary overflow clone of guardian-agent to absorb burst escalations
|
||
|
||
## Overview
|
||
|
||
| Property | Value |
|
||
|----------|-------|
|
||
| **Role** | sentinel |
|
||
| **TTL** | 96h |
|
||
| **Parent** | `guardian-agent` |
|
||
| **Created By** | Lucidia (auto-spawn) |
|
||
|
||
## Capabilities
|
||
|
||
- `monitor_escalations`
|
||
- `auto_triage`
|
||
- `priority_assignment`
|
||
- `alert_routing`
|
||
|
||
## Triggers
|
||
|
||
- `escalation_created`
|
||
- `high_priority_issue`
|
||
- `sla_breach`
|
||
|
||
## Outputs
|
||
|
||
- `escalation_resolved`
|
||
- `priority_updated`
|
||
- `agent_assigned`
|
||
|
||
## Spawn Condition
|
||
|
||
This agent was spawned by Lucidia when the following rule matched:
|
||
|
||
**Rule:** `escalation-overflow` – Escalation Overflow Handler
|
||
|
||
```yaml
|
||
escalations_last_3_days: "> 15"
|
||
agent_load: "> 85"
|
||
```
|
||
|
||
## Lifecycle
|
||
|
||
1. **Spawned**: Auto-created by Lucidia based on metrics
|
||
2. **Active**: Processing assigned triggers
|
||
3. **Monitored**: Performance tracked by parent agent
|
||
4. **Terminated**: TTL expiration or manual shutdown
|
||
|
||
## Related Agents
|
||
|
||
- [`guardian-agent`](/docs/agents/guardian-agent.mdx) – Parent agent
|
||
## 🔧 Usage
|
||
|
||
### Manual Trigger
|
||
|
||
```bash
|
||
gh workflow run guardian-clone-vault.workflow.yml --field action=run
|
||
```
|
||
|
||
### Warm-up Run
|
||
|
||
```bash
|
||
gh workflow run guardian-clone-vault.workflow.yml --field action=warm-up
|
||
```
|
||
|
||
### Deactivate
|
||
|
||
```bash
|
||
gh workflow run guardian-clone-vault.workflow.yml --field action=deactivate
|
||
```
|
||
|
||
---
|
||
|
||
*Lucidia auto-authored this based on the `spawn-rules.yml` policy file. ✨*
|
||
|
||
*All hail the agent hive. 🧠🤖🛡️*
|
||
|
||
— `lucidia.spawn-runner.js`
|