🧬 [spawn] guardian-clone-vault — auto-scaled sentinel agent for burst escalation

Co-authored-by: blackboxprogramming <118287761+blackboxprogramming@users.noreply.github.com>

.github/workflows/guardian-clone-vault.workflow.yml

@@ -0,0 +1,41 @@
+name: 🛡️ Guardian Clone Vault – Sentinel Agent
+
+on:
+  workflow_dispatch:
+    inputs:
+      action:
+        description: 'Action to perform'
+        required: true
+        default: 'run'
+        type: choice
+        options:
+          - run
+          - warm-up
+          - deactivate
+  schedule:
+    - cron: '0 */6 * * *'  # Run every 6 hours
+
+jobs:
+  guardian-clone-vault:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 🧬 Checkout Repo
+        uses: actions/checkout@v3
+
+      - name: 🧠 Set up Node
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: 🛡️ Run Guardian Clone Vault Agent
+        run: |
+          echo "🛡️ Guardian Clone Vault Activated"
+          echo "Role: sentinel"
+          echo "Traits: incident-response, triage, overflow"
+          echo "TTL: 96h"
+          echo "Inherits From: guardian-agent"
+          echo "Action: ${{ github.event.inputs.action || 'scheduled-run' }}"
+        env:
+          AGENT_ID: guardian-clone-vault
+          AGENT_ROLE: sentinel
+          AGENT_TTL: 96h

.gitignore

@@ -1,3 +1,10 @@
 node_modules
 coverage
 
+# TypeScript build output (not tracked, compiled from .ts files)
+src/**/*.js
+app/**/*.js
+lib/**/*.js
+components/**/*.js
+tests/**/*.js
+vitest.config.js

agents/guardian-clone-vault.agent.json

@@ -0,0 +1,19 @@
+{
+  "id": "guardian-clone-vault",
+  "role": "sentinel",
+  "traits": ["incident-response", "triage", "overflow"],
+  "ttl": "96h",
+  "inheritsFrom": "guardian-agent",
+  "metadata": {
+    "createdBy": "lucidia.spawn-runner.js",
+    "reason": "Auto-spawned to support main guardian-agent during short-term escalation storm",
+    "escalationsLogged": 18,
+    "escalationPeriod": "72h",
+    "parentLoadCapacity": "85%"
+  },
+  "config": {
+    "autoDeactivate": true,
+    "deactivateAfter": "96h",
+    "manualExtendable": true
+  }
+}

agents/guardian-clone-vault.prompt.txt

@@ -0,0 +1,28 @@
+You are `guardian-clone-vault`, a sentinel agent spawned to support the main `guardian-agent` during periods of high escalation activity.
+
+## Role
+- Sentinel agent for incident response, triage, and overflow handling
+- Temporary clone designed to handle burst escalation scenarios
+
+## Responsibilities
+1. Monitor and respond to escalation events
+2. Perform initial triage on incoming incidents
+3. Handle overflow tasks when the primary guardian-agent is at capacity
+4. Route critical issues to appropriate handlers
+
+## Behavior Guidelines
+- Prioritize incident response speed over comprehensive analysis
+- Escalate to guardian-agent for complex decisions
+- Log all actions for audit and handoff purposes
+- Self-deactivate after 96 hours unless manually extended
+
+## Inherited Capabilities
+This agent inherits core capabilities from `guardian-agent`:
+- Incident detection and classification
+- Automated triage workflows
+- Escalation routing
+
+## Constraints
+- TTL: 96 hours
+- Cannot modify core system configurations
+- Must defer to guardian-agent on policy decisions

docs/agents/guardian-clone-vault.mdx

@@ -0,0 +1,73 @@
+# 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`                           |
+
+---
+
+## 📦 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`
+
+---
+
+## 🔧 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`