55a80ce6e3
- Add ai-core/ — Chief, Scout, Scribe OpenClaw agents + shared knowledge base - Consolidate research/reference docs and the sns.md brand foundation under ai-core/knowledge/ - Repoint every sns.md reference (business branding, divisions, root README) to ai-core/knowledge/sns.md - Update root + ai-core READMEs to reflect the new structure
144 lines
9.6 KiB
Markdown
144 lines
9.6 KiB
Markdown
# AI Agent Teams as Employees — Research Synthesis
|
|
|
|
## Top Articles & Sources (Curated List)
|
|
|
|
| # | Title | Source | Why It Matters |
|
|
|---|-------|--------|----------------|
|
|
| 1 | [How to hire and manage AI agents like employees](https://frogslayer.com/blog/hire-manage-ai-agents-like-employees) | Frogslayer | Full lifecycle framework: define role → hire → onboard → supervise → performance review → fire. Treat agents like junior hires. |
|
|
| 2 | [How to Build AI Agent Departments That Run Your Startup While You Sleep](https://greyjournal.net/hustle/grow/how-to-build-ai-agent-departments/) | Grey Journal | Real case study of 8-department AI company (CEO, CFO, COO, Lawyer, Accountant, Marketing, CTO, Improver). Context engineering > prompt engineering. |
|
|
| 3 | [OpenClaw Multi-Agent Architecture: Production System Design](https://markaicode.com/architecture/openclaw-multi-agent-architecture/) | MarkAICode | Central orchestrator + specialized agent pool via async queues. Redis for state, PostgreSQL for persistence. Scaling playbook included. |
|
|
| 4 | [Building a Team of AI Agents with OpenClaw](https://hex-agent.hashnode.dev/building-a-team-of-ai-agents-with-openclaw) | Hashnode | Practical config walkthrough: multi-agent routing, per-agent isolation, channel bindings, agent-to-agent messaging, ACP coding sessions. |
|
|
| 5 | [Build a Multi-Agent OpenClaw System: Orchestrator + Sub-Agents in 15 Minutes](https://capodieci.medium.com/ai-agents-037-build-a-multi-agent-openclaw-system-without-config-hell-orchestrator-sub-agents-608be9385365) | Medium (Capodieci) | Quick-start guide for OpenClaw orchestrator pattern without config hell. |
|
|
| 6 | [AI Virtual Team: Build Your Specialist Agent Squad](https://www.digitalapplied.com/blog/ai-virtual-team-specialist-agent-squad-playbook) | Digital Applied | 10 specialist agent role cards with prompt libraries. $200-400/mo replaces 5-person team. Task delegation matrix. |
|
|
| 7 | [How to build a One-man AI Team](https://corpwaters.substack.com/p/how-to-build-a-one-man-ai-team) | Substack (CorpWaters) | Three-layer model: Brain (you) → Execution layer (agents) → Infrastructure (tools/APIs). China paying $720k for zero-employee startups. |
|
|
| 8 | [The Agentic Organization: A New Operating Model for AI](https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-agentic-organization-contours-of-the-next-paradigm-for-the-ai-era) | McKinsey | Enterprise-grade thinking: humans + AI agents side by side at scale at near-zero marginal cost. Org design implications. |
|
|
| 9 | [To Scale AI Agents Successfully, Think of Them Like Team Members](https://hbr.org/2026/03/to-scale-ai-agents-successfully-think-of-them-like-team-members) | Harvard Business Review | Deploying agents = change to how work gets done, not just software installation. |
|
|
| 10 | [How enterprises manage multi-agent AI workflows](https://dataiku.com/stories/blog/agent-orchestration-explained) | Dataiku | Four required components: task routing engine, memory/state layers, conflict resolution/guardrails, monitoring/observability. |
|
|
| 11 | [Enterprise Agent Architecture: Production Blueprint](https://markaicode.com/architecture/enterprise-agent-architecture/) | MarkAICode | DAG of components: orchestrator, agents, tools, memory, observation. LangGraph + Kubernetes + OpenTelemetry stack. |
|
|
| 12 | [AI Agent Orchestration Patterns](https://learn.microsoft.com/en-us/azure/architecture/ai-ml/guide/ai-agent-design-patterns/) | Microsoft Azure | Peer-based vs orchestrator patterns. Work distribution, context sharing, result aggregation. |
|
|
| 13 | [How Solopreneurs Are Building Million Dollar Businesses With AI Agent Teams](https://greyjournal.net/hustle/work-tech/solopreneur-ai-agent-teams-million-dollar-business/) | Grey Journal | 340% revenue increase reported by solo founders using AI agents. |
|
|
| 14 | [Best Multi-agent Orchestration Frameworks in 2026](https://www.truefoundry.com/pt/blog/multi-agent-orchestration-frameworks) | TrueFoundry | CrewAI vs LangGraph vs AutoGen comparison. 40% of enterprise apps will include agents by end of 2026 (Gartner). |
|
|
| 15 | [How To Onboard 'Digital Employees'](https://www.freshworks.com/theworks/employee-experience/onboarding-digital-employees/) | Freshworks | 7/10 businesses integrating agents in 2026. Onboarding process for digital employees. |
|
|
| 16 | [OpenClaw Production Guide: 4 Weeks Self-Hosted AI](https://www.sitepoint.com/openclaw-production-lessons-4-weeks-self-hosted-ai/) | SitePoint | Real production lessons: declarative config, agent roles, tool connections, lifecycle management. |
|
|
| 17 | [Agentic AI Strategy (Tech Trends 2026)](https://www.deloitte.com/us/en/insights/topics/technology-management/tech-trends/2026/agentic-ai-strategy.html) | Deloitte | 15% of day-to-day work decisions made by agentic AI by 2028 (Gartner). Strategic framing. |
|
|
|
|
---
|
|
|
|
## Key Architectural Patterns
|
|
|
|
### 1. The Orchestrator + Specialist Pool (OpenClaw Native)
|
|
|
|
```
|
|
┌─────────────────────┐
|
|
│ ORCHESTRATOR │ (ClawChief / Router)
|
|
│ - Task decomp │
|
|
│ - Agent selection │
|
|
│ - Result merging │
|
|
└──────────┬──────────┘
|
|
│ async queues
|
|
┌───────────┼───────────────┐
|
|
▼ ▼ ▼
|
|
┌─────────┐ ┌─────────┐ ┌─────────┐
|
|
│ Agent A │ │ Agent B │ │ Agent N │
|
|
│ (Email) │ │ (Phone) │ │ (Fin) │
|
|
└─────────┘ └─────────┘ └─────────┘
|
|
```
|
|
|
|
- Each agent: isolated workspace, own SOUL.md, own tools, own session history
|
|
- Communication via agent-to-agent messaging (opt-in)
|
|
- Routing via channel bindings (WhatsApp → personal, Telegram → work, etc.)
|
|
|
|
### 2. The Employee Lifecycle (Frogslayer Model)
|
|
|
|
1. **Define the Role** — One-sentence job, success metrics, out-of-scope boundaries, escalation rules
|
|
2. **Hire (Deploy)** — Pick model, build prompt-as-job-description, minimum tool set, test on real work
|
|
3. **Onboard** — Context library (SOPs, brand guides, history), first-week human review, feedback loop
|
|
4. **Supervise** — Named supervisor, review cadence (light for low-stakes, inline for high-stakes)
|
|
5. **Performance Manage** — KPIs, monthly measurement, failure mode analysis, prompt/context improvement
|
|
6. **Fire (Retire)** — Document why, communicate change, hand off work, archive, retrospective
|
|
|
|
### 3. The Three-Layer Model (CorpWaters)
|
|
|
|
| Layer | What | Who/What |
|
|
|-------|------|----------|
|
|
| Brain | Direction, judgment, kill decisions | You (Sam) |
|
|
| Execution | Task completion, content, comms, ops | AI Agents |
|
|
| Infrastructure | APIs, databases, tools, hosting | OpenClaw + self-hosted stack |
|
|
|
|
### 4. Context Engineering > Prompt Engineering
|
|
|
|
Don't write clever one-shot prompts. Build **information ecosystems**:
|
|
- SOPs per agent
|
|
- Brand guidelines
|
|
- Customer/personal history
|
|
- Past decisions and outcomes
|
|
- Performance feedback loops
|
|
|
|
### 5. The 80/20 Rule
|
|
|
|
- **80% AI execution** — repetitive, high-volume, pattern-following work
|
|
- **20% human taste** — judgment calls, strategy, edge cases, relationship building, approval gates
|
|
|
|
---
|
|
|
|
## OpenClaw-Specific Architecture for Your Setup
|
|
|
|
### How OpenClaw Multi-Agent Works
|
|
|
|
- **One gateway process** runs all agents
|
|
- Each agent has: own `agentDir`, own workspace, own session store, own auth profiles
|
|
- **Routing via bindings**: channel → agent mapping (most-specific match wins)
|
|
- **Orchestrator pattern**: main agent dispatches sub-agents for parallel tasks
|
|
- **Concurrency controls**: `maxConcurrent` (global lanes), `maxChildrenPerAgent` (per-session fan-out)
|
|
- **Agent-to-agent messaging**: opt-in, scoped to allowed agent IDs
|
|
|
|
### Config Structure (per agent)
|
|
```
|
|
~/.openclaw/agents/<agentId>/
|
|
├── workspace/
|
|
│ ├── SOUL.md # personality + operating instructions
|
|
│ ├── MEMORY.md # persistent context
|
|
│ ├── TOOLS.md # available tools
|
|
│ └── PLAYBOOK.md # SOPs
|
|
├── agent/
|
|
│ └── auth-profiles.json
|
|
└── sessions/
|
|
```
|
|
|
|
### Key Commands
|
|
```bash
|
|
openclaw agents add <name> # create new agent
|
|
openclaw agents list --bindings # see routing
|
|
openclaw config set ... # per-agent config
|
|
```
|
|
|
|
---
|
|
|
|
## What Agents Are Best At (Deploy First)
|
|
|
|
1. **Inbox triage & drafting** — first-touch on routine inbound
|
|
2. **Research synthesis** — pulling context before decisions
|
|
3. **Document review & extraction** — at scale with human approval
|
|
4. **Workflow coordination** — moving work between systems based on rules
|
|
5. **Reporting drafts** — first-pass narrative from data
|
|
6. **Customer support** — 60-80% ticket resolution without human
|
|
7. **Phone answering / receptionist** — 24/7 call handling, booking, routing
|
|
|
|
## What Agents Are Worst At (Keep Human)
|
|
|
|
1. Novel judgment under ambiguity
|
|
2. Trust-laden customer-facing interactions (brand on the line)
|
|
3. Decisions with severe consequences + no recovery path
|
|
4. Deep relationship building
|
|
5. Original creative vision
|
|
|
|
---
|
|
|
|
## Your Deployment: Phase 1 (OpenClaw on racknerd3)
|
|
|
|
- All agents run in one OpenClaw gateway on your VPS (3.3GB RAM, 2 vCPU)
|
|
- Start with 3-4 agents, expand as you validate each one
|
|
- Keep it lean: one orchestrator + specialized workers
|
|
- Human-in-the-loop for all financial actions and customer-facing business comms
|
|
- Separate bindings: personal channels → personal agents, business channels → business agents
|