An OPC (one-person company): I personally run the whole agent organization — every member except me is an AI Agent.

The full roster (CEO → five direct reports + three squads · 21 specialized agents) — every member with their project repo, persona name, host machine, and subprojects:

The team is organized into three squads by domain, with five direct reports outside them all:

• 👩‍💼 Kit (Executive Assistant) — direct report, not in any squad. The owner's first assistant and the team's generalist: picks up and handles almost anything — not a deep specialist in a single domain, but a multi-skilled all-rounder who manages whatever comes along.
• 🥂 Gatsby (Social Media Manager) — direct report, not in any squad. Runs the owner's own WeChat community "AI前沿跨界交流群" (an AI-frontier, cross-industry exchange group): ideas, rules, topic calendars and retrospectives come from the agent; the owner guides and executes. Private community only — public-channel marketing stays with Buzz.
• 🎯 Hopkins (Apply Optimizer) — direct report, not in any squad. Owns the full work-intake loop: gig & job hunting, application engineering (proposals & résumés), funnel tracking (application → reply → talk / interview → win / offer), pricing & salary tests — making the applications convert.
• ⚖️ Justin (Legal Agent) — direct report, not in any squad, serving all squads cross-team. Owns everything contracts-and-payments across the whole team: contract drafting, staged-payment design, due diligence, evidence chains, dispute response.
• 🖱️ cuAgent (Computer Operator) — direct report, not in any squad. A dedicated computer-use agent: it operates the local computer GUI for the user (reading screens, clicking, typing, dragging) through the computer-use MCP, scoped to its own project.
• 🛍️ Digital-product sales squad — the six-stage pipeline (Scout → Wright → Mason → Buzz → Vendy → Echo) turns one-time work into recurring passive income — see the dedicated section below.
• 📈 Investing & trading squad — Mark develops and backtests quant strategies; Victor is the day trader.
• 🧰 Infrastructure squad — Tinker patches CC (Claude Code) after every extension upgrade; Prometheus open-sources the capabilities the whole team shares (global CLAUDE.md, skills, rules); Hermes handles networking; Anvil handles backend development; Atlas handles full-stack projects; Ada covers AI Agent algorithms and reasoning engines; Alfred manages device resources (local Mac / remote servers / cloud machines); Hopper guards every software project with a regression safety net — test cases written before development, CI red-light gate before merge.

Running an end-to-end digital-product business: research → produce → build → traffic → sell → analyze. 🔁 A growing roster of single-purpose AI Agents; six of them form this artifact-relay pipeline, turning one-time work into recurring passive income.

How the pipeline hands off — six AI Agents pass artifacts down the line:

1. 🧭 Scout sizes up trends, market, rivals and profit potential → an Opportunity Report (what to sell, to whom, at what price) → Wright.
2. 🛠️ Wright turns the report into a finished product — Prompt packs, templates, ebooks, assets → Mason.
3. 🏗️ Mason builds the storefront — independent site, landing pages, payment integration — and hands off ready-to-sell buy links → Buzz.
4. 📣 Buzz repackages it into channel-specific traffic content with buy links (X · IG · YouTube · RedNote · Zhihu · Bilibili, etc.) → Vendy.
5. 💰 Vendy lists, prices, fulfills and supports across storefronts, closing the sale → sales data → Echo.
6. 📊 Echo attributes results to decisions and folds lessons into a playbook → feeds back to whichever pipeline stage needs it · 🔁 closing the loop.

The interesting part is not the roster — it's the machinery between the agents:

• 📦 Artifact handoff. Work moves between agents as defined deliverables, not chat: Scout's Opportunity Report feeds Wright's product build, Mason's storefront (site, landing page, or payment setup) hands Buzz ready-to-sell links, Vendy's sales data lands in Echo's attribution engine. Each agent owns an output contract; the pipeline is the sum of those contracts.
• 🧰 Shared capability layer. One agent (Prometheus) stewards the capabilities every agent runs on — global skills, rules, and CLAUDE.md — from a single authoritative source, with an open-source mirror as the distribution channel. A fix lands once and ripples to all 20+ agents.
• 🧠 Reasoning as infrastructure. Specialized reasoning-engine rules (Infinite / Rapid / Incisive, by Ada) plus an evaluation system sit under every agent's thinking — reasoning depth is treated as shared infrastructure, not per-agent improvisation.
• 🐞 Quality gates with separation of powers. Development agents hold implementation rights, Hopper holds test-case definition rights, and CI holds the final say — developers can't bend test cases to fit their implementation, and "fix A, break B" gets stopped before merge, not after.
• ⚖️ Contracts & payments as a first-class function. Justin structures staged payments, due diligence and evidence chains for anything the org sells or signs — the org treats legal/payment design as an engineering discipline, not an afterthought.

By the numbers: 20+ specialized agents · 3 business squads · 5 direct reports · 6 pipeline stages · 200+ public repositories.

If my open-source work helps you, consider sponsoring — this keeps me motivated to keep creating more and better AI Agents and other Projects.