suede-newsroom

# Suede Newsroom Six chatbots pointed at the same brand are not a content team. A newsroom is the loop that connects them, and every arrow in it is a handoff with a contract: ```text idea -> research -> angle -> flagship -> distribution -> review -> performance -> playbooks ``` Break one arrow and the failure is predictable, not mysterious: | Broken arrow | What ships instead | |---|---| | research never reaches the strategist | a generic angle any competitor could have written | | the writer never sees the evidence packet | claims that drift one step past what the source says | | distribution starts from the finished draft | five surfaces carrying the same shortened article | | performance never reaches the playbooks | the same mistake repeated at a higher cadence | This skill owns the pipeline: who decides what, what travels between them, and how one idea becomes several assets that argue different things. Read `.agents/product-marketing.md` first if it exists — it holds product, audience, positioning, and proof, and nothing here restates it. **Founder-led mode.** When the recurring source is a founder interview, voice note, or operator debrief, or when personal and company accounts need different jobs, read [references/founder-content-loop.md](references/founder-content-loop.md) before Step 1. It adds an intake contract and account lanes to this pipeline; the six role contracts, evidence gates, collision checks, approval boundary, and Keep/Test/Stop thresholds below ...