Meet Our Team: The AI Agents Running Traffic Empire
Most companies have an "About Our Team" page with headshots and LinkedIn links. We have something different: eight AI agents with defined roles, measurable outputs, and the ability to rewrite each other's instructions when performance drops. Here is who they are and how they work.
The Org Chart You Have Never Seen Before
Traditional companies organize around humans with titles. Our company organizes around agents with instruction files. Every agent has a CLAUDE.md — a detailed document that specifies its role, its inputs, its outputs, its success criteria, and its constraints.
These instruction files are not suggestions. They are the agent's operating system. When the CEO agent starts a cycle, it reads its own CLAUDE.md line by line and executes each step. When the Builder agent receives a design spec, it follows its CLAUDE.md to scaffold, code, deploy, and verify.
The instruction files are also mutable — and this is where it gets interesting. The Auditor agent can rewrite any other agent's instructions if that agent is consistently underperforming. The system literally rewires itself.
The CEO: Strategic Orchestration
The CEO does not write code, design brands, or produce content. It decides. Every cycle starts with the CEO loading context: the registry (current state of all sites), the git log (what changed since last cycle), the analytics report (which sites are healthy, which are struggling), and the auditor's last report (what went wrong, what needs improvement).
Based on this data, the CEO makes three types of decisions:
- Build — commission a new site from a Research-approved niche
- Improve — allocate agents to fix or enhance an existing site
- Deprecate — shut down a site that is not performing and redirect its subdomain
The CEO also enforces the ratchet: if the portfolio score dropped since last cycle, no new builds. The system must fix what is broken before expanding.
The Auditor: The Immune System
The Auditor is arguably the most important agent in the system, and it is deliberately the last to run in every cycle. Its job is quality control at the system level.
After all other agents have completed their work, the Auditor reviews everything:
- Did the Builder's sites actually deploy? Are they returning 200 status codes?
- Did the Content agent's articles meet quality standards?
- Did the SEO agent configure all GEO endpoints correctly?
- Did the Research agent's niche scores align with actual performance?
Each agent receives a grade: A (excellent), B (good), C (needs improvement), D (failing). For agents graded C or D:
- First occurrence: the Auditor proposes instruction changes in its report
- 3+ consecutive weeks of the same failure: the Auditor directly edits the agent's
CLAUDE.md - If the instruction change improves metrics next cycle, it stays. If not, the Auditor reverts it.
The critical design choice: the Auditor reviews itself too. If its own recommendations led to worse outcomes, it adjusts its own evaluation criteria. This recursive self-improvement is what makes the system anti-fragile rather than merely robust.
The Specialists
The Research agent does not just find opportunities — it tracks how accurate its predictions were. If it scored a niche at 85 but the resulting site underperformed, it adjusts its scoring model. Over time, the Research agent gets better at predicting which niches will actually generate traffic. It also maintains a knowledge/rejected/ directory of niches it investigated and rejected, with reasons — preventing the system from re-researching the same dead ends.
Every site in our portfolio has a unique visual identity. CalcFit uses clinical blues and greens that signal health and precision. PayScale Pro uses navy and emerald that signal trust and financial expertise. Pixelry uses creative magentas that signal artistic tools. The Designer produces a complete brand JSON spec that the Builder consumes — ensuring the design intent is perfectly preserved in code.
The Builder is our most prolific agent. It takes a design spec and produces a complete, production-ready Next.js site. Every calculator implements validated formulas. Every tool processes data correctly. Every page is server-rendered for SEO. The Builder verifies its own work with curl checks after deployment — if a site returns anything other than a 200 status, the deploy is flagged as failed.
The Virtual Newsroom
This is perhaps the most unusual part of our operation. The Content agent manages a virtual newsroom with five named writer personas. Each persona has a distinct editorial voice, subject matter expertise, and writing style.
Why personas instead of a single generic voice? Because tone matters. A fitness article about BMI limitations needs a different voice than a finance article about tax bracket optimization. A trend explainer about viral memes needs different energy than a technical analysis of VPN encryption protocols.
Our five writers:
These are not fake people. We are not pretending they are human. They are personas — consistent editorial voices that produce better content than a single generic voice could. Each persona's byline appears on articles they "write," and readers can expect a consistent tone and expertise level from each one.
The Operations Backbone
Analytics runs first in every cycle for a reason: every other agent's decisions depend on having current data. The Analytics agent computes a health score for every live site — a composite metric based on uptime, page performance, traffic trends, and engagement signals. When a site's health score drops, the Analytics agent diagnoses why: Is it a build failure? A slow page? Declining search rankings? Missing structured data?
The SEO/GEO agent has a unique dual mandate. Traditional SEO (meta tags, structured data, sitemaps, internal linking) is table stakes. But we also optimize for GEO — Generative Engine Optimization. Every site exposes /llms.txt endpoints that AI assistants can read. This is a bet on the future: as more users discover tools through ChatGPT, Claude, and other AI assistants, being structured and readable by these systems becomes a competitive advantage.
How They Work Together
The agents do not work in isolation. They read each other's outputs. The CEO reads the Analytics report and the Auditor's recommendations before making decisions. The Builder reads the Designer's brand spec. The Content agent reads the SEO agent's keyword recommendations. The Auditor reads everyone's status files.
This is coordination through shared state rather than real-time communication. The registry (registry.json) and the git history serve as the shared memory layer. Every agent writes a status file after completing its work: registry/status-{agent}-{date}.json. These status files form the ratchet's data layer — they are how the system tracks what changed, what improved, and what regressed.
It is a fundamentally different model from how human teams work. There are no meetings, no Slack channels, no status updates. Just structured data flowing between specialized functions, with the Auditor as the quality gate and the CEO as the decision function.
Want to see the system in action? Read about how we built 23 websites in 48 hours, or learn why we chose to tell you all of this.