content

A publishing pipeline that never fakes a green.

Briefs become drafts, drafts face reviews in parallel, and only a double green ships. Put it on a schedule and the pipeline fires itself every morning, recalls what yesterday taught it, and files a bug instead of publishing a red.

what monday looks like

  1. 01Install the Content Studio pack: blog post, social post, newsletter, repurpose
  2. 02Run one article attended: brief, research, draft, two reviews in parallel
  3. 03Watch the fix loop send findings back to the draft until both reviews pass
  4. 04Then add the schedule, and stop starting it yourself

The daily loop, as it runs in production

  1. Fires itself

    An RRULE schedule creates the day’s task. Nobody starts it.

  2. Recalls before acting

    Queries memory first: yesterday’s context, learned rules.

  3. Researches and drafts

    Agents source, check and write, one governed step at a time.

  4. Hard verification gate

    Claims cited, entities verified. A red files a bug task. The loop never fakes green.

  5. Publishes

    Content ships with its provenance attached.

  6. Sweeps and closes the loop

    Verifies its own output landed. Tomorrow it all runs again.

install these

questions

Is this actually autonomous, or a fancy scheduler?

The schedule only starts it. The loop then recalls what past runs learned, drafts, faces its reviews, and stops at the gates you placed. Selection, memory, verification, and governance are what make it a system rather than a timer.

What stops it from publishing something bad?

The verification gate. Reviews run in parallel and findings loop the draft back until it passes; on a hard red the workflow files a bug task instead of shipping. A loop that cannot fake green is the entire point.

Where does it keep our style and standards?

Two places, deliberately: policies deliver rules like "every claim carries a source" into the active step, and memories carry the accumulated rulings, so run 40 writes with everything run 1 had to be told.

Can a human stay in the loop?

Wherever you want one. Keep the approval gate before publish and the pipeline drafts autonomously but ships only when you release it; remove it and the double-green reviews are the bar.