System 02 · Editorial

Content OS

Idea to published, on a schedule, with the quality gate in the middle. Nothing reaches your CMS that has not cleared word count, readability and keyword placement.

PipelineIntent → brief → draft → QA → publish
Throughput4–100 articles a month
CMS targetsWordPress, Shopify, Webflow, Wix
Quality gateBlocking, not advisory
Architecture

Three layers, so the guessing stays in one of them.

Directive

What to do

The SOP, written down. Goals, inputs, the tools to use, the outputs and the edge cases — in plain language, versioned like code. When we learn an API limit the hard way it gets written here, so it is never learned twice.

Orchestration

Decision-making

The only probabilistic layer. It reads the directive, calls the tools in order, handles the errors and asks when something is genuinely ambiguous. It does not do the work itself.

Execution

Doing the work

Deterministic scripts. Same input, same output, every run. Ninety per cent accuracy per step is fifty-nine per cent over five, so anything that must be right lives down here instead.

Data flow

In, through, out.

Sources
Keyword universe and gap analysis
Live search-results research per brief
Your existing best-performing pages
Brand voice, locked at onboarding
Process
  1. Classify intent and buyer stage
  2. Build the brief from SERP research
  3. Draft, then a separate refinement pass
  4. Compliance and quality gate
  5. Publish with schema, meta and hero image
  6. Adapt for social from the same brief
Artifacts
Published article, live on your CMS
Meta title, description and JSON-LD
Hero and inline imagery
Social variants per platform
Pipeline record with its full history

The refinement pass is separate from the draft on purpose. A single generation pass produces competent, generic prose; the second pass is where the specifics and the argument arrive — and where anything generic gets rejected before you ever see it.

Integrations

It reads your stack. It doesn't replace it.

WordPressShopifyWebflowAirtableSearch ConsoleAnalytics 4Google DriveSlackClickUpLinkedInInstagramX

Read-only wherever read-only is enough. Nothing gets write access it doesn't need, and every write is logged.

Quality gates

A run either passes, or it doesn't ship.

Word count within spec and readability inside the target band.

Primary keyword present in the H1 and the title, without stuffing.

Author attribution is a real, named human — never a fictional byline.

If a gate fails, the pipeline halts and files the error. It does not retry blindly, and it does not hand you a report built on half a run.

Datasheet

The boring details.

SpecStandardDeployable
Where it runsOur infrastructureYours
Who holds the API keysUs, scoped per clientYou
CadenceMonthly, or weeklyAny schedule
Raw data retentionRebuilt each runYour policy
Artifact deliveryYour Drive and trackerYour choice
Source code accessFull
Runs unattendedYesYes
Failure alertingSlack and emailYour channels
The other systems

Same architecture, different job.

Want it in your own stack?

Deployable hands over the software, the hosting and the keys. You run it; we stay on for support.

Talk scope