zarnite/zarn-creative-brief-to-asset-plan · Datasets at Hugging Face

zarn_creative_brief_to_asset_plan_train_0000

train

easy

Zarn

creative_brief

apache-2.0

zarnite-team-reviewed-gold-track-starter

0.88

{ "brand": "First Mile Creative", "theme": "event promo", "project_background": "First Mile Creative needs support for event promo and wants work that feels premium and restrained without losing practical clarity.", "business_goal": "package one clearer offer", "audience": "brand managers", "channels": [ ...

{ "vertical": "media tools", "tone": "premium and restrained", "must_keep": [ "clear value proposition", "one proof point", "one concise CTA" ], "must_avoid": [ "empty lifestyle language", "unsupported performance claims", "bloated launch scope" ] }

{ "primary": "brand managers", "attention_constraint": "executive skim behavior", "trust_builder": "Concrete proof beats generic ambition." }

[ { "asset": "founder notes", "quality": "messy but detailed", "best_use": "angle extraction" }, { "asset": "customer quote", "quality": "short but believable", "best_use": "proof or trust beat" }, { "asset": "product screenshots", "quality": "clean", "best_use": "visual su...

[ "Do not promise unsupported outcomes.", "Keep the first deliverable light enough to review in one pass.", "Flag anything that needs approval instead of smoothing over it.", "Keep the final plan consistent across all proposed deliverables." ]

{ "deliverables": [ { "priority": 1, "asset": "hero asset", "channel": "Instagram Reels", "reason": "Unlocks feedback quickly while carrying the main promise." }, { "priority": 2, "asset": "proof asset", "channel": "YouTube Shorts", "reason": "Turns the clai...

[ { "stage": "concept sign-off", "owner": "strategy lead", "purpose": "Lock the angle before production expands." }, { "stage": "draft review", "owner": "creative lead", "purpose": "Check whether the proof and hierarchy are still intact." }, { "stage": "stakeholder review", "ow...

[ "The plan can drift if the proof source is older than the current offer or campaign context.", "Too many channels too early may recreate the same review burden the package is meant to reduce.", "If approval-sensitive language is embedded in the hero asset, revisions will become slower and more expensive." ]

{ "primary_metric": "coverage_and_constraint_score", "secondary_metrics": [ "deliverable_fit", "qa_readiness", "dependency_clarity", "message_hierarchy_quality", "handoff_readiness" ], "automatic_failures": [ "Misses the stated proof requirement", "Ignores approval-sensitive constrai...

{ "why_now": "Stakeholder patience is thinning, so the first pass has to feel focused and useful.", "commercial_goal": "package one clearer offer", "core_tension": "The team needs enough structure to ship, but not so much scope that the review cycle expands again.", "proof_strategy": "Use one central proof line...

[ { "level": 1, "message": "Lead with the operational promise, not the process description.", "why": "This gives the audience a reason to care immediately." }, { "level": 2, "message": "A smaller first pass made review faster and clearer for the whole team.", "why": "The proof line is the ...

[ { "segment": "brand managers", "need": "Fast signal that the asset will be useful before it becomes another thing to review.", "trigger": "concrete proof plus low-hype tone" }, { "segment": "secondary internal stakeholder", "need": "Confidence that the package is reviewable and aligned to th...

[ { "channel": "Instagram Reels", "job": "carry the main promise", "format_note": "This is the hero surface that sets the tone for the rest of the package." }, { "channel": "YouTube Shorts", "job": "surface the proof", "format_note": "Make the evidence impossible to miss without bloating t...

[ { "stage": "brief approval", "owner": "strategy lead", "standard": "The angle and proof are locked before production expands." }, { "stage": "asset review", "owner": "creative lead", "standard": "The hero asset, proof asset, and CTA asset remain aligned." }, { "stage": "stakehold...

{ "hero_angle": "The best asset plan treats the first release as a scoped proof package, not as the whole campaign.", "asset_matrix": [ { "asset_type": "hero asset", "primary_job": "make the promise obvious", "must_keep": "tone plus proof line" }, { "asset_type": "proof asset", ...

[ "The output names what ships first, why it ships first, and what should wait.", "Message hierarchy and asset plan stay consistent across channels.", "Approval ownership is visible enough that the work can move without a second planning pass." ]

{ "modality": "brief-plus-asset-context", "brief_surfaces": [ "creative_brief", "brand_context", "audience_profile", "available_assets" ], "review_stages": [ "concept sign-off", "draft review", "stakeholder review", "final QA" ], "risk_pressure": [ "The plan can drift if ...

[ { "label": "hero-first package", "rationale": "Acceptable when the plan leads with the hero asset and compresses the downstream support assets into fewer deliverables.", "outputs": { "asset_priority": "hero asset first", "channel_bias": "highest-attention channel gets the clearest proof asse...

[ { "label": "brainstorm masquerading as plan", "why_bad": "Produces ideas without naming what ships first or who approves it.", "conflicting_rule": "The first asset should be clearly prioritized and justified." }, { "label": "message drift", "why_bad": "Changes the core promise as assets move...

Easy rows for creative brief translation into asset system planning still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct.

[ "high-context", "constraint-dense", "difficulty-easy", "message-hierarchy", "asset-prioritization", "approval-path", "channel-fit", "dependency-handoff" ]

[ "competing-stakeholder-priorities", "channel-specific-constraint-carryover", "message-order-drift", "unclear-first-asset" ]

[ "Produces a brainstorm instead of a production-ready asset plan.", "Lets the message hierarchy drift between channels.", "Hides approval ownership or dependencies that would block execution." ]

{ "status": "starter-train-ready", "gold_candidate": false, "recommended_reviewers": 1, "adjudication_mode": "single-review-spot-check", "required_checks": [ "The first asset is clearly prioritized and commercially justified.", "Message hierarchy stays stable across the asset family.", "Approval s...

zarn_creative_brief_to_asset_plan_train_0001

train

medium

Zarn

creative_brief

apache-2.0

zarnite-team-reviewed-gold-track-starter

0.91

{ "brand": "Signal Oak", "theme": "new feature push", "project_background": "Signal Oak needs support for new feature push and wants work that feels clear and practical without losing practical clarity.", "business_goal": "improve review speed", "audience": "marketing leads", "channels": [ "Email", ...

{ "vertical": "productivity", "tone": "clear and practical", "must_keep": [ "clear value proposition", "one proof point", "one concise CTA" ], "must_avoid": [ "empty lifestyle language", "unsupported performance claims", "bloated launch scope" ] }

{ "primary": "marketing leads", "attention_constraint": "fast mobile consumption", "trust_builder": "Concrete proof beats generic ambition." }

[ { "asset": "founder notes", "quality": "messy but detailed", "best_use": "angle extraction" }, { "asset": "customer quote", "quality": "short but believable", "best_use": "proof or trust beat" }, { "asset": "product screenshots", "quality": "clean", "best_use": "visual su...

[ "Do not promise unsupported outcomes.", "Keep the first deliverable light enough to review in one pass.", "Flag anything that needs approval instead of smoothing over it.", "Keep the final plan consistent across all proposed deliverables." ]

{ "deliverables": [ { "priority": 1, "asset": "hero asset", "channel": "Email", "reason": "Unlocks feedback quickly while carrying the main promise." }, { "priority": 2, "asset": "proof asset", "channel": "Webinar follow-up", "reason": "Turns the claim into ...

[ { "stage": "concept sign-off", "owner": "strategy lead", "purpose": "Lock the angle before production expands." }, { "stage": "draft review", "owner": "creative lead", "purpose": "Check whether the proof and hierarchy are still intact." }, { "stage": "stakeholder review", "ow...

[ "The plan can drift if the proof source is older than the current offer or campaign context.", "Too many channels too early may recreate the same review burden the package is meant to reduce.", "If approval-sensitive language is embedded in the hero asset, revisions will become slower and more expensive." ]

{ "primary_metric": "coverage_and_constraint_score", "secondary_metrics": [ "deliverable_fit", "qa_readiness", "dependency_clarity", "message_hierarchy_quality", "handoff_readiness" ], "automatic_failures": [ "Misses the stated proof requirement", "Ignores approval-sensitive constrai...

{ "why_now": "The team has enough material, but not enough clarity on what to ship first.", "commercial_goal": "improve review speed", "core_tension": "The team needs enough structure to ship, but not so much scope that the review cycle expands again.", "proof_strategy": "Use one central proof line across the a...

[ { "level": 1, "message": "Lead with the operational promise, not the process description.", "why": "This gives the audience a reason to care immediately." }, { "level": 2, "message": "A smaller first pass made review faster and clearer for the whole team.", "why": "The proof line is the ...

[ { "segment": "marketing leads", "need": "Fast signal that the asset will be useful before it becomes another thing to review.", "trigger": "concrete proof plus low-hype tone" }, { "segment": "secondary internal stakeholder", "need": "Confidence that the package is reviewable and aligned to t...

[ { "channel": "Email", "job": "carry the main promise", "format_note": "This is the hero surface that sets the tone for the rest of the package." }, { "channel": "Webinar follow-up", "job": "surface the proof", "format_note": "Make the evidence impossible to miss without bloating the asse...

[ { "stage": "brief approval", "owner": "strategy lead", "standard": "The angle and proof are locked before production expands." }, { "stage": "asset review", "owner": "creative lead", "standard": "The hero asset, proof asset, and CTA asset remain aligned." }, { "stage": "stakehold...

{ "hero_angle": "The best asset plan treats the first release as a scoped proof package, not as the whole campaign.", "asset_matrix": [ { "asset_type": "hero asset", "primary_job": "make the promise obvious", "must_keep": "tone plus proof line" }, { "asset_type": "proof asset", ...

[ "The output names what ships first, why it ships first, and what should wait.", "Message hierarchy and asset plan stay consistent across channels.", "Approval ownership is visible enough that the work can move without a second planning pass." ]

{ "modality": "brief-plus-asset-context", "brief_surfaces": [ "creative_brief", "brand_context", "audience_profile", "available_assets" ], "review_stages": [ "concept sign-off", "draft review", "stakeholder review", "final QA" ], "risk_pressure": [ "The plan can drift if ...

[ { "label": "hero-first package", "rationale": "Acceptable when the plan leads with the hero asset and compresses the downstream support assets into fewer deliverables.", "outputs": { "asset_priority": "hero asset first", "channel_bias": "highest-attention channel gets the clearest proof asse...

[ { "label": "brainstorm masquerading as plan", "why_bad": "Produces ideas without naming what ships first or who approves it.", "conflicting_rule": "The first asset should be clearly prioritized and justified." }, { "label": "message drift", "why_bad": "Changes the core promise as assets move...

Medium rows for creative brief translation into asset system planning mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible.

[ "high-context", "constraint-dense", "difficulty-medium", "message-hierarchy", "asset-prioritization", "approval-path", "channel-fit", "dependency-handoff" ]

[ "competing-stakeholder-priorities", "channel-specific-constraint-carryover", "message-order-drift", "unclear-first-asset" ]

[ "Produces a brainstorm instead of a production-ready asset plan.", "Lets the message hierarchy drift between channels.", "Hides approval ownership or dependencies that would block execution." ]

{ "status": "starter-train-ready", "gold_candidate": false, "recommended_reviewers": 1, "adjudication_mode": "single-review-spot-check", "required_checks": [ "The first asset is clearly prioritized and commercially justified.", "Message hierarchy stays stable across the asset family.", "Approval s...

zarn_creative_brief_to_asset_plan_train_0002

train

hard

Zarn

creative_brief

apache-2.0

zarnite-team-reviewed-gold-track-starter

0.85

{ "brand": "Harborline Works", "theme": "seasonal launch", "project_background": "Harborline Works needs support for seasonal launch and wants work that feels clear and practical without losing practical clarity.", "business_goal": "package one clearer offer", "audience": "brand managers", "channels": [ ...

{ "vertical": "beauty", "tone": "clear and practical", "must_keep": [ "clear value proposition", "one proof point", "one concise CTA" ], "must_avoid": [ "empty lifestyle language", "unsupported performance claims", "bloated launch scope" ] }

{ "primary": "brand managers", "attention_constraint": "executive skim behavior", "trust_builder": "Concrete proof beats generic ambition." }

[ { "asset": "founder notes", "quality": "messy but detailed", "best_use": "angle extraction" }, { "asset": "customer quote", "quality": "short but believable", "best_use": "proof or trust beat" }, { "asset": "product screenshots", "quality": "clean", "best_use": "visual su...

[ "Do not promise unsupported outcomes.", "Keep the first deliverable light enough to review in one pass.", "Flag anything that needs approval instead of smoothing over it.", "Keep the final plan consistent across all proposed deliverables." ]

{ "deliverables": [ { "priority": 1, "asset": "hero asset", "channel": "Webinar follow-up", "reason": "Unlocks feedback quickly while carrying the main promise." }, { "priority": 2, "asset": "proof asset", "channel": "YouTube Shorts", "reason": "Turns the cl...

[ { "stage": "concept sign-off", "owner": "strategy lead", "purpose": "Lock the angle before production expands." }, { "stage": "draft review", "owner": "creative lead", "purpose": "Check whether the proof and hierarchy are still intact." }, { "stage": "stakeholder review", "ow...

[ "The plan can drift if the proof source is older than the current offer or campaign context.", "Too many channels too early may recreate the same review burden the package is meant to reduce.", "If approval-sensitive language is embedded in the hero asset, revisions will become slower and more expensive." ]

{ "primary_metric": "coverage_and_constraint_score", "secondary_metrics": [ "deliverable_fit", "qa_readiness", "dependency_clarity", "message_hierarchy_quality", "handoff_readiness" ], "automatic_failures": [ "Misses the stated proof requirement", "Ignores approval-sensitive constrai...

{ "why_now": "The team has enough material, but not enough clarity on what to ship first.", "commercial_goal": "package one clearer offer", "core_tension": "The team needs enough structure to ship, but not so much scope that the review cycle expands again.", "proof_strategy": "Use one central proof line across ...

[ { "level": 1, "message": "Lead with the operational promise, not the process description.", "why": "This gives the audience a reason to care immediately." }, { "level": 2, "message": "A smaller first pass made review faster and clearer for the whole team.", "why": "The proof line is the ...

[ { "segment": "brand managers", "need": "Fast signal that the asset will be useful before it becomes another thing to review.", "trigger": "concrete proof plus low-hype tone" }, { "segment": "secondary internal stakeholder", "need": "Confidence that the package is reviewable and aligned to th...

[ { "channel": "Webinar follow-up", "job": "carry the main promise", "format_note": "This is the hero surface that sets the tone for the rest of the package." }, { "channel": "YouTube Shorts", "job": "surface the proof", "format_note": "Make the evidence impossible to miss without bloating...

[ { "stage": "brief approval", "owner": "strategy lead", "standard": "The angle and proof are locked before production expands." }, { "stage": "asset review", "owner": "creative lead", "standard": "The hero asset, proof asset, and CTA asset remain aligned." }, { "stage": "stakehold...

{ "hero_angle": "The best asset plan treats the first release as a scoped proof package, not as the whole campaign.", "asset_matrix": [ { "asset_type": "hero asset", "primary_job": "make the promise obvious", "must_keep": "tone plus proof line" }, { "asset_type": "proof asset", ...

[ "The output names what ships first, why it ships first, and what should wait.", "Message hierarchy and asset plan stay consistent across channels.", "Approval ownership is visible enough that the work can move without a second planning pass." ]

{ "modality": "brief-plus-asset-context", "brief_surfaces": [ "creative_brief", "brand_context", "audience_profile", "available_assets" ], "review_stages": [ "concept sign-off", "draft review", "stakeholder review", "final QA" ], "risk_pressure": [ "The plan can drift if ...

[ { "label": "hero-first package", "rationale": "Acceptable when the plan leads with the hero asset and compresses the downstream support assets into fewer deliverables.", "outputs": { "asset_priority": "hero asset first", "channel_bias": "highest-attention channel gets the clearest proof asse...

[ { "label": "brainstorm masquerading as plan", "why_bad": "Produces ideas without naming what ships first or who approves it.", "conflicting_rule": "The first asset should be clearly prioritized and justified." }, { "label": "message drift", "why_bad": "Changes the core promise as assets move...

Hard rows for creative brief translation into asset system planning contain ambiguity, adversarial traps, and high-cost failure modes, so the example tests more than surface fluency and is intended to stress the benchmark slices.

[ "high-context", "constraint-dense", "difficulty-hard", "message-hierarchy", "asset-prioritization", "approval-path", "channel-fit", "dependency-handoff", "stress-case" ]

[ "competing-stakeholder-priorities", "channel-specific-constraint-carryover", "message-order-drift", "unclear-first-asset", "multi-constraint-pressure" ]

[ "Produces a brainstorm instead of a production-ready asset plan.", "Lets the message hierarchy drift between channels.", "Hides approval ownership or dependencies that would block execution.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows." ]

{ "status": "starter-train-ready", "gold_candidate": true, "recommended_reviewers": 2, "adjudication_mode": "dual-review-plus-adjudication", "required_checks": [ "The first asset is clearly prioritized and commercially justified.", "Message hierarchy stays stable across the asset family.", "Approv...

zarn_creative_brief_to_asset_plan_train_0003

train

easy

Zarn

creative_brief

apache-2.0

zarnite-team-reviewed-gold-track-starter

0.93

{ "brand": "Tidal North Labs", "theme": "creator partnership", "project_background": "Tidal North Labs needs support for creator partnership and wants work that feels operator-sharp and concise without losing practical clarity.", "business_goal": "increase qualified replies", "audience": "creator operators", ...

{ "vertical": "consumer hardware", "tone": "operator-sharp and concise", "must_keep": [ "clear value proposition", "one proof point", "one concise CTA" ], "must_avoid": [ "empty lifestyle language", "unsupported performance claims", "bloated launch scope" ] }

{ "primary": "creator operators", "attention_constraint": "executive skim behavior", "trust_builder": "Concrete proof beats generic ambition." }

[ { "asset": "founder notes", "quality": "messy but detailed", "best_use": "angle extraction" }, { "asset": "customer quote", "quality": "short but believable", "best_use": "proof or trust beat" }, { "asset": "product screenshots", "quality": "clean", "best_use": "visual su...

[ "Do not promise unsupported outcomes.", "Keep the first deliverable light enough to review in one pass.", "Flag anything that needs approval instead of smoothing over it.", "Keep the final plan consistent across all proposed deliverables." ]

{ "deliverables": [ { "priority": 1, "asset": "hero asset", "channel": "Email", "reason": "Unlocks feedback quickly while carrying the main promise." }, { "priority": 2, "asset": "proof asset", "channel": "Landing page", "reason": "Turns the claim into somet...

[ { "stage": "concept sign-off", "owner": "strategy lead", "purpose": "Lock the angle before production expands." }, { "stage": "draft review", "owner": "creative lead", "purpose": "Check whether the proof and hierarchy are still intact." }, { "stage": "stakeholder review", "ow...

[ "The plan can drift if the proof source is older than the current offer or campaign context.", "Too many channels too early may recreate the same review burden the package is meant to reduce.", "If approval-sensitive language is embedded in the hero asset, revisions will become slower and more expensive." ]

{ "primary_metric": "coverage_and_constraint_score", "secondary_metrics": [ "deliverable_fit", "qa_readiness", "dependency_clarity", "message_hierarchy_quality", "handoff_readiness" ], "automatic_failures": [ "Misses the stated proof requirement", "Ignores approval-sensitive constrai...

{ "why_now": "The team has enough material, but not enough clarity on what to ship first.", "commercial_goal": "increase qualified replies", "core_tension": "The team needs enough structure to ship, but not so much scope that the review cycle expands again.", "proof_strategy": "Use one central proof line across...

[ { "level": 1, "message": "Lead with the operational promise, not the process description.", "why": "This gives the audience a reason to care immediately." }, { "level": 2, "message": "A smaller first pass made review faster and clearer for the whole team.", "why": "The proof line is the ...

[ { "segment": "creator operators", "need": "Fast signal that the asset will be useful before it becomes another thing to review.", "trigger": "concrete proof plus low-hype tone" }, { "segment": "secondary internal stakeholder", "need": "Confidence that the package is reviewable and aligned to...

[ { "channel": "Email", "job": "carry the main promise", "format_note": "This is the hero surface that sets the tone for the rest of the package." }, { "channel": "Landing page", "job": "surface the proof", "format_note": "Make the evidence impossible to miss without bloating the asset." ...