Content OS

News to Blog (E2E)

The most complete workflow in the product, and the only one that reaches an external system.

Vertical: Digital · Status: ✅ Live Back to Digital · workflows index


Trigger

A human queues a news item. Everything to ready is unattended.

Flow

queue news item
        |
generate draft            [Creative Agent] - brand prompt - SEO keywords - competitor brief
        |
quality repair            self-graded: structure - length - keyword placement
        |
SEO bolding               first-use <strong> on assigned keywords
        |
compliance pipeline       can regenerate with feedback
        |
ZeroGPT detect -> up to 2 humanization passes    (fails open)
        |
blocked-phrase scan -> content_warnings
        |
state: ready              <- STOPS HERE
        |
[human] compliance review -> acknowledge high-severity findings
        |
[human] Send to CMS       server-enforced 409 while gated

Where the judgement sits

Two rules the whole workflow is built around:

  1. Structural problems hard-block; quality problems save the draft with visible warnings. The agent never quietly decides something was good enough.
  2. Publishing is always human. The compliance gate does not decide - it only guarantees a person read the findings first.

Agents involved

Discovery Agent supplies the item - Creative Agent drafts - Compliance Agent reviews at both source and draft, and gates delivery.

Gaps

No vernacular versions (Localization Agent proposed), no images beyond a thumbnail, one angle per topic.

Roadmap source

Deliverable ② (page 5); page 6 blog tonality, imagery and guard rails; page 4 LFC — see roadmap_ref_extracted.md.

Source: roadmap/workflows/digital/news-to-blog/README.md