example_id string | benchmark_split string | difficulty string | product_scope string | task_family string | dataset_license string | annotation_status string | confidence float64 | creative_brief dict | brand_context dict | audience_profile dict | available_assets list | constraints list | reference_output dict | review_path list | risk_register list | rubric dict | project_frame dict | message_hierarchy list | audience_segments list | channel_strategy list | approval_matrix list | reference_brief_package dict | success_checks list | evidence_manifest dict | reference_variants list | negative_examples list | difficulty_rationale string | benchmark_slices list | adversarial_features list | expected_failure_modes list | review_readiness dict |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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."
... | [
{
"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_0004 | train | medium | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Signal Oak",
"theme": "ugc collection",
"project_background": "Signal Oak needs support for ugc collection and wants work that feels expert and calm without losing practical clarity.",
"business_goal": "tighten launch sequencing",
"audience": "creator operators",
"channels": [
"Email",
"... | {
"vertical": "media tools",
"tone": "expert and calm",
"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": "LinkedIn",
"reason": "Turns the claim into something... | [
{
"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": "tighten launch sequencing",
"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": "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": "LinkedIn",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating the asset."
},
... | [
{
"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_0005 | train | hard | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Glowforge Labs",
"theme": "seasonal launch",
"project_background": "Glowforge Labs needs support for seasonal launch and wants work that feels playful and energetic without losing practical clarity.",
"business_goal": "package one clearer offer",
"audience": "marketing leads",
"channels": [
... | {
"vertical": "beauty",
"tone": "playful and energetic",
"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": "low review bandwidth",
"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": "App onboarding",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "Webinar follow-up",
"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": "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": "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": "App onboarding",
"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... | [
{
"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_0006 | train | easy | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Echoframe Media",
"theme": "creator partnership",
"project_background": "Echoframe Media needs support for creator partnership and wants work that feels confident but low-hype without losing practical clarity.",
"business_goal": "tighten launch sequencing",
"audience": "busy founders",
"channels... | {
"vertical": "health tech",
"tone": "confident but low-hype",
"must_keep": [
"clear value proposition",
"one proof point",
"one concise CTA"
],
"must_avoid": [
"empty lifestyle language",
"unsupported performance claims",
"bloated launch scope"
]
} | {
"primary": "busy founders",
"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": "LinkedIn",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "Email",
"reason": "Turns the claim into something... | [
{
"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 launch window is close enough that the first package must be reviewable immediately.",
"commercial_goal": "tighten launch sequencing",
"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... | [
{
"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": "busy founders",
"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 the... | [
{
"channel": "LinkedIn",
"job": "carry the main promise",
"format_note": "This is the hero surface that sets the tone for the rest of the package."
},
{
"channel": "Email",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating the asset."
},
... | [
{
"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_0007 | train | medium | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Glowforge Labs",
"theme": "event promo",
"project_background": "Glowforge Labs needs support for event promo and wants work that feels playful and energetic without losing practical clarity.",
"business_goal": "package one clearer offer",
"audience": "lean internal teams",
"channels": [
"Ins... | {
"vertical": "wellness",
"tone": "playful and energetic",
"must_keep": [
"clear value proposition",
"one proof point",
"one concise CTA"
],
"must_avoid": [
"empty lifestyle language",
"unsupported performance claims",
"bloated launch scope"
]
} | {
"primary": "lean internal teams",
"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": "Instagram Reels",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "TikTok",
"reason": "Turns the claim into s... | [
{
"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": "lean internal teams",
"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 ... | [
{
"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": "TikTok",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating the asset... | [
{
"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_0008 | train | hard | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Orbit Thread",
"theme": "new feature push",
"project_background": "Orbit Thread needs support for new feature push and wants work that feels fast and witty without losing practical clarity.",
"business_goal": "increase qualified replies",
"audience": "busy founders",
"channels": [
"LinkedIn"... | {
"vertical": "software",
"tone": "fast and witty",
"must_keep": [
"clear value proposition",
"one proof point",
"one concise CTA"
],
"must_avoid": [
"empty lifestyle language",
"unsupported performance claims",
"bloated launch scope"
]
} | {
"primary": "busy founders",
"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": "LinkedIn",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "Webinar follow-up",
"reason": "Turns the claim in... | [
{
"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 launch window is close enough that the first package must be reviewable immediately.",
"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 proo... | [
{
"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": "busy founders",
"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 the... | [
{
"channel": "LinkedIn",
"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 a... | [
{
"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_0009 | train | easy | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Lattice Harbor",
"theme": "ugc collection",
"project_background": "Lattice Harbor needs support for ugc collection and wants work that feels clear and practical without losing practical clarity.",
"business_goal": "increase qualified replies",
"audience": "brand managers",
"channels": [
"You... | {
"vertical": "media tools",
"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": "YouTube Shorts",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "App onboarding",
"reason": "Turns the claim... | [
{
"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 launch window is close enough that the first package must be reviewable immediately.",
"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 proo... | [
{
"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": "YouTube Shorts",
"job": "carry the main promise",
"format_note": "This is the hero surface that sets the tone for the rest of the package."
},
{
"channel": "App onboarding",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating th... | [
{
"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_0010 | train | medium | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Juniper Relay",
"theme": "event promo",
"project_background": "Juniper Relay needs support for event promo and wants work that feels clear and practical without losing practical clarity.",
"business_goal": "package one clearer offer",
"audience": "marketing leads",
"channels": [
"App onboard... | {
"vertical": "fintech",
"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": "low review bandwidth",
"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": "App onboarding",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "Email",
"reason": "Turns the claim into som... | [
{
"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": "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": "App onboarding",
"job": "carry the main promise",
"format_note": "This is the hero surface that sets the tone for the rest of the package."
},
{
"channel": "Email",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating the asset."... | [
{
"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_0011 | train | hard | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Northbeam Studio",
"theme": "creator partnership",
"project_background": "Northbeam Studio needs support for creator partnership and wants work that feels expert and calm without losing practical clarity.",
"business_goal": "improve review speed",
"audience": "marketing leads",
"channels": [
... | {
"vertical": "wellness",
"tone": "expert and calm",
"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": "Webinar follow-up",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "Landing page",
"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": "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 acro... | [
{
"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": "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": "Landing page",
"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... | 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_0012 | train | easy | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Signal Oak",
"theme": "new feature push",
"project_background": "Signal Oak needs support for new feature push and wants work that feels operator-sharp and concise without losing practical clarity.",
"business_goal": "improve review speed",
"audience": "creator operators",
"channels": [
"App... | {
"vertical": "creator education",
"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": "low review bandwidth",
"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": "App onboarding",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "LinkedIn",
"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": "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": "App onboarding",
"job": "carry the main promise",
"format_note": "This is the hero surface that sets the tone for the rest of the package."
},
{
"channel": "LinkedIn",
"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... | 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_0013 | train | medium | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Echoframe Media",
"theme": "seasonal launch",
"project_background": "Echoframe Media needs support for seasonal launch and wants work that feels clear and practical without losing practical clarity.",
"business_goal": "improve review speed",
"audience": "marketing leads",
"channels": [
"App ... | {
"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": "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": "App onboarding",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "Landing page",
"reason": "Turns the claim i... | [
{
"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": "App onboarding",
"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 ... | [
{
"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_0014 | train | hard | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Signal Oak",
"theme": "seasonal launch",
"project_background": "Signal Oak needs support for seasonal launch and wants work that feels operator-sharp and concise without losing practical clarity.",
"business_goal": "tighten launch sequencing",
"audience": "marketing leads",
"channels": [
"We... | {
"vertical": "travel",
"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": "marketing leads",
"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": "tighten launch sequencing",
"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": "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": "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_0015 | train | easy | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Velora Motion",
"theme": "creator partnership",
"project_background": "Velora Motion needs support for creator partnership and wants work that feels playful and energetic without losing practical clarity.",
"business_goal": "improve review speed",
"audience": "creator operators",
"channels": [
... | {
"vertical": "beauty",
"tone": "playful and energetic",
"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": "App onboarding",
"reason": "Turns the claim into som... | [
{
"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": "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": "App onboarding",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating the asset."... | [
{
"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_0016 | train | medium | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Orbit Thread",
"theme": "creator partnership",
"project_background": "Orbit Thread needs support for creator partnership and wants work that feels expert and calm without losing practical clarity.",
"business_goal": "package one clearer offer",
"audience": "lean internal teams",
"channels": [
... | {
"vertical": "software",
"tone": "expert and calm",
"must_keep": [
"clear value proposition",
"one proof point",
"one concise CTA"
],
"must_avoid": [
"empty lifestyle language",
"unsupported performance claims",
"bloated launch scope"
]
} | {
"primary": "lean internal teams",
"attention_constraint": "low review bandwidth",
"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": "YouTube Shorts",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "App onboarding",
"reason": "Turns the claim... | [
{
"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 launch window is close enough that the first package must be reviewable immediately.",
"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... | [
{
"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": "lean internal teams",
"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 ... | [
{
"channel": "YouTube Shorts",
"job": "carry the main promise",
"format_note": "This is the hero surface that sets the tone for the rest of the package."
},
{
"channel": "App onboarding",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating th... | [
{
"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_0017 | train | hard | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Harborline Works",
"theme": "event promo",
"project_background": "Harborline Works needs support for event promo and wants work that feels playful and energetic without losing practical clarity.",
"business_goal": "package one clearer offer",
"audience": "brand managers",
"channels": [
"Webi... | {
"vertical": "travel",
"tone": "playful and energetic",
"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": "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": "Webinar follow-up",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "LinkedIn",
"reason": "Turns the claim in... | [
{
"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": "LinkedIn",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating the a... | [
{
"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_0018 | train | easy | Zarn | creative_brief | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Orbit Thread",
"theme": "seasonal launch",
"project_background": "Orbit Thread needs support for seasonal launch and wants work that feels confident but low-hype without losing practical clarity.",
"business_goal": "improve review speed",
"audience": "lean internal teams",
"channels": [
"Lin... | {
"vertical": "travel",
"tone": "confident but low-hype",
"must_keep": [
"clear value proposition",
"one proof point",
"one concise CTA"
],
"must_avoid": [
"empty lifestyle language",
"unsupported performance claims",
"bloated launch scope"
]
} | {
"primary": "lean internal teams",
"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": "LinkedIn",
"reason": "Unlocks feedback quickly while carrying the main promise."
},
{
"priority": 2,
"asset": "proof asset",
"channel": "Email",
"reason": "Turns the claim into something... | [
{
"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 launch window is close enough that the first package must be reviewable immediately.",
"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... | [
{
"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": "lean internal teams",
"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 ... | [
{
"channel": "LinkedIn",
"job": "carry the main promise",
"format_note": "This is the hero surface that sets the tone for the rest of the package."
},
{
"channel": "Email",
"job": "surface the proof",
"format_note": "Make the evidence impossible to miss without bloating the asset."
},
... | [
{
"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... |
End of preview. Expand in Data Studio
Zarn Creative Brief to Asset Plan
Dataset Description
Creative briefs mapped to delivery plans, asset priorities, review checkpoints, and dependencies.
Team Attribution
This dataset was created and reviewed by the Zarnite team through internal benchmark design, generation, and quality-control workflows. It should be presented as a Zarnite-authored benchmark starter pack, not as a purely human-collected field corpus.
Ecosystem Need Tier
High Ecosystem Need
Why This Category Is Attractive
Turning messy business goals into an actionable creative system is a high-value creative-ops use case, but few public datasets capture asset hierarchy, review flow, and handoff logic together.
Benchmark Goal
Evaluate whether a model can transform a creative brief into a production-ready asset plan with strong message hierarchy, approval flow, and downstream handoff clarity.
Included In This Folder
data/train.jsonl,data/validation.jsonl,data/test.jsonl: starter benchmark splits with 1200 total rows.schema.json: JSON Schema for row validation.benchmark_spec.json: metrics, quality gates, and target release scale.LICENSE.md: folder-local license notice for self-contained publishing.PUBLISHING.md: repo-specific publish instructions for Hugging Face.hf_repo_template.json: machine-readable repo template used by the uploader script.
Target Public Scale
- Train: 16,000
- Validation: 2,000
- Test: 2,000
- Total target rows: 20,000
Recommended Metrics
coverage_and_constraint_scoredeliverable_fitmessage_hierarchy_qualitydependency_clarityhandoff_readiness
Gold-Track Benchmark Assets
ANNOTATION_GUIDELINES.md: how to expand rows without drifting from the benchmark purpose.REVIEW_PROTOCOL.md: how to audit validation and test rows with dual review and adjudication.BASELINE_EVAL_SPEC.json: expected output contract, slice reporting, and release thresholds.RELEASE_CHECKLIST.md: final pre-publish checks for the public Hugging Face release.SCORING_PROFILE.json: prediction keys, scoring expectations, and slice reporting requirements.prediction_template.jsonl: starter template for benchmark submissions or baseline runs.
Expanded Row Anatomy
project_frame: why the work matters now, what commercial goal it serves, and what tension the plan must resolve.message_hierarchy: the ordered narrative the asset family should preserve.channel_strategyandapproval_matrix: how the plan changes by surface and who has to approve what.reference_brief_package: the gold high-level asset system, not just a loose brainstorm.difficulty_rationale: why the row belongs in its difficulty bucket instead of a weaker slice.benchmark_slices: named reporting slices such as approval friction, proof preservation, or citation traps.adversarial_features,expected_failure_modes, andreview_readiness: what the row is testing and how a gold-track reviewer should treat it.evidence_manifest,reference_variants, andnegative_examples: the source evidence boundary, acceptable alternate answers, and concrete failure cases.
Hugging Face Deployment
This folder is self-contained and can be uploaded as its own Hugging Face dataset repository.
- Suggested repo id:
zarnite/zarn-creative-brief-to-asset-plan - Example upload command:
python upload_to_huggingface.py --dataset-folder "push/high-ecosystem-need/Zarn-Creative-Brief-to-Asset-Plan" --repo-id "zarnite/zarn-creative-brief-to-asset-plan" - You can swap the namespace by passing
--namespace YOUR_USERNAMEto the uploader.
Local Evaluation
- Example eval command:
python run_priority_eval.py --dataset-folder "push/high-ecosystem-need/Zarn-Creative-Brief-to-Asset-Plan" --splits validation test prediction_template.jsonlgives the required output shape for local or leaderboard-style submissions.
License
This package is marked apache-2.0. The rows in this folder are original starter examples for benchmark packaging.
- Downloads last month
- 103