A Fleet workflow makes review the pipeline instead of the favor: drafts run through a brand-and-claims review against your actual product facts, then a named approver gates publication.
genflows:
- name: launch-post
steps:
- {name: draft, prompt: "Draft the announcement per the brief in the trigger ticket. Every product claim must be supported by the corpus.", corpus: ["marketing/brand-voice.md", "docs/product/**/*.md", "marketing/claims-allowed.md"], kind: report, out: post.md}
- {name: brand-claims, prompt: "Flag off-voice passages and any claim not supported by the product docs or the approved-claims list.", depends_on: [draft], kind: review, out: flags.md}
- {name: marketing-lead-ok, depends_on: [draft, brand-claims], kind: approval, out: decision.md}
- {name: publish, depends_on: [marketing-lead-ok, draft], kind: publish, out: published.md}
The approved-claims file is the quiet hero: a maintained list of what you're allowed to say about the product, applied by the review step on every draft. Claims drift gets caught at review, not at retraction.
