SOLUTION · N · 002

An AI content engine that keeps up without falling apart.

This is a set of specialized AI agents that plan, write, review, and publish marketing content together. One agent plans the work, a few others actually write and design it, and one exists purely to catch mistakes before anything goes out. All of it runs against real performance data, so the whole system keeps getting better instead of repeating itself.
STATUS
IN PRODUCTION
PIPELINE
6 specialists, 1 planner
OUTPUT
Fresh content, every week
CHANNELS
Meta · X · LinkedIn
What MERIDIAN actually does.
MERIDIAN is built from four pieces, all coordinated by a planner agent. The shape changes depending on the project, the foundation underneath does not.
// 01

Planner-led orchestration

A planner agent owns the entire production process. It decides which specialists run, in what order, and what actually gets shipped, and every one of those decisions is visible and logged.

  • One planner, six specialists
  • Every decision has a clear source
  • Replans automatically if something fails
// 02

Critic that rejects

The critic agent reviews everything against your actual brand voice, tone, and the brief itself. Any disagreement gets surfaced, every rejection is logged, and a human always keeps the final veto.

  • Enforces your actual brand voice
  • Checks tone on every piece
  • Every rejection gets logged
// 03

Bounded tool use

Every specialist only touches the real world through a specific tool, whether that is generating something, rendering it, scheduling it, or publishing it. Each tool has clear limits, and every call it makes is traceable.

  • A defined tool for every action
  • Safe to run more than once
  • Checked before anything ships
// 04

Analytics feedback into the brief

Performance data feeds back into the brief itself, not into the model. That means the system learns what is actually working at a level a human can read, understand, and override.

  • Tracked by channel
  • Feeds back into the brief, not the model
  • Summaries a person can actually read
How MERIDIAN lands in a team.
Four phases from first read to operator handoff. Each produces an artifact your marketing team can read on its own.
01
AUDIT

Read the existing content workflow.

We sit with your actual marketing team and follow both the assets that ship and the ones that quietly never do. Most of how MERIDIAN ends up shaped comes directly out of this.

Workflow map and asset taxonomy
02
DESIGN

Plan the agent graph.

Six specialists with named roles, covering ingest, brief, write, render, critique, and publish, plus a planner that owns the whole production graph. All of it written down before any of it gets built.

Agent contracts and tool schemas
03
BUILD

Engineer the pipeline.

A cloud native backend, video generation pipelines, real Meta API integrations, and attribution feedback built in. Observability from day one, not bolted on later.

A live, working pipeline
04
OPERATE

Hand the keys.

A marketing operator owns the loop. They can read every brief, override any output, retighten the critic, and roll back any asset.

Operator console and an ongoing retainer
What MERIDIAN is built on.
Choices that survived production. We choose for legibility, so your team can read the agent graph in three years.
CORE
Python · TS
Async-first pipeline
MODELS
GPT-4o · Claude · open
Multi-model by default
ORCHESTRATION
Custom · LangGraph
State-machine agent graph
RENDERING
Video · image · copy
Per-format pipelines
CHANNELS
Meta · X · LinkedIn
Native API integrations
OBSERVABILITY
OTel · custom traces
Every decision replayable
Questions we get asked.
Six that come up most often about MERIDIAN.

No. MERIDIAN replaces the production work, the actual mechanical labor of turning a brief into a set of assets shaped for each channel. The interesting work, the strategy, the brief writing, the judgment on what is even worth saying, stays completely human.

Teams we have built this for end up spending more time on strategy after it launches, not less. The system just gives them their attention back.

The critic agent enforces it. We start by actually writing your brand voice rules down in a form the system can check against, and the critic rejects anything that drifts from it. Drift is the most common way this kind of system fails, and the critic exists specifically to catch it.

If your brand voice genuinely cannot be written down in any consistent way, that is a different problem, and we will tell you honestly if that is what we are seeing.

Performance data gets summarized regularly and proposed to the human operator as changes to the brief, never as some silent retraining happening behind the scenes. The operator approves or edits the proposal, the brief gets updated, and the pipeline starts producing against the new version. The model never quietly changes its mind about your brand on its own.

The Meta family of apps, X, LinkedIn, and a generic webhook for whatever else your stack uses, plus email and CRM integration through API. Adding a new channel is mostly a matter of building the specialist for it, the planner picks it up automatically once that exists.

It varies a lot by engagement, and honestly we do not optimize for a number here. Quality through the critic is the actual goal, throughput is just whatever that quality allows.

Tell us what you are dealing with. We read through your existing workflow, get back to you within 48 hours with an honest architecture sketch, and go from there together.

MERIDIAN, built for your actual content workflow.

Tell us what you are dealing with. We respond within 48 hours with an honest read and an architecture sketch.