This is a work in progress, shared at the design level. The Foundry provides the user interface and configuration parameters of our content-creation capabilities — the place where a working capability stops being wiring and starts being something you can configure, direct, and hand to a team.

Why it exists

Our first set of content-creation tools worked — but they were so intertwined with our AI harness that extracting them, or instantiating new versions for a new publication, was genuinely difficult. Every new show meant surgery on the machine that ran the last one. The Foundry is the answer: separate the configuration of a content operation — its topics, calendar, voice, sources, standards — from the machinery that executes it, so new instances stamp out instead of getting hand-forged.

Where it is today

The first beta is out now (September 2026): the marketing team at QuickLaunch uses the Foundry to manage the topics and dates that drive production of the QuickLaunch blog. A team that isn't us, steering an AI content operation through configuration instead of code — that's the whole thesis, at version one.

The same underlying capabilities already run in production on our own properties:

  • quicklaunch.io/blog — the weekly professional column, produced on schedule, now Foundry-managed.
  • The DBNR Weekly — the Sunday broadcast, produced end-to-end with no humans in the loop.
  • Signal & Noise — the Wednesday investigation, fine print first.

Where it's going

As we migrate each content-creation project onto the Foundry architecture, the design converges on something bigger than a dashboard: one of the Agent employees we describe in our operations research. Create a staff member with a point of view and a thirst for knowledge within a specific domain — and put it to work. It becomes more of an expert as each day passes: self-learning, self-editing, iteratively improving its performance with experience. The Foundry is where you'd hire one, configure one, and read its work.

A design principle worth stating even at this altitude: the Foundry is the durable control plane. The runners that execute the work are interchangeable infrastructure — they can change underneath without the operation noticing. Configuration outlives machinery.

What we're not sharing yet

Deeper architecture, the console itself, and the roadmap stay internal while the beta hardens. This page will grow as the product does — that's the memo format working as intended.

Beta · Live Design shared at high level