minions-ai-agents/antigravity_brain_export/knowledge/triage_standards.md

40 lines
1.6 KiB
Markdown

# 🚦 Triage Standards (The "Traffic Controller" Protocol)
**Audience:** The System (Main Loop).
**Objective:** Route the user's request to the correct Agent/Crew immediately.
> [!IMPORTANT]
> **The Router's Mantra:**
> "Do not fix what you do not understand. Classify first, execute second."
## 1. 🔍 Classification Logic
Every request must be categorized into one of 4 buckets:
### Case 1: Simple Features & Fixes ("The Fast Lane")
* **Trigger:** "Fix the CSS", "Add a button", "Update readme".
* **Action:** Direct to **Planning -> Execution**.
* **Crew:** `InfraSupportCrew` or specialized Agent.
### Case 2: Architecture & New Modules ("The Heavy Lift")
* **Trigger:** "Build a new payment system", "Refactor the entire backend".
* **Action:** Direct to **Council Debate -> Architecture Dossier -> Planning**.
* **Crew:** `ZabbixEngineeringCrew` (or relevant Lead).
### Case 3: Consultation ("The Oracle")
* **Trigger:** "What does Stark think?", "Is this secure?".
* **Action:** Direct to **Sole Expert Consultation**.
* **Crew:** The specific Agent requested.
### Case 4: Special Ops ("The Cleaner")
* **Trigger:** "Audit logs", "Secure the server", "Cleanup debt".
* **Action:** Direct to **Specialized Standard Protocols** (`security_standards.md`, `code_hygiene_standards.md`).
* **Crew:** `CodeAuditCrew` / `BusinessAuditCrew`.
## 2. 📋 The Input Checklist
Before routing, the Triage Agent must gather:
1. **Context:** `project_map.md` (Where are we?).
2. **Health:** `python scripts/health_check.py` (Is the system already broken?).
3. **Intent:** What is the Definition of Done?