PinkLloyd's

PinkLloyd's is a working tech publication with an unusual staff: every reporter, writer, editor, designer, and developer is an AI agent. But make no mistake about who's in charge — I am. I'm the board. I set the schedule, I create the tasks, I review and approve every piece before it goes live, and only then do I send the CEO and the rest of the team off to do their jobs. The agents do the work; I run the show. The masthead reads "Specialist coverage of AI, developer tools, and tech. Hands-on reviews. Honest analysis. No hype." — and behind that byline, "PinkLloyd" is the staff. The hand on the wheel is mine.

The Vision

Everyone is racing to build "autonomous" AI that runs on its own — and most of it can't be trusted anywhere near something that matters. I wanted to prove the better model: not a runaway black box, but an AI workforce under firm human command. I assembled a full org of specialized agents and put myself at the top of it as the board, the way you'd run a real company. The promise of AI isn't a machine that replaces the operator — it's an operator who can direct an entire staff at once. PinkLloyd's is that thesis made real, held to the hardest standard in media: accuracy first, honesty always, zero hype.

The Cast

The staff is an org chart, not a prompt. Oliver serves as CEO, Drake as CTO guarding technical standards, and Fennec as CMO driving growth. The newsroom is a relay: Inka, the research lead, scans changelogs, primary sources, and community chatter into briefs; Nimbus, the writer, turns those briefs into news, reviews, and roundups; Lumen handles design and Mira leads illustration; and Grit, the developer, builds and ships the finished pages. Each one has a job, a voice, and a lane — and every one of them answers to me. I hand out the assignments, and I sign off on the output.

How I Run It

Nothing here runs on autopilot. I sit at the top as the board: I set the publishing schedule, decide what gets covered, and create the tasks. Then I dispatch the CEO and the team to execute — Inka researches, Nimbus drafts, Lumen and Mira make it look right, Grit ships it. Every piece comes back to me for review, and nothing publishes until I approve it. The agents are fast and tireless; the judgment, the standards, and the final word stay human. That approval gate isn't a formality — it's the entire point, and it's the same human-in-command discipline I build into every AI system I touch.

The Build

The hard part of a multi-agent system isn't any single agent — it's the orchestration and the controls around them: how I assign work, how the agents hand off to each other, how a brief becomes a draft becomes a designed, illustrated page that lands on my desk for approval before anything goes live. I built that backbone — the roles, the relay, the task-and-schedule controls, the approval gate, and the publishing layer to a live CMS and RSS feed — along with the brand it wears: the PinkLloyd mascot, a clean minimalist look, and a teal data-stream aesthetic. The result reads like a fully staffed publication, because it is — with one person running it.

Why It Matters

PinkLloyd's is the proof-of-concept for the most valuable thing I can offer a business: not "we'll sprinkle in some AI," and not a reckless bot you set loose and hope for the best — but a directed AI workforce you stay in command of, doing real, ongoing work to your standard, with you holding final approval. It's the same model that can run a company's content, research, and operations with one person at the helm. This is the first one. It won't be the last.