1.4 KiB
1.4 KiB
Standing Subagent Roles Specification
Captured from the Jul 8-9, 2026 sessions. These are persistent team definitions, not one-off delegations.
Network Services Team
Standing SME team for managing servers/systems infrastructure.
| Role | Domain | Responsibility |
|---|---|---|
| Team Lead | Orchestrator | Delegates tasks, reports to Germaine, coordinates across SME subs |
| Server Admin | Hetzner/netcup | Inventory, provisioning, health monitoring, spec management |
| Network Engineer | MikroTik/Ubiquiti/DNS | Router configs, tower backups, connectivity, topology |
| Backup Specialist | S3/DR | Bucket management, restore testing, sync scripts |
| UI Specialist | Dashboard/accessibility | Page builds, W3C pass, mobile UX, interactive patterns |
UI Team
Standing design team for modern interface creation.
| Role | Responsibility |
|---|---|
| Lead Designer | Art direction, layout, composition |
| HTML/CSS Specialist | W3C-compliant implementation, accessibility enforcement |
| Visual/Comm Artist | Graphic design, color, typography, branding |
Works with the interactive design team. Separate from Network Services Team's UI Specialist (who handles ops dashboard/accessibility).
When to use standing teams vs ad-hoc delegation
- Use standing team for recurring classes of work
- Delegate to Team Lead (role=orchestrator) who further delegates to SME leads
- Use ad-hoc for one-off tasks