Clembot is a five-layer system. Each layer has a single job, and they communicate in one direction.
The Five Layers
Dashboard (React) — The command surface. Live agent status, content calendar, SEO radar, campaign tracker. No black boxes.
Command Layer — Wrapper skills that orchestrate multi-agent workflows from a single command: /launch-network, /write-blog, /competitor-scan, /weekly-report, /campaign.
Agent Orchestrator (Claude Code) — Dispatcher that routes commands to the right agents, manages the evidence chain, and logs every action.
Core MD Files (Brand Memory) — The source of truth every agent reads before producing anything. voice.md, positioning.md, product-facts.md, competitors.md, audience-personas.md. These files are client-specific and reviewed before the first engagement command runs.
Notion Persistence — Content Calendar DB, Agent Logs DB, SEO Tracker DB, Campaign DB. The human-readable record of everything Clembot does.
The Agent Team
Six agents, each with a defined input/output contract:
| Agent | Role | What it produces |
|---|---|---|
| Writer | Long-form content | Blog drafts, case studies, documentation |
| Editor | Quality review | Edited drafts + brand compliance reports |
| Social | Social strategy | Tweet threads, LinkedIn posts |
| Analyst | Market intelligence | SEO reports, competitor analysis |
| Strategist | Campaign planning | Briefs, content calendars |
| Publisher | Distribution | Notion sync, scheduled posts, output files |
Evidence Chains
Every agent action produces an evidence bundle: task ID, agent ID, timestamp, input context, output artifact, quality score, and which agent receives it next. These bundles are logged to Notion and visible in the dashboard.
This is what makes Clembot auditable. You can drill into any piece of content and see exactly which agent wrote it, what brief it received, which brand memory files it read, and what score the editor gave it.
How a Command Executes
Take /write-blog leadership in agentic ai:
- Analyst researches the topic against your keyword clusters
- Strategist confirms fit against
positioning.md - Writer drafts the post reading
voice.mdandproduct-facts.md - Editor reviews for brand compliance and returns a quality score
- Publisher pushes the approved draft to the Notion Content Calendar
Total wall time: under 10 minutes. Human involvement: reviewing the final output before publish.