Universal 14 Agent Blueprint

STANDARD AGENT ROSTER — SAME ROLES, ANY NICHE — INSTRUCTIONS CHANGE, PIPELINE DOESN'T

1 — Current State: sitzio.de
2
Agents Live
15/15
Issues Done
Backlog
Project Status
12
Agents Missing
0
CEO Runs
Researcher
Status: idle · Adapter: codex_local (gpt-5.4)
Heartbeat: 300s · Last beat: 09:39 UTC
Work done: 16 Codex sessions, 15 issues completed
Output: 8 competitor deep-dives, 60+ screenshots
Completed all research
CEO
Status: idle · Adapter: codex_local (gpt-5.4)
Heartbeat: 300s · Last beat: 07:56 UTC
Work done: 0 sessions, 0 issues executed
Log: "pre-screen skip — no changes since last heartbeat"
Idle — no issues assigned
The gap: Research is done. But nobody has created strategy issues, nobody is designing, coding, writing content, or deploying. The CEO has never run because no work was assigned to it. The project is stuck in backlog status. 12 more agents are needed to go from research to live site.
2 — The Universal 14 Agent Roster
Same 14 roles for every niche. When Scout discovers a new niche, Paperclip provisions these 14 agents. Each gets niche-specific AGENTS.md instructions injected. The roles, pipeline, and heartbeat mechanism are identical across all companies.
CEO
#1
Orchestrator
Strategy, delegation, prioritization. Creates issues for all other agents. Reviews output, makes go/no-go decisions.
Per niche: mission, goals, budget
Researcher
#2
Intelligence
Competitor analysis, feature extraction, UX testing, SEO audit. Runs pre-launch and ongoing surveillance.
Per niche: keywords, competitors, market
Strategist
#3
Planning
Keyword architecture, URL structure, content calendar, sitemap. Bridges Research to Content.
Per niche: keyword clusters, content types
Designer
#4
Visual
Design system, components, tokens, brand, OG images, icons, all visual assets.
Per niche: aesthetic, audience
Developer
#5
Engineering
All code: core app, integrations, i18n, technical SEO. The heaviest token spender.
Per niche: tech stack, features, APIs
Writer
#6
Content
Landing pages, blog posts, UI copy, documentation, help center. Gets briefs from Strategist.
Per niche: language, tone, domain
Quality
#7
Gate
Functional tests, content uniqueness, E-E-A-T, accessibility (WCAG), security. Nothing ships without approval.
Per niche: thresholds, standards
Compliance
#8
Legal
Privacy pages, terms, procurement packages, jurisdiction-specific docs (DSGVO/GDPR/CCPA).
Per niche: jurisdiction, regulations
Ops
#9
Infrastructure
Deploy, CI/CD, domain, SSL, payments, CWV monitoring, uptime, broken links, content decay.
Per niche: hosting, payments
Growth
#10
Acquisition
SEO tracking, directory listings, outreach, link building, influencer seeding, community presence.
Per niche: channels, communities
Revenue
#11
Monetization
Pricing, conversion funnels, retention, social proof, churn prevention, dunning.
Per niche: pricing model, customer
Support
#12
User Ops
Knowledge base, ticket triage, feedback collection, cancellation surveys, bug escalation.
Per niche: product domain, FAQs
Comms
#13
Outbound
Onboarding drips, feature emails, newsletters, win-back campaigns, seasonal pushes.
Per niche: sequences, events, tone
Analytics
#14
Intelligence
Data synthesis, weekly CEO briefs, KPI tracking, anomaly detection, first-party data content.
Per niche: KPIs, data sources
3 — Automated Pipeline Flow
Phase 1
Intelligence
Before any code is written. Scout discovers the niche, Researcher maps the competition, Strategist plans the architecture.
Trigger
Scout
Platform
→
Create
Company
14 agents
→
Execute
Research
Researcher
→
Review
Strategy
CEO
→
Plan
Architecture
Strategist
CEO creates build issues
Phase 2
Build & Ship
Design, develop, write, validate, comply, deploy. Each agent works its queue. Quality gates everything before Ops ships it.
Step 1
Design
Designer
→
Step 2
Build
Developer
→
Step 3
Write
Writer
→
Step 4
Comply
Compliance
→
Gate
Test
Quality
→
Ship
Deploy
Ops
site goes live — continuous loop begins
Phase 3
Operate & Grow
Continuous loop. Agents monitor, acquire, optimize, support, communicate, and synthesize. Analytics feeds CEO, CEO creates new issues, cycle repeats forever.
Acquire
Growth
Growth
→
Convert
Revenue
Revenue
→
Retain
Support
Support
→
Engage
Comms
Comms
→
Monitor
Health
Ops
→
Synthesize
Report
Analytics
→
Decide
Iterate
CEO
4 — The Heartbeat Engine
How Paperclip drives everything. There is no event bus, no webhook chain. Every agent runs on a 300-second heartbeat timer. When the heartbeat fires, the agent checks its inbox. If there is an assigned issue, it wakes up, spawns a Codex session, executes autonomously, and reports back. If no work exists, it skips. This is why the CEO shows pre-screen skip in logs — nobody assigned it any issues.
Every 300s
Heartbeat Fires
Paperclip timer ticks for each agent on its configured interval
Pre-screen
Check Inbox
Any assigned issues? Any mentions? Any wakeup requests?
If work
Spawn Codex
Checkout issue, start codex_local session with AGENTS.md
Execute
Autonomous Work
Agent uses MCP tools (Playwright, Serper, Qdrant...) to complete the task
Done
Report & Close
Post results to Paperclip issue, mark done, return to idle
The Issue Queue is Everything
CEO Creates
Issues with clear deliverables, assigns to specific agents. "Design the landing page" → Designer. "Write the Datenschutz" → Writer.
Agent Wakes
On next heartbeat, agent sees assigned issue, checks it out (atomic lock), spawns Codex session, works the task.
Cycle Repeats
Agent closes issue, posts output. CEO reads result on next heartbeat, creates follow-up issues. The queue never empties in Phase 3.
5 — Niche Portability: Same Pipeline, Different Instructions
sitzio.de
SEATING PLAN GENERATOR
  • German SEO keywords
  • Education directories (Lehrer-Online)
  • DSGVO compliance + AVV
  • React + TypeScript + Vite
  • Teacher communities (#instalehrerzimmer)
  • Freemium: EUR 2-3/mo
  • Schuljahresbeginn seasonal push
  • WebUntis / IServ integrations
=
Same 14
agents
Different
AGENTS.md
image-optimizer.io
IMAGE COMPRESSION TOOL
  • English SEO keywords
  • Developer directories (Product Hunt)
  • GDPR + CCPA compliance
  • Next.js + WebAssembly
  • Developer communities (HN, Reddit)
  • Freemium: $5/mo
  • Black Friday seasonal push
  • Cloudflare / Vercel integrations
The universal pattern: Scout finds a niche → Paperclip creates company → injects niche-specific AGENTS.md into each of the 14 standard agents → CEO starts creating issues → pipeline runs identically. The roles are fixed. The instructions are variable. The infrastructure is shared. That is the entire system.
What Paperclip Provisions Per Company
Fixed (never changes)
14 agent roles
Codex adapter config
Heartbeat timers (300s)
Issue queue + checkout
Paperclip API access
MCP servers (Playwright, Qdrant)
Variable (per niche)
AGENTS.md instructions
Target keywords + competitors
Tech stack + features
Jurisdiction + regulations
Distribution channels
Pricing model + tiers
Bootstrap input
Domain name
Source site analysis
Competitor list
Monetization strategy
Verdict + risk assessment
Recommended tech stack