sethserver.com Subscribe
Colorful illustration of multiple microphone stands and musical instruments including trumpets arranged on a vibrant multi-colored background with orange, yellow, pink, blue and red panels, representing podcast recording studio or music performance setup

Orchestrating Specialized Systems Trumps AGI

By Seth Black • Updated: September 17, 2026

AI · 3 min read

Like this kind of writing? Get one email a week with notes on startups, AI, and the occasional strong opinion about Python: subscribe to the newsletter.

AGI - Artificial General Intelligence, or "strong AI" - has been the holy grail since Alan Turing kicked off the Turing Test over seventy years ago. Sounds amazing, right? One all-knowing system that beats humans at every cognitive task.

But there's a problem: even if we could build it, AGI might be the wrong target. The future looks less like one brain-in-a-jar and more like an orchestrated set of smaller, specialized systems-the "third future" I've been nudging people toward in this post on machine learning systems.

I've watched startups burn real money chasing "one model to rule them all" while perfectly usable, boring systems sat on the shelf because they weren't sexy enough for a pitch deck. Customers don't buy sexy. They buy "it works today."

The Myth of AGI: A Tempting but Flawed Idea

AGI is appealing because it's simple. Humans love simple. We also love pretending machines are people. So we picture a robotic assistant that can do taxes, therapy, and witty banter in the same breath - like a robotic Alfred... or, if I'm being honest, Bender. Who doesn't want their own personal Bender Bending Rodriguez?

AGI doesn't hold up under scrutiny:

  1. We don't understand human intelligence well enough.
    Neuroscience is impressive, but "impressive" isn't the same as "we can reproduce it."

  2. Human intelligence isn't singular.
    It's a messy interaction of specialized subsystems that change over time. If you've ever watched a smart, calm adult turn into a screaming toddler because they skipped lunch, you already understand the architecture.

  3. We overestimate what current AI is doing.
    Today's models can be brilliant at narrow tasks and still fail at basic generalization or "common sense." Common sense is a moving target that we can't even agree on.

  4. AGI amplifies ethical risk.
    Control, accountability, and unintended consequences get harder when the system is both powerful and general.

The Better Bet: Orchestration of Specialized AI

Instead of chasing a monolith, build a coordinated system of specialists:

Here's what orchestration looks like:

def solve(ticket):
    facts = retriever.search(ticket)
    intent = classifier.predict(ticket)
    draft = llm.generate(ticket, context=facts, style="support")

    if intent in {"high_risk", "legal", "refund_exception"}:
        return human_review(draft)

    return draft

A Real Example (Because Startups Love "Real" Right Up Until It's Inconvenient)

On a consulting gig, a company wanted "an AI support agent" that could answer anything, update accounts, issue refunds, and "sound human." Translation: they wanted AGI, but with a Zendesk integration.

What actually worked was orchestration:
- A classifier to detect intent and risk (refunds, legal threats, account access)
- Retrieval over their actual policy docs (not vibes)
- A small set of workflows for the top ticket types
- Human review gates for anything that could create financial or compliance damage

The result wasn't magical. It was better than magical. It reduced ticket time, cut repeat contacts, and stopped support from playing telephone between sales promises and reality. The CEO was mildly disappointed it didn't feel like science fiction. The customers were not.

Why This Wins in the Real World

AGI makes for good headlines. But orchestration is how you actually build products that work.

-Sethers

Share this post
Newsletter

One email, once a week.

Notes on databases, systems, and the occasional strong opinion about Python. No spam, unsubscribe anytime.

Seth Black
Written by

Seth Black

Engineer and founder based in Texas. Writes about databases, AI, and running things in production. Embeds in small teams as lead engineer.

More from AI

View all →
AI

How to be a Good Farrier: What the Car Teaches Us About AI and Your Job

Nov 10, 2026
AI

Principle of Least Privilege in the AI Age

Apr 14, 2026
AI

How to Actually Secure MCP (Model Context Protocol)

Apr 14, 2026