example_id string | benchmark_split string | difficulty string | product_scope string | task_family string | dataset_license string | annotation_status string | confidence float64 | account_context dict | crm_snapshot dict | interaction_history list | source_text string | source_notes string | transform_goal string | style_guide dict | factual_must_keep list | risky_or_missing_facts list | constraints list | reference_output dict | acceptable_variants list | rubric dict | 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_crm_note_to_followup_messages_train_0000 | train | easy | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"account_name": "Echoframe Media",
"vertical": "creator education",
"company_size": "2-10 people",
"geography": "EMEA",
"opportunity_type": "brand sponsor",
"products_in_scope": [
"video repurposing package",
"creator partnership sprint"
],
"primary_contact": {
"name": "Sofia Brooks",
... | {
"owner": "Lucas",
"pipeline_stage": "expansion planning",
"forecast_band": "$25k-$50k",
"relationship_temperature": "warm",
"decision_timeline": "before the monthly planning meeting",
"last_contact_channel": "Loom",
"last_contact_date": "2026-04-18T00:00:00",
"required_approvals": [
"security revi... | [
{
"date": "2026-04-16T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Sofia Brooks. They emphasized the drag from slow short-form repurposing and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broade... | CRM summary: Sofia Brooks, the partnerships lead at Echoframe Media, is evaluating video repurposing package under a brand sponsor motion. They want to prove value with one tightly scoped improvement, but the drag from slow short-form repurposing is real, and there is extra caution because the current timeline depends ... | Account context:
- Company: Echoframe Media
- Vertical: creator education
- Team size: 2-10 people
- Geography: EMEA
- Opportunity motion: brand sponsor
- Current stage: expansion planning
- Forecast band: $25k-$50k
Call notes:
- Sofia Brooks said the team needs a first step that feels useful without creating a giant ... | Write a production-quality follow-up package for Sofia Brooks: three subject line options, one email, one short channel-native message for Loom, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone operator-sharp and concise, and ... | {
"tone": "operator-sharp and concise",
"audience": "partnerships lead at a creator education company with 2-10 people",
"communication_style": "direct and executive-friendly",
"personalization_rules": [
"mirror their preference for practical language",
"acknowledge the small team and limited review tim... | [
"The opportunity type is brand sponsor.",
"The main product in scope is video repurposing package.",
"The team wants to prove value with one tightly scoped improvement.",
"The strongest pain point is slow short-form repurposing.",
"The preferred next step is to review the scoped pilot doc.",
"Pricing shou... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply security review is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Echoframe Media: a tighter next step for video repurposing package",
"Recap and scoped follow-up for brand sponsor",
"A low-friction way to move video repurposing package forward"
],
"followup_email": "Hi Sofia Brooks,\n\nThanks again for walking me through how Echoframe ... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"the current timeline depends on a senior stakeholder approval",
"legal wants language reviewed before procurement starts"
],
"r... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Easy rows for crm follow-up generation with factual restraint still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
zarn_crm_note_to_followup_messages_train_0001 | train | medium | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"account_name": "Lattice Harbor",
"vertical": "media tools",
"company_size": "51-200 people",
"geography": "APAC",
"opportunity_type": "brand sponsor",
"products_in_scope": [
"automation pilot",
"post-production retainer"
],
"primary_contact": {
"name": "Mia Walker",
"role": "creator m... | {
"owner": "Noah",
"pipeline_stage": "pilot shaping",
"forecast_band": "$50k-$100k",
"relationship_temperature": "high-interest with approval risk",
"decision_timeline": "this Thursday afternoon",
"last_contact_channel": "LinkedIn DM",
"last_contact_date": "2026-04-19T00:00:00",
"required_approvals": [
... | [
{
"date": "2026-04-17T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Mia Walker. They emphasized the drag from an over-scoped first step and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader ro... | CRM summary: Mia Walker, the creator manager at Lattice Harbor, is evaluating automation pilot under a brand sponsor motion. They want to show a quick win before procurement gets involved, but the drag from an over-scoped first step is real, and there is extra caution because the current timeline depends on a senior st... | Account context:
- Company: Lattice Harbor
- Vertical: media tools
- Team size: 51-200 people
- Geography: APAC
- Opportunity motion: brand sponsor
- Current stage: pilot shaping
- Forecast band: $50k-$100k
Call notes:
- Mia Walker said the team needs a first step that feels useful without creating a giant rollout.
- ... | Write a production-quality follow-up package for Mia Walker: three subject line options, one email, one short channel-native message for LinkedIn DM, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone playful and energetic, and ... | {
"tone": "playful and energetic",
"audience": "creator manager at a media tools company with 51-200 people",
"communication_style": "direct and executive-friendly",
"personalization_rules": [
"call back the two-day turnaround goal",
"reference their recent launch timeline",
"mirror their preference... | [
"The opportunity type is brand sponsor.",
"The main product in scope is automation pilot.",
"The team wants to show a quick win before procurement gets involved.",
"The strongest pain point is an over-scoped first step.",
"The preferred next step is to reply with the preferred start week.",
"Pricing shoul... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply finance approval is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Lattice Harbor: a tighter next step for automation pilot",
"Recap and scoped follow-up for brand sponsor",
"A low-friction way to move automation pilot forward"
],
"followup_email": "Hi Mia Walker,\n\nThanks again for walking me through how Lattice Harbor is handling this... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"the current timeline depends on a senior stakeholder approval",
"they asked not to mention pricing until scope is tighter",
"th... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Medium rows for crm follow-up generation with factual restraint mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
zarn_crm_note_to_followup_messages_train_0002 | train | hard | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"account_name": "Velora Motion",
"vertical": "media tools",
"company_size": "201-1000 people",
"geography": "LATAM",
"opportunity_type": "brand sponsor",
"products_in_scope": [
"creator partnership sprint",
"automation pilot"
],
"primary_contact": {
"name": "Ava Walker",
"role": "partn... | {
"owner": "Isla",
"pipeline_stage": "expansion planning",
"forecast_band": "$5k-$10k",
"relationship_temperature": "high-interest with approval risk",
"decision_timeline": "before the monthly planning meeting",
"last_contact_channel": "Loom",
"last_contact_date": "2026-04-20T00:00:00",
"required_approv... | [
{
"date": "2026-04-18T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Ava Walker. They emphasized the drag from slow short-form repurposing and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader ... | CRM summary: Ava Walker, the partnerships lead at Velora Motion, is evaluating creator partnership sprint under a brand sponsor motion. They want to show a quick win before procurement gets involved, but the drag from slow short-form repurposing is real, and there is extra caution because the champion is positive but t... | Account context:
- Company: Velora Motion
- Vertical: media tools
- Team size: 201-1000 people
- Geography: LATAM
- Opportunity motion: brand sponsor
- Current stage: expansion planning
- Forecast band: $5k-$10k
Call notes:
- Ava Walker said the team needs a first step that feels useful without creating a giant rollou... | Write a production-quality follow-up package for Ava Walker: three subject line options, one email, one short channel-native message for Loom, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone fast and witty, and optimize for a... | {
"tone": "fast and witty",
"audience": "partnerships lead at a media tools company with 201-1000 people",
"communication_style": "direct and executive-friendly",
"personalization_rules": [
"recognize the stakeholder handoff issue they described",
"call back the two-day turnaround goal",
"acknowledg... | [
"The opportunity type is brand sponsor.",
"The main product in scope is creator partnership sprint.",
"The team wants to show a quick win before procurement gets involved.",
"The strongest pain point is slow short-form repurposing.",
"The preferred next step is to reply with the preferred start week.",
"P... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply finance approval is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Velora Motion: a tighter next step for creator partnership sprint",
"Recap and scoped follow-up for brand sponsor",
"A low-friction way to move creator partnership sprint forward"
],
"followup_email": "Hi Ava Walker,\n\nThanks again for walking me through how Velora Motio... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"the champion is positive but time-strapped",
"the current timeline depends on a senior stakeholder approval",
"they are compari... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Hard rows for crm follow-up generation with factual restraint 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",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit",
"stress-case"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta",
"multi-constraint-pressure"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step.",
"Collapses several real constraints into a generic polished answer that sounds smoother than the s... | {
"status": "starter-train-ready",
"gold_candidate": true,
"recommended_reviewers": 2,
"adjudication_mode": "dual-review-plus-adjudication",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
... |
zarn_crm_note_to_followup_messages_train_0003 | train | easy | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"account_name": "Orbit Thread",
"vertical": "wellness",
"company_size": "2-10 people",
"geography": "North America",
"opportunity_type": "agency lead",
"products_in_scope": [
"content operating system",
"automation pilot"
],
"primary_contact": {
"name": "Mia Morris",
"role": "founder",... | {
"owner": "Mia",
"pipeline_stage": "solution fit",
"forecast_band": "$50k-$100k",
"relationship_temperature": "neutral but engaged",
"decision_timeline": "once the brand lead is back",
"last_contact_channel": "Slack",
"last_contact_date": "2026-04-21T00:00:00",
"required_approvals": [
"legal review... | [
{
"date": "2026-04-19T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Mia Morris. They emphasized the drag from stretched approval cycles and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader ro... | CRM summary: Mia Morris, the founder at Orbit Thread, is evaluating content operating system under a agency lead motion. They want to increase reply rates without sounding pushy, but the drag from stretched approval cycles is real, and there is extra caution because they asked not to mention pricing until scope is tigh... | Account context:
- Company: Orbit Thread
- Vertical: wellness
- Team size: 2-10 people
- Geography: North America
- Opportunity motion: agency lead
- Current stage: solution fit
- Forecast band: $50k-$100k
Call notes:
- Mia Morris said the team needs a first step that feels useful without creating a giant rollout.
- T... | Write a production-quality follow-up package for Mia Morris: three subject line options, one email, one short channel-native message for Slack, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone playful and energetic, and optimi... | {
"tone": "playful and energetic",
"audience": "founder at a wellness company with 2-10 people",
"communication_style": "practical with light urgency",
"personalization_rules": [
"mention the creator performance concern they raised",
"call back the two-day turnaround goal",
"reference their recent l... | [
"The opportunity type is agency lead.",
"The main product in scope is content operating system.",
"The team wants to increase reply rates without sounding pushy.",
"The strongest pain point is stretched approval cycles.",
"The preferred next step is to book a 25-minute working session.",
"Pricing should s... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply legal review is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Orbit Thread: a tighter next step for content operating system",
"Recap and scoped follow-up for agency lead",
"A low-friction way to move content operating system forward"
],
"followup_email": "Hi Mia Morris,\n\nThanks again for walking me through how Orbit Thread is han... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"they asked not to mention pricing until scope is tighter",
"budget owner has not joined a call yet"
],
"required_approvals": [
... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Easy rows for crm follow-up generation with factual restraint still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
zarn_crm_note_to_followup_messages_train_0004 | train | medium | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"account_name": "Echoframe Media",
"vertical": "health tech",
"company_size": "2-10 people",
"geography": "LATAM",
"opportunity_type": "enterprise pilot",
"products_in_scope": [
"post-production retainer",
"automation pilot"
],
"primary_contact": {
"name": "Lucas Walker",
"role": "part... | {
"owner": "Noah",
"pipeline_stage": "pilot shaping",
"forecast_band": "$25k-$50k",
"relationship_temperature": "neutral but engaged",
"decision_timeline": "early next week",
"last_contact_channel": "phone",
"last_contact_date": "2026-04-22T00:00:00",
"required_approvals": [
"finance approval",
... | [
{
"date": "2026-04-20T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Lucas Walker. They emphasized the drag from stretched approval cycles and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader ... | CRM summary: Lucas Walker, the partnerships lead at Echoframe Media, is evaluating post-production retainer under a enterprise pilot motion. They want to simplify stakeholder handoff before scale-up, but the drag from stretched approval cycles is real, and there is extra caution because the champion is positive but tim... | Account context:
- Company: Echoframe Media
- Vertical: health tech
- Team size: 2-10 people
- Geography: LATAM
- Opportunity motion: enterprise pilot
- Current stage: pilot shaping
- Forecast band: $25k-$50k
Call notes:
- Lucas Walker said the team needs a first step that feels useful without creating a giant rollout... | Write a production-quality follow-up package for Lucas Walker: three subject line options, one email, one short channel-native message for phone, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone playful and energetic, and opti... | {
"tone": "playful and energetic",
"audience": "partnerships lead at a health tech company with 2-10 people",
"communication_style": "practical with light urgency",
"personalization_rules": [
"mirror their preference for practical language",
"acknowledge the small team and limited review time",
"men... | [
"The opportunity type is enterprise pilot.",
"The main product in scope is post-production retainer.",
"The team wants to simplify stakeholder handoff before scale-up.",
"The strongest pain point is stretched approval cycles.",
"The preferred next step is to reply with the preferred start week.",
"Pricing... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply finance approval is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Echoframe Media: a tighter next step for post-production retainer",
"Recap and scoped follow-up for enterprise pilot",
"A low-friction way to move post-production retainer forward"
],
"followup_email": "Hi Lucas Walker,\n\nThanks again for walking me through how Echoframe... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"the champion is positive but time-strapped",
"legal wants language reviewed before procurement starts",
"the current timeline d... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Medium rows for crm follow-up generation with factual restraint mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
zarn_crm_note_to_followup_messages_train_0005 | train | hard | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"account_name": "Harborline Works",
"vertical": "software",
"company_size": "11-50 people",
"geography": "North America",
"opportunity_type": "brand sponsor",
"products_in_scope": [
"content operating system",
"video repurposing package"
],
"primary_contact": {
"name": "Ivy Rivera",
"r... | {
"owner": "Noah",
"pipeline_stage": "discovery",
"forecast_band": "$50k-$100k",
"relationship_temperature": "high-interest with approval risk",
"decision_timeline": "early next week",
"last_contact_channel": "email",
"last_contact_date": "2026-04-23T00:00:00",
"required_approvals": [
"legal review"... | [
{
"date": "2026-04-21T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Ivy Rivera. They emphasized the drag from slow short-form repurposing and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader ... | CRM summary: Ivy Rivera, the brand lead at Harborline Works, is evaluating content operating system under a brand sponsor motion. They want to prove value with one tightly scoped improvement, but the drag from slow short-form repurposing is real, and there is extra caution because they asked not to mention pricing unti... | Account context:
- Company: Harborline Works
- Vertical: software
- Team size: 11-50 people
- Geography: North America
- Opportunity motion: brand sponsor
- Current stage: discovery
- Forecast band: $50k-$100k
Call notes:
- Ivy Rivera said the team needs a first step that feels useful without creating a giant rollout.... | Write a production-quality follow-up package for Ivy Rivera: three subject line options, one email, one short channel-native message for email, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone playful and energetic, and optimi... | {
"tone": "playful and energetic",
"audience": "brand lead at a software company with 11-50 people",
"communication_style": "warm and concise",
"personalization_rules": [
"mention the creator performance concern they raised",
"call back the two-day turnaround goal",
"acknowledge the small team and l... | [
"The opportunity type is brand sponsor.",
"The main product in scope is content operating system.",
"The team wants to prove value with one tightly scoped improvement.",
"The strongest pain point is slow short-form repurposing.",
"The preferred next step is to confirm the internal approver list.",
"Pricin... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply legal review is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Harborline Works: a tighter next step for content operating system",
"Recap and scoped follow-up for brand sponsor",
"A low-friction way to move content operating system forward"
],
"followup_email": "Hi Ivy Rivera,\n\nThanks again for walking me through how Harborline Wo... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"they asked not to mention pricing until scope is tighter",
"they are comparing two vendors in parallel",
"legal wants language ... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Hard rows for crm follow-up generation with factual restraint 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",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit",
"stress-case"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta",
"multi-constraint-pressure"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step.",
"Collapses several real constraints into a generic polished answer that sounds smoother than the s... | {
"status": "starter-train-ready",
"gold_candidate": true,
"recommended_reviewers": 2,
"adjudication_mode": "dual-review-plus-adjudication",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
... |
zarn_crm_note_to_followup_messages_train_0006 | train | easy | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"account_name": "Lattice Harbor",
"vertical": "wellness",
"company_size": "51-200 people",
"geography": "EMEA",
"opportunity_type": "enterprise pilot",
"products_in_scope": [
"content operating system",
"automation pilot"
],
"primary_contact": {
"name": "Zoe Kim",
"role": "partnerships... | {
"owner": "Ava",
"pipeline_stage": "procurement",
"forecast_band": "$10k-$25k",
"relationship_temperature": "cautiously positive",
"decision_timeline": "once the brand lead is back",
"last_contact_channel": "Zoom",
"last_contact_date": "2026-04-24T00:00:00",
"required_approvals": [
"finance approva... | [
{
"date": "2026-04-22T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Zoe Kim. They emphasized the drag from review rounds without a clear owner and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a bro... | CRM summary: Zoe Kim, the partnerships lead at Lattice Harbor, is evaluating content operating system under a enterprise pilot motion. They want to simplify stakeholder handoff before scale-up, but the drag from review rounds without a clear owner is real, and there is extra caution because legal wants language reviewe... | Account context:
- Company: Lattice Harbor
- Vertical: wellness
- Team size: 51-200 people
- Geography: EMEA
- Opportunity motion: enterprise pilot
- Current stage: procurement
- Forecast band: $10k-$25k
Call notes:
- Zoe Kim said the team needs a first step that feels useful without creating a giant rollout.
- They s... | Write a production-quality follow-up package for Zoe Kim: three subject line options, one email, one short channel-native message for Zoom, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone clear and practical, and optimize for... | {
"tone": "clear and practical",
"audience": "partnerships lead at a wellness company with 51-200 people",
"communication_style": "direct and executive-friendly",
"personalization_rules": [
"acknowledge the small team and limited review time",
"recognize the stakeholder handoff issue they described",
... | [
"The opportunity type is enterprise pilot.",
"The main product in scope is content operating system.",
"The team wants to simplify stakeholder handoff before scale-up.",
"The strongest pain point is review rounds without a clear owner.",
"The preferred next step is to book a 25-minute working session.",
"... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply finance approval is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Lattice Harbor: a tighter next step for content operating system",
"Recap and scoped follow-up for enterprise pilot",
"A low-friction way to move content operating system forward"
],
"followup_email": "Hi Zoe Kim,\n\nThanks again for walking me through how Lattice Harbor ... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"legal wants language reviewed before procurement starts",
"budget owner has not joined a call yet"
],
"required_approvals": [
... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Easy rows for crm follow-up generation with factual restraint still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
zarn_crm_note_to_followup_messages_train_0007 | train | medium | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"account_name": "Juniper Relay",
"vertical": "media tools",
"company_size": "2-10 people",
"geography": "EMEA",
"opportunity_type": "agency lead",
"products_in_scope": [
"creative workflow audit",
"post-production retainer"
],
"primary_contact": {
"name": "Nora Nguyen",
"role": "revops... | {
"owner": "Ava",
"pipeline_stage": "discovery",
"forecast_band": "$25k-$50k",
"relationship_temperature": "high-interest with approval risk",
"decision_timeline": "this Thursday afternoon",
"last_contact_channel": "Slack",
"last_contact_date": "2026-04-25T00:00:00",
"required_approvals": [
"procure... | [
{
"date": "2026-04-23T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Nora Nguyen. They emphasized the drag from slow short-form repurposing and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader... | CRM summary: Nora Nguyen, the revops lead at Juniper Relay, is evaluating creative workflow audit under a agency lead motion. They want to show a quick win before procurement gets involved, but the drag from slow short-form repurposing is real, and there is extra caution because budget owner has not joined a call yet. | Account context:
- Company: Juniper Relay
- Vertical: media tools
- Team size: 2-10 people
- Geography: EMEA
- Opportunity motion: agency lead
- Current stage: discovery
- Forecast band: $25k-$50k
Call notes:
- Nora Nguyen said the team needs a first step that feels useful without creating a giant rollout.
- They spec... | Write a production-quality follow-up package for Nora Nguyen: three subject line options, one email, one short channel-native message for Slack, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone confident but low-hype, and opti... | {
"tone": "confident but low-hype",
"audience": "revops lead at a media tools company with 2-10 people",
"communication_style": "warm and concise",
"personalization_rules": [
"mention the creator performance concern they raised",
"reference their recent launch timeline",
"recognize the stakeholder h... | [
"The opportunity type is agency lead.",
"The main product in scope is creative workflow audit.",
"The team wants to show a quick win before procurement gets involved.",
"The strongest pain point is slow short-form repurposing.",
"The preferred next step is to reply with the preferred start week.",
"Pricin... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply procurement onboarding is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Juniper Relay: a tighter next step for creative workflow audit",
"Recap and scoped follow-up for agency lead",
"A low-friction way to move creative workflow audit forward"
],
"followup_email": "Hi Nora Nguyen,\n\nThanks again for walking me through how Juniper Relay is ha... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"budget owner has not joined a call yet",
"the champion is positive but time-strapped",
"they asked not to mention pricing until... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Medium rows for crm follow-up generation with factual restraint mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
zarn_crm_note_to_followup_messages_train_0008 | train | hard | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"account_name": "Harborline Works",
"vertical": "creator education",
"company_size": "201-1000 people",
"geography": "LATAM",
"opportunity_type": "creator outreach",
"products_in_scope": [
"video repurposing package",
"creative workflow audit"
],
"primary_contact": {
"name": "Lucas Patel",... | {
"owner": "Elijah",
"pipeline_stage": "procurement",
"forecast_band": "$5k-$10k",
"relationship_temperature": "cautiously positive",
"decision_timeline": "this Thursday afternoon",
"last_contact_channel": "email",
"last_contact_date": "2026-04-26T00:00:00",
"required_approvals": [
"security review"... | [
{
"date": "2026-04-24T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Lucas Patel. They emphasized the drag from generic post-call follow-up and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader... | CRM summary: Lucas Patel, the partnerships lead at Harborline Works, is evaluating video repurposing package under a creator outreach motion. They want to increase reply rates without sounding pushy, but the drag from generic post-call follow-up is real, and there is extra caution because legal wants language reviewed ... | Account context:
- Company: Harborline Works
- Vertical: creator education
- Team size: 201-1000 people
- Geography: LATAM
- Opportunity motion: creator outreach
- Current stage: procurement
- Forecast band: $5k-$10k
Call notes:
- Lucas Patel said the team needs a first step that feels useful without creating a giant ... | Write a production-quality follow-up package for Lucas Patel: three subject line options, one email, one short channel-native message for email, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone playful and energetic, and optim... | {
"tone": "playful and energetic",
"audience": "partnerships lead at a creator education company with 201-1000 people",
"communication_style": "consultative and low-pressure",
"personalization_rules": [
"reference their recent launch timeline",
"mirror their preference for practical language",
"reco... | [
"The opportunity type is creator outreach.",
"The main product in scope is video repurposing package.",
"The team wants to increase reply rates without sounding pushy.",
"The strongest pain point is generic post-call follow-up.",
"The preferred next step is to confirm the internal approver list.",
"Pricin... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply security review is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Harborline Works: a tighter next step for video repurposing package",
"Recap and scoped follow-up for creator outreach",
"A low-friction way to move video repurposing package forward"
],
"followup_email": "Hi Lucas Patel,\n\nThanks again for walking me through how Harborl... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"legal wants language reviewed before procurement starts",
"they asked not to mention pricing until scope is tighter",
"they are... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Hard rows for crm follow-up generation with factual restraint 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",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit",
"stress-case"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta",
"multi-constraint-pressure"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step.",
"Collapses several real constraints into a generic polished answer that sounds smoother than the s... | {
"status": "starter-train-ready",
"gold_candidate": true,
"recommended_reviewers": 2,
"adjudication_mode": "dual-review-plus-adjudication",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
... |
zarn_crm_note_to_followup_messages_train_0009 | train | easy | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"account_name": "Lattice Harbor",
"vertical": "beauty",
"company_size": "51-200 people",
"geography": "LATAM",
"opportunity_type": "customer expansion",
"products_in_scope": [
"creative workflow audit",
"video repurposing package"
],
"primary_contact": {
"name": "Noah Lopez",
"role": "... | {
"owner": "Elijah",
"pipeline_stage": "discovery",
"forecast_band": "$50k-$100k",
"relationship_temperature": "cautiously positive",
"decision_timeline": "this Thursday afternoon",
"last_contact_channel": "phone",
"last_contact_date": "2026-04-27T00:00:00",
"required_approvals": [
"brand lead sign-... | [
{
"date": "2026-04-25T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Noah Lopez. They emphasized the drag from slow short-form repurposing and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader ... | CRM summary: Noah Lopez, the revops lead at Lattice Harbor, is evaluating creative workflow audit under a customer expansion motion. They want to cut turnaround time before the next launch, but the drag from slow short-form repurposing is real, and there is extra caution because the champion is positive but time-strapp... | Account context:
- Company: Lattice Harbor
- Vertical: beauty
- Team size: 51-200 people
- Geography: LATAM
- Opportunity motion: customer expansion
- Current stage: discovery
- Forecast band: $50k-$100k
Call notes:
- Noah Lopez said the team needs a first step that feels useful without creating a giant rollout.
- The... | Write a production-quality follow-up package for Noah Lopez: three subject line options, one email, one short channel-native message for phone, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone playful and energetic, and optimi... | {
"tone": "playful and energetic",
"audience": "revops lead at a beauty company with 51-200 people",
"communication_style": "practical with light urgency",
"personalization_rules": [
"mirror their preference for practical language",
"mention the creator performance concern they raised",
"reference t... | [
"The opportunity type is customer expansion.",
"The main product in scope is creative workflow audit.",
"The team wants to cut turnaround time before the next launch.",
"The strongest pain point is slow short-form repurposing.",
"The preferred next step is to confirm the internal approver list.",
"Pricing... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply brand lead sign-off is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Lattice Harbor: a tighter next step for creative workflow audit",
"Recap and scoped follow-up for customer expansion",
"A low-friction way to move creative workflow audit forward"
],
"followup_email": "Hi Noah Lopez,\n\nThanks again for walking me through how Lattice Harb... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"the champion is positive but time-strapped",
"budget owner has not joined a call yet"
],
"required_approvals": [
"brand lea... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Easy rows for crm follow-up generation with factual restraint still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
zarn_crm_note_to_followup_messages_train_0010 | train | medium | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"account_name": "Juniper Relay",
"vertical": "health tech",
"company_size": "51-200 people",
"geography": "North America",
"opportunity_type": "enterprise pilot",
"products_in_scope": [
"post-production retainer",
"content operating system"
],
"primary_contact": {
"name": "Mia Chen",
"... | {
"owner": "Lucas",
"pipeline_stage": "expansion planning",
"forecast_band": "$5k-$10k",
"relationship_temperature": "high-interest with approval risk",
"decision_timeline": "before the monthly planning meeting",
"last_contact_channel": "phone",
"last_contact_date": "2026-04-28T00:00:00",
"required_appr... | [
{
"date": "2026-04-26T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Mia Chen. They emphasized the drag from slow short-form repurposing and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader ro... | CRM summary: Mia Chen, the marketing director at Juniper Relay, is evaluating post-production retainer under a enterprise pilot motion. They want to prove value with one tightly scoped improvement, but the drag from slow short-form repurposing is real, and there is extra caution because they asked not to mention pricin... | Account context:
- Company: Juniper Relay
- Vertical: health tech
- Team size: 51-200 people
- Geography: North America
- Opportunity motion: enterprise pilot
- Current stage: expansion planning
- Forecast band: $5k-$10k
Call notes:
- Mia Chen said the team needs a first step that feels useful without creating a giant... | Write a production-quality follow-up package for Mia Chen: three subject line options, one email, one short channel-native message for phone, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone operator-sharp and concise, and opt... | {
"tone": "operator-sharp and concise",
"audience": "marketing director at a health tech company with 51-200 people",
"communication_style": "direct and executive-friendly",
"personalization_rules": [
"reference their recent launch timeline",
"mirror their preference for practical language",
"recogn... | [
"The opportunity type is enterprise pilot.",
"The main product in scope is post-production retainer.",
"The team wants to prove value with one tightly scoped improvement.",
"The strongest pain point is slow short-form repurposing.",
"The preferred next step is to review the scoped pilot doc.",
"Pricing sh... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply procurement onboarding is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Juniper Relay: a tighter next step for post-production retainer",
"Recap and scoped follow-up for enterprise pilot",
"A low-friction way to move post-production retainer forward"
],
"followup_email": "Hi Mia Chen,\n\nThanks again for walking me through how Juniper Relay i... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"they asked not to mention pricing until scope is tighter",
"budget owner has not joined a call yet",
"the current timeline depe... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Medium rows for crm follow-up generation with factual restraint mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
zarn_crm_note_to_followup_messages_train_0011 | train | hard | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"account_name": "Lattice Harbor",
"vertical": "travel",
"company_size": "2-10 people",
"geography": "North America",
"opportunity_type": "creator outreach",
"products_in_scope": [
"automation pilot",
"video repurposing package"
],
"primary_contact": {
"name": "Sofia Lopez",
"role": "cr... | {
"owner": "Isla",
"pipeline_stage": "expansion planning",
"forecast_band": "$25k-$50k",
"relationship_temperature": "neutral but engaged",
"decision_timeline": "early next week",
"last_contact_channel": "Slack",
"last_contact_date": "2026-04-16T00:00:00",
"required_approvals": [
"procurement onboar... | [
{
"date": "2026-04-27T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Sofia Lopez. They emphasized the drag from scattered stakeholder feedback and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broa... | CRM summary: Sofia Lopez, the creator manager at Lattice Harbor, is evaluating automation pilot under a creator outreach motion. They want to cut turnaround time before the next launch, but the drag from scattered stakeholder feedback is real, and there is extra caution because the current timeline depends on a senior ... | Account context:
- Company: Lattice Harbor
- Vertical: travel
- Team size: 2-10 people
- Geography: North America
- Opportunity motion: creator outreach
- Current stage: expansion planning
- Forecast band: $25k-$50k
Call notes:
- Sofia Lopez said the team needs a first step that feels useful without creating a giant r... | Write a production-quality follow-up package for Sofia Lopez: three subject line options, one email, one short channel-native message for Slack, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone premium and restrained, and opti... | {
"tone": "premium and restrained",
"audience": "creator manager at a travel company with 2-10 people",
"communication_style": "warm and concise",
"personalization_rules": [
"reference their recent launch timeline",
"mirror their preference for practical language",
"recognize the stakeholder handoff... | [
"The opportunity type is creator outreach.",
"The main product in scope is automation pilot.",
"The team wants to cut turnaround time before the next launch.",
"The strongest pain point is scattered stakeholder feedback.",
"The preferred next step is to book a 25-minute working session.",
"Pricing should ... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply procurement onboarding is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"Lattice Harbor: a tighter next step for automation pilot",
"Recap and scoped follow-up for creator outreach",
"A low-friction way to move automation pilot forward"
],
"followup_email": "Hi Sofia Lopez,\n\nThanks again for walking me through how Lattice Harbor is handling ... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"the current timeline depends on a senior stakeholder approval",
"they are comparing two vendors in parallel",
"budget owner has... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Hard rows for crm follow-up generation with factual restraint 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",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit",
"stress-case"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta",
"multi-constraint-pressure"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step.",
"Collapses several real constraints into a generic polished answer that sounds smoother than the s... | {
"status": "starter-train-ready",
"gold_candidate": true,
"recommended_reviewers": 2,
"adjudication_mode": "dual-review-plus-adjudication",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
... |
zarn_crm_note_to_followup_messages_train_0012 | train | easy | Zarn | rewrite | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"account_name": "First Mile Creative",
"vertical": "creator education",
"company_size": "11-50 people",
"geography": "North America",
"opportunity_type": "enterprise pilot",
"products_in_scope": [
"automation pilot",
"post-production retainer"
],
"primary_contact": {
"name": "Liam Shah",
... | {
"owner": "Mia",
"pipeline_stage": "procurement",
"forecast_band": "$5k-$10k",
"relationship_temperature": "warm",
"decision_timeline": "before the monthly planning meeting",
"last_contact_channel": "LinkedIn DM",
"last_contact_date": "2026-04-17T00:00:00",
"required_approvals": [
"brand lead sign-... | [
{
"date": "2026-04-28T00:00:00",
"channel": "Zoom",
"summary": "Discovery call with Liam Shah. They emphasized the drag from an over-scoped first step and asked for a lighter first step.",
"customer_signal": "engaged",
"outcome": "Agreed to receive a tighter scope before discussing a broader rol... | CRM summary: Liam Shah, the founder at First Mile Creative, is evaluating automation pilot under a enterprise pilot motion. They want to show a quick win before procurement gets involved, but the drag from an over-scoped first step is real, and there is extra caution because legal wants language reviewed before procure... | Account context:
- Company: First Mile Creative
- Vertical: creator education
- Team size: 11-50 people
- Geography: North America
- Opportunity motion: enterprise pilot
- Current stage: procurement
- Forecast band: $5k-$10k
Call notes:
- Liam Shah said the team needs a first step that feels useful without creating a ... | Write a production-quality follow-up package for Liam Shah: three subject line options, one email, one short channel-native message for LinkedIn DM, one gentle bump message for no reply after a few business days, and one internal CRM next-step note. Preserve the factual notes, keep the tone playful and energetic, and o... | {
"tone": "playful and energetic",
"audience": "founder at a creator education company with 11-50 people",
"communication_style": "warm and concise",
"personalization_rules": [
"mention the creator performance concern they raised",
"call back the two-day turnaround goal",
"acknowledge the small team... | [
"The opportunity type is enterprise pilot.",
"The main product in scope is automation pilot.",
"The team wants to show a quick win before procurement gets involved.",
"The strongest pain point is an over-scoped first step.",
"The preferred next step is to share one representative asset for audit.",
"Prici... | [
"Do not invent a discount, budget ceiling, or approved contract term.",
"Do not imply brand lead sign-off is already complete unless the notes say so.",
"Do not claim a start date beyond the stated review window.",
"If procurement timing is unclear, frame it as pending rather than decided."
] | [
"Preserve all must-keep facts unless explicitly flagged as unresolved.",
"Do not invent a discount, budget, or contractual approval.",
"Keep the relationship warm without sounding needy or overly urgent.",
"Use one clear next step instead of stacking multiple asks.",
"Reflect the customer's communication pr... | {
"email_subject_options": [
"First Mile Creative: a tighter next step for automation pilot",
"Recap and scoped follow-up for enterprise pilot",
"A low-friction way to move automation pilot forward"
],
"followup_email": "Hi Liam Shah,\n\nThanks again for walking me through how First Mile Creative is h... | [
"A follow-up that preserves the same facts but uses a slightly warmer, more conversational rhythm.",
"A more executive version that trims adjectives and keeps the ask even tighter.",
"A version that foregrounds the next step first, as long as it still acknowledges the approval friction."
] | {
"primary_metric": "factual_recall_and_tone_score",
"secondary_metrics": [
"personalization_use",
"channel_fit",
"hallucination_rate",
"cta_quality"
],
"automatic_failures": [
"Invents budget, discount, approval status, or signed timeline.",
"Drops a must-keep fact that materially chang... | {
"modality": "crm-notes-and-interaction-history",
"sources": [
"account_context",
"crm_snapshot",
"interaction_history",
"source_notes"
],
"risk_flags": [
"legal wants language reviewed before procurement starts",
"the current timeline depends on a senior stakeholder approval"
],
"r... | [
{
"label": "warmer relationship-preserving outreach",
"rationale": "Acceptable when the message uses a softer, more relational opening but preserves the same facts and one-step CTA.",
"outputs": {
"email_shift": "softer opening sentence",
"dm_shift": "more conversational cadence without losi... | [
{
"label": "hallucinated certainty",
"why_bad": "States pricing, discounts, or approval status that the notes do not support.",
"conflicting_rule": "Do not invent a discount, budget, or contractual approval."
},
{
"label": "generic follow-up",
"why_bad": "Ignores the specific pain points and... | Easy rows for crm follow-up generation with factual restraint still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"approval-ambiguity",
"single-cta",
"personalization-vs-restraint",
"pipeline-state-faithfulness",
"channel-fit"
] | [
"budget-inference-trap",
"unapproved-discount",
"relationship-temperature-drift",
"overly-pushy-cta"
] | [
"Invents budget, discounting, approval status, or timing certainty.",
"Sounds generic because it ignores the specific notes and preferences.",
"Stacks multiple asks instead of one clean low-friction next step."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"All must-keep facts survive in the email, short message, and CRM note.",
"The outreach stays warm and specific without becoming pushy.",
"N... |
End of preview. Expand in Data Studio
Zarn CRM Note to Followup Messages
Dataset Description
High-context CRM notes transformed into personalized follow-up emails, DMs, and next-step nudges with factual preservation checks.
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
CRM follow-up is commercially valuable because it turns messy relationship context into action, and buyers care a lot about not sounding generic or inventing facts.
Benchmark Goal
Evaluate factual preservation, personalization quality, channel fit, and hallucination resistance in CRM follow-up generation.
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: 14,000
- Validation: 1,800
- Test: 1,800
- Total target rows: 17,600
Recommended Metrics
factual_recall_and_tone_scorepersonalization_usechannel_fithallucination_ratecta_quality
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
account_context: account profile, contact details, products in scope, and stakeholders.crm_snapshot: pipeline stage, forecast band, relationship temperature, approvals, and risk flags.interaction_history: several prior touches with summaries and outcomes.source_notes: long-form CRM and call notes designed to test factual retention.reference_output: multiple subject options, one full email, one DM, one gentle bump, and one internal CRM note.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-crm-note-to-followup-messages - Example upload command:
python upload_to_huggingface.py --dataset-folder "push/high-ecosystem-need/Zarn-CRM-Note-to-Followup-Messages" --repo-id "zarnite/zarn-crm-note-to-followup-messages" - 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-CRM-Note-to-Followup-Messages" --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
- 57