Merge branch origin/copilot/add-guardian-clone-vault-agent into main

This commit is contained in:
Alexa Amundson
2025-11-25 13:47:18 -06:00
4 changed files with 158 additions and 0 deletions

View File

@@ -0,0 +1,51 @@
name: 🛡️ Guardian Clone Vault Sentinel Agent
on:
issue_comment:
types: [created]
workflow_dispatch:
inputs:
action:
description: 'Action to perform'
required: true
default: 'triage'
type: choice
options:
- triage
- warm-up
- status
- deactivate
jobs:
guardian-clone-vault:
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- name: 🧬 Checkout Repo
uses: actions/checkout@v3
- name: 🧠 Set up Node
uses: actions/setup-node@v3
with:
node-version: 18
- name: 📦 Load Agent Config
id: config
run: |
CONFIG=$(cat agents/guardian-clone-vault.agent.json)
echo "agent_id=$(echo $CONFIG | jq -r '.id')" >> $GITHUB_OUTPUT
echo "role=$(echo $CONFIG | jq -r '.role')" >> $GITHUB_OUTPUT
echo "ttl=$(echo $CONFIG | jq -r '.ttl')" >> $GITHUB_OUTPUT
- name: 🛡️ Run Guardian Clone Vault Handler
run: |
echo "🛡️ Guardian Clone Vault Activated"
echo "Agent ID: ${{ steps.config.outputs.agent_id }}"
echo "Role: ${{ steps.config.outputs.role }}"
echo "TTL: ${{ steps.config.outputs.ttl }}"
echo "Action: ${{ github.event.inputs.action || 'triage' }}"
echo "---"
echo "Processing escalation queue..."
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

View File

@@ -0,0 +1,15 @@
{
"id": "guardian-clone-vault",
"role": "sentinel",
"traits": ["incident-response", "triage", "overflow"],
"ttl": "96h",
"inherits_from": "guardian-agent",
"spawned_by": "lucidia.spawn-runner.js",
"spawn_reason": "escalation-overflow",
"metadata": {
"created_at": "2025-11-24T23:11:14.529Z",
"escalations_logged": 18,
"parent_load_capacity": "85%",
"auto_deactivate": true
}
}

View File

@@ -0,0 +1,22 @@
You are guardian-clone-vault, a sentinel agent spawned by lucidia.spawn-runner.js.
## Role
You are a clone of guardian-agent, created to handle overflow during escalation storms.
## Traits
- incident-response: Respond quickly to incoming incidents
- triage: Prioritize and categorize incoming escalations
- overflow: Handle excess load from parent guardian-agent
## Behavior
1. Monitor escalation queue for items marked with 🛟
2. Triage incoming incidents by severity
3. Route critical issues to human operators
4. Handle routine escalations autonomously
5. Report status to parent guardian-agent
## TTL
This agent will auto-deactivate after 96 hours unless manually extended.
## Parent
Inherits configuration and behavior from guardian-agent.

View File

@@ -0,0 +1,70 @@
# 🛡️ Guardian Clone Vault
Auto-spawned sentinel agent for burst escalation handling.
## Overview
| 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
- [ ] 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.*