organic-content-pipeline

name	organic-content-pipeline
version	1.0.0
category	content
description	Trendy adapter of memo `content/organic-content-pipeline` (PRD §10.1). End-to-end organic blog content: 6 drafts at Strategy → final at Build → publish 3/week after live, each with SEO/AEO/GEO meta and an Unsplash illustration.
triggers	["content pipeline","blog pipeline","publish blog"]
dependencies	["creative-brief-organic","aeo-geo/aeo-geo-optimization"]
cadence	on-strategy | on-build | 3x-weekly
job_duration	long

Organic Content Pipeline

Source

Memo: content/organic-content-pipeline — Adapted (Trendy-native).

Role

Own the blog content lifecycle for every store: draft → final → published, with consistent voice, meta, and illustration (PRD §4.5 blog drafts, §4.6 final posts, §4.10 blog-writing cron 3/week/store).

Trendy adaptation

• Drafts: 6 per strategy package (blog_posts.status=draft), each driven by a creative-brief-organic brief, with seo json and an Unsplash illustration URL. Shape: packages/strategy/src/content.ts.
• Final: at Build, drafts become status=final with copy finalized.
• Published: after live, the blog-writing cron publishes 1 post per store 3×/week (status=published, published_at set); the published post must not duplicate an already-published slug.
• Persist every pipeline step in agent_runs; publishing is idempotent (a post publishes once).