Knuckles-Team Full Ecosystem Health Workflow
CONCEPT:KG-2.12
End-to-end ecosystem health check across containers, system resources, workspace, and observability stack. This is the "canary" workflow that validates all infrastructure layers are operational.
Steps
Step 0: Systems Manager
Agent: intake-agent
Tools: graph_query, nc_files
Get system memory, CPU, and disk stats
Expected: memory, cpu
Step 1: Container Manager Mcp
Agent: processor-agent
Tools: graph_analyze, document_tools
List all running Docker containers and their health status
Expected: container, running
Step 2: Langfuse Mcp
Agent: validator-agent
Tools: graph_query
Check Langfuse health and list recent traces
Expected: health
Step 3: Repository Manager Mcp
Agent: report-agent
Tools: graph_write, document_tools
List workspace actions and verify workspace configuration
Expected: workspace, list
Step 4: KG Persistence [depends_on: repository-manager-mcp]
Agent: report-agent
Tools: graph_write
Persist workflow results as nodes and edges in the Knowledge Graph. Create appropriate typed nodes with metadata and link to existing domain entities.
Output
- Full Ecosystem Health results persisted in KG
- Structured report (MD/PDF)
- Audit trail with timestamps and agent attributions
Human Oversight Required
✅ Critical decisions require human review and approval.
Execution
Run this workflow as a dependency-ordered DAG. Steps with no unmet depends_on run in parallel; dependents run after their prerequisites complete.
- Run first (in parallel): Step 0 — Systems Manager; Step 1 — Container Manager Mcp; Step 2 — Langfuse Mcp; Step 3 — Repository Manager Mcp
- After level 0: Step 4 — KG Persistence
Execution: If graph-os is reachable, offload the whole DAG via graph_orchestrate action=execute_workflow (or the kg-delegate skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet depends_on in parallel, then their dependents.