Capability 06 · Prepare materials
Campaign Studio
Connect exact approved-claims and brand-kit inputs to claim-linked copy, rendered-file validation, and a content-addressed draft review package.
The problem¶
Campaign review slows when claims, safety context, channel copy, brand components, validation evidence, and rendered files live in separate places. A technically valid copy object can still produce a clipped or stale final asset, and an informal handoff can lose the exact inputs and file hashes that reviewers need.
Objective¶
Create a structured campaign brief, fail-closed input record, claim-linked message and channel drafts, policy and rendered-file evidence, and a deterministic package that qualified medical, legal, and regulatory reviewers can assess.
How it helps¶
- Preflights the exact approved-claims JSON and brand-kit paths; missing, malformed, excluded, or inconsistent inputs stop the workflow instead of falling back to demo data.
- Reports the current workflow status and next required step, then enforces applicable claim IDs and exact approved text or allowed variants for each channel.
- Validates the actual rendered files, seals their hashes, and exports a manifest plus content-addressed ZIP for review.
How the plugin works¶
Exact governed inputs
A campaign brief, approved-claims JSON path, brand-kit directory, jurisdiction, audience, CTA, and requested channels.
Draft, validate, render, and package
create_campaign_briefretrieve_approved_claimsretrieve_brand_componentsget_campaign_statuspreflight_campaign_inputsgenerate_audience_journeygenerate_message_architecturegenerate_channel_copyvalidate_claims_and_fair_balancerender_emailrender_bannerrender_postervalidate_rendered_assetspackage_mlr_submissionrender_mlr_reviewexport_mlr_package
Traceable draft MLR handoff
Validated copy and rendered assets, canonical Markdown and interactive HTML review, manifest, hashes, and a content-addressed ZIP.
A three-step workflow¶
Bind the exact inputs
Set the governed brief and validate the approved-claims JSON and brand-kit directory before drafting.
Draft with traceability
Create the journey, message architecture, and English email, banner, or poster copy with claim IDs and fair balance.
Validate, render, export
Check every channel and rendered file, render the canonical review, and export the sealed draft package.
Sample input¶
The fictional JSON combines a compact US/FDA campaign brief with one simulated efficacy claim and one simulated safety statement. It is explicitly demonstration content and must never be adapted as real product messaging.
Interpreted sample output¶
The representative email excerpt links each non-CTA block to a fictional claim ID and includes both efficacy and safety
content. Its software policy check passes, while the claim status remains needs_review and the package remains a draft
for qualified MLR review. A passing validator is not evidence that the content or rendered asset is approved.
Download representative output JSON
Business value indicators¶
| Indicator | What a business reviewer learns |
|---|---|
| Copy blocks with claim IDs | Whether promotional statements retain an approved-claim reference |
| Claim and policy check results | Which wording, fair-balance, or required-element issues remain |
| Input paths, fingerprints, and workflow status | Whether the run uses the intended sources and which step is required next |
| Rendered-file checks and hashes | Whether email, banner, or poster output is complete, current, visible, and unchanged |
| Package manifest and digest | Whether reviewers received the exact content-addressed handoff that the workflow exported |
Boundaries and human review¶
The package is a review aid, not regulatory approval. Version 1.1 produces English email, banner, and poster drafts; it does not extract approved claims from PDF or other formats. A qualified medical, legal, and regulatory reviewer must assess claims, fair balance, jurisdictional elements, source currency, and final visual fidelity before use. Revalidate after any brief, claim, brand, policy, template, copy, or rendered-output change. The tools do not send email, traffic ads, publish assets, or record an authoritative external decision.
Get started¶
Inspect the fictional claim-to-copy mapping, then use the canonical pinned guide for exact input preflight, status-led resume, renderer validation, and the content-addressed review export.