example_id string | benchmark_split string | difficulty string | product_scope string | task_family string | dataset_license string | annotation_status string | confidence float64 | meeting_context dict | agenda list | transcript list | reference_summary dict | reference_decisions list | reference_action_items list | reference_followup_package dict | open_questions list | rubric dict | pre_read_context dict | decision_tensions list | followup_risks list | quality_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_meeting_to_actions_train_0100 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "First Mile Creative",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Z... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Zoe Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Liam Morris",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a teaser-first cut for the client onboarding workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the n... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Zoe Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Zoe Walker",
"role": "creative lead",
"task": "Revise the client onboarding brief around a teaser-first cut.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "First Mile Creative client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed tha... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0101 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Velora Motion",
"meeting_type": "creative review",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ivy Diaz",
"r... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Ivy Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Miles Morgan",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a proof-first recap for the creative review workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof a... | [
{
"owner": "Ivy Diaz",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Velora Motion creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal l... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Velora Motion working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Velora Motion approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Velora Motion... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Velora Motion working brief",
"Velora Motion approval thread",
"Velora Motion launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0102 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Signal Oak",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-24T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ethan Broo... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Ethan Brooks",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-24."
},
{
"speaker": "Isla Patel",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"executive_summary": "The team aligned on using a lightweight review draft for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Ethan Brooks",
"role": "creative lead",
"task": "Revise the client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable... | {
"email_subject": "Signal Oak client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Signal Oak working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Signal Oak approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Signal Oak launch t... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Signal Oak working brief",
"Signal Oak approval thread",
"Signal Oak launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versus over... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0103 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Harborline Works",
"meeting_type": "creative review",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia Chen"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Mia Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Noah Walker",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a tighter pilot package for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Mia Chen",
"role": "creative lead",
"task": "Revise the creative review brief around a tighter pilot package.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Harborline Works creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0104 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Tidal North Labs",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia Morgan",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Mia Morgan",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Nora Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a teaser-first cut for the vendor sync workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next re... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Mia Morgan",
"role": "creative lead",
"task": "Revise the vendor sync brief around a teaser-first cut.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what p... | {
"email_subject": "Tidal North Labs vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakehold... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0105 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Tidal North Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Elijah Walker... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Elijah Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Liam Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a teaser-first cut for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next re... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Elijah Walker",
"role": "creative lead",
"task": "Revise the retrospective brief around a teaser-first cut.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Chen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Tidal North Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the appro... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0106 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Northbeam Studio",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Miles Shah",... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Miles Shah",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Ivy Chen",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a proof-first recap for the campaign planning workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Miles Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Miles Shah",
"role": "creative lead",
"task": "Revise the campaign planning brief around a proof-first recap.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Northbeam Studio campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0107 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Juniper Relay",
"meeting_type": "creative review",
"meeting_date": "2026-05-01T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "E... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Elijah Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Miles Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved w... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Elijah Chen",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"email_subject": "Juniper Relay creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0108 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Echoframe Media",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-28T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Lucas... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Lucas Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Nora Brooks",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a proof-first recap for the campaign planning workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the ... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Lucas Diaz",
"role": "creative lead",
"task": "Revise the campaign planning brief around a proof-first recap.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Echoframe Media campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0109 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "First Mile Creative",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Isla Morris",
"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Isla Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Nora Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next rev... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Isla Morris",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "First Mile Creative vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that le... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0110 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Velora Motion",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-22T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Elijah Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Ethan Chen",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a teaser-first cut for the campaign planning workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next revie... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Elijah Chen",
"role": "creative lead",
"task": "Revise the campaign planning brief around a teaser-first cut.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Velora Motion campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that lega... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Velora Motion working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Velora Motion approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Velora Motion... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Velora Motion working brief",
"Velora Motion approval thread",
"Velora Motion launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0111 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Harborline Works",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-08T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Sofia Diaz",... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Sofia Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Sofia Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a tighter pilot package for the campaign planning workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved wh... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Sofia Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Sofia Diaz",
"role": "creative lead",
"task": "Revise the campaign planning brief around a tighter pilot package.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Harborline Works campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0112 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Glowforge Labs",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Nora W... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Nora Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Ivy Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a teaser-first cut for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the nex... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Nora Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Nora Walker",
"role": "creative lead",
"task": "Revise the client onboarding brief around a teaser-first cut.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Glowforge Labs client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Glowforge Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Glowforge Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Glowforge L... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Glowforge Labs working brief",
"Glowforge Labs approval thread",
"Glowforge Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0113 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Tidal North Labs",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Nora... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Nora Rivera",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Mia Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the ... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Nora Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Nora Rivera",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Tidal North Labs client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0114 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Lattice Harbor",
"meeting_type": "retrospective",
"meeting_date": "2026-04-28T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ivy ... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Ivy Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Mia Morris",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a lightweight review draft for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Ivy Walker",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Lattice Harbor retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Lattice Harbor working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Lattice Harbor approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Lattice Har... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Lattice Harbor working brief",
"Lattice Harbor approval thread",
"Lattice Harbor launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0115 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Echoframe Media",
"meeting_type": "creative review",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Nora Patel",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Nora Patel",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Ethan Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a teaser-first cut for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the nex... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Nora Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Nora Patel",
"role": "creative lead",
"task": "Revise the creative review brief around a teaser-first cut.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Echoframe Media creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two st... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0116 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Glowforge Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-05-01T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mile... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Miles Lopez",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Zoe Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a lightweight review draft for the retrospective workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next r... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Miles Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Miles Lopez",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"email_subject": "Glowforge Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that leg... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Glowforge Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Glowforge Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Glowforge L... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Glowforge Labs working brief",
"Glowforge Labs approval thread",
"Glowforge Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0117 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "First Mile Creative",
"meeting_type": "creative review",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia M... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Mia Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Jalen Brooks",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a tighter pilot package for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Mia Morris",
"role": "creative lead",
"task": "Revise the creative review brief around a tighter pilot package.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Mia Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "First Mile Creative creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed th... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0118 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Juniper Relay",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-08T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Isla Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Ava Chen",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a lightweight review draft for the campaign planning workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Isla Chen",
"role": "creative lead",
"task": "Revise the campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable ... | {
"email_subject": "Juniper Relay campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0119 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Harborline Works",
"meeting_type": "creative review",
"meeting_date": "2026-05-15T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Lucas Morgan",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Miles Brooks",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"executive_summary": "The team aligned on using a teaser-first cut for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the nex... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Lucas Morgan",
"role": "creative lead",
"task": "Revise the creative review brief around a teaser-first cut.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Harborline Works creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two s... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0120 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Glowforge Labs",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Jalen Morgan",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Jalen Morgan",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Noah Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Jalen Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Jalen Morgan",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Glowforge Labs vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the sou... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Glowforge Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Glowforge Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Glowforge L... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Glowforge Labs working brief",
"Glowforge Labs approval thread",
"Glowforge Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0121 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Glowforge Labs",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Zoe Morris",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Zoe Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Mia Morris",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I ... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next rev... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Zoe Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Zoe Morris",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Glowforge Labs vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal l... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Glowforge Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Glowforge Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Glowforge L... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Glowforge Labs working brief",
"Glowforge Labs approval thread",
"Glowforge Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0122 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Velora Motion",
"meeting_type": "creative review",
"meeting_date": "2026-05-08T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ivy Morgan",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Ivy Morgan",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Liam Chen",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a proof-first recap for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Ivy Morgan",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Velora Motion creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the app... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Velora Motion working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Velora Motion approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Velora Motion... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Velora Motion working brief",
"Velora Motion approval thread",
"Velora Motion launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0123 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Signal Oak",
"meeting_type": "retrospective",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia Chen",
"role": "... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Mia Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Lucas Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a proof-first recap for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next r... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof a... | [
{
"owner": "Mia Chen",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what p... | {
"email_subject": "Signal Oak retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver w... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Signal Oak working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Signal Oak approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Signal Oak launch t... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Signal Oak working brief",
"Signal Oak approval thread",
"Signal Oak launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versus over... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0124 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "First Mile Creative",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-24T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "J... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Jalen Brooks",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-24."
},
{
"speaker": "Ava Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a lightweight review draft for the campaign planning workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still maki... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Jalen Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Jalen Brooks",
"role": "creative lead",
"task": "Revise the campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable... | {
"email_subject": "First Mile Creative campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also ag... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0125 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Tidal North Labs",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-08T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Noah Patel",... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Noah Patel",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Sofia Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making ... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Noah Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Noah Patel",
"role": "creative lead",
"task": "Revise the client onboarding brief around a tighter pilot package.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Tidal North Labs client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0126 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Orbit Thread",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Zoe Walker",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Zoe Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Mia Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a proof-first recap for the campaign planning workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the ... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Zoe Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Zoe Walker",
"role": "creative lead",
"task": "Revise the campaign planning brief around a proof-first recap.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Orbit Thread campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Orbit Thread working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Orbit Thread approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Orbit Thread la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Orbit Thread working brief",
"Orbit Thread approval thread",
"Orbit Thread launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0127 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Glowforge Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Sofia Nguyen",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Sofia Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Nora Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a teaser-first cut for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next re... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Sofia Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Sofia Nguyen",
"role": "creative lead",
"task": "Revise the retrospective brief around a teaser-first cut.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Glowforge Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approve... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Glowforge Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Glowforge Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Glowforge L... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Glowforge Labs working brief",
"Glowforge Labs approval thread",
"Glowforge Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0128 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "First Mile Creative",
"meeting_type": "retrospective",
"meeting_date": "2026-05-15T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": ... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Lucas Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Isla Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a lightweight review draft for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Lucas Nguyen",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"email_subject": "First Mile Creative retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed tha... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0129 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Tidal North Labs",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Lucas Morgan",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Lucas Morgan",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Sofia Diaz",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the n... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Lucas Morgan",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"email_subject": "Tidal North Labs vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the a... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0130 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Echoframe Media",
"meeting_type": "retrospective",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Miles Kim",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Miles Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Nora Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a proof-first recap for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next r... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Miles Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Miles Kim",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Echoframe Media retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the appro... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0131 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Echoframe Media",
"meeting_type": "retrospective",
"meeting_date": "2026-04-28T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Mia Brooks",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Mia Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I... | {
"executive_summary": "The team aligned on using a proof-first recap for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Mia Brooks",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Jalen Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Echoframe Media retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stake... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0132 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Echoframe Media",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Isla Walker",... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Isla Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Ava Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a lightweight review draft for the campaign planning workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Isla Walker",
"role": "creative lead",
"task": "Revise the campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable... | {
"email_subject": "Echoframe Media campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0133 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Northbeam Studio",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-28T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Liam Morris",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Liam Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Nora Chen",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I ... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next rev... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Liam Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Liam Morris",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Northbeam Studio vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0134 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Juniper Relay",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-12T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Mia Shah",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Ethan Brooks",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making th... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Mia Shah",
"role": "creative lead",
"task": "Revise the client onboarding brief around a tighter pilot package.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Juniper Relay client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0135 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Cinder Atlas",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ethan Shah",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Ethan Shah",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Ethan Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"executive_summary": "The team aligned on using a teaser-first cut for the client onboarding workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while s... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Ethan Shah",
"role": "creative lead",
"task": "Revise the client onboarding brief around a teaser-first cut.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Cinder Atlas client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the s... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Cinder Atlas working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Cinder Atlas approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Cinder Atlas la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Cinder Atlas working brief",
"Cinder Atlas approval thread",
"Cinder Atlas launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0136 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Northbeam Studio",
"meeting_type": "creative review",
"meeting_date": "2026-04-24T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Ivy Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-04-24."
},
{
"speaker": "Liam Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a proof-first recap for the creative review workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Ivy Morris",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Northbeam Studio creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that lega... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0137 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Lattice Harbor",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Liam Walker",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Liam Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Elijah Morris",
"role": "stakeholder",
"timestamp": "00:21",
"... | {
"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making ... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Liam Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Liam Walker",
"role": "creative lead",
"task": "Revise the client onboarding brief around a tighter pilot package.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Lattice Harbor client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed tha... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Lattice Harbor working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Lattice Harbor approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Lattice Har... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Lattice Harbor working brief",
"Lattice Harbor approval thread",
"Lattice Harbor launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0138 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Signal Oak",
"meeting_type": "creative review",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Elijah Lopez",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Elijah Lopez",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Lucas Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a tighter pilot package for the creative review workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved whil... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Elijah Lopez",
"role": "creative lead",
"task": "Revise the creative review brief around a tighter pilot package.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"email_subject": "Signal Oak creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the so... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Signal Oak working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Signal Oak approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Signal Oak launch t... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Signal Oak working brief",
"Signal Oak approval thread",
"Signal Oak launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versus over... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0139 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Juniper Relay",
"meeting_type": "retrospective",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Miles Morris",
"r... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Miles Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Ivy Brooks",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a tighter pilot package for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the ... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Miles Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Miles Morris",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Juniper Relay retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two sta... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0140 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "First Mile Creative",
"meeting_type": "creative review",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ethan... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ethan Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Liam Morris",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a proof-first recap for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Ethan Morris",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Mia Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "First Mile Creative creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0141 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Harborline Works",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Elija... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Elijah Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Zoe Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a teaser-first cut for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the nex... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Elijah Chen",
"role": "creative lead",
"task": "Revise the client onboarding brief around a teaser-first cut.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Harborline Works client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0142 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Echoframe Media",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Liam Shah",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Liam Shah",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Ethan Walker",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I... | {
"executive_summary": "The team aligned on using a proof-first recap for the vendor sync workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next rev... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Liam Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Liam Shah",
"role": "creative lead",
"task": "Revise the vendor sync brief around a proof-first recap.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Ethan Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what ... | {
"email_subject": "Echoframe Media vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0143 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Cinder Atlas",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Nora Brooks",
"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Nora Brooks",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Sofia Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the n... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Nora Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Nora Brooks",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Cinder Atlas vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the appro... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Cinder Atlas working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Cinder Atlas approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Cinder Atlas la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Cinder Atlas working brief",
"Cinder Atlas approval thread",
"Cinder Atlas launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0144 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Juniper Relay",
"meeting_type": "creative review",
"meeting_date": "2026-04-22T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "L... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Lucas Patel",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Ethan Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Lucas Patel",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Juniper Relay creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0145 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "First Mile Creative",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-08T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Noah Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Sofia Morgan",
"role": "stakeholder",
"timestamp": "00:21",
"t... | {
"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making th... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Noah Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Noah Walker",
"role": "creative lead",
"task": "Revise the client onboarding brief around a tighter pilot package.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"email_subject": "First Mile Creative client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agree... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0146 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Northbeam Studio",
"meeting_type": "creative review",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Isla Sha... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Isla Shah",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Noah Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Isla Shah",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Northbeam Studio creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed th... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0147 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Harborline Works",
"meeting_type": "creative review",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ethan Ki... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ethan Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Isla Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Ethan Kim",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Harborline Works creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed th... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0148 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Tidal North Labs",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-08T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"na... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Ivy Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Sofia Morgan",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"executive_summary": "The team aligned on using a teaser-first cut for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the nex... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Ivy Morris",
"role": "creative lead",
"task": "Revise the client onboarding brief around a teaser-first cut.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Tidal North Labs client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0149 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Orbit Thread",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia Shah"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Mia Shah",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Ethan Brooks",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a teaser-first cut for the campaign planning workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the nex... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof an... | [
{
"owner": "Mia Shah",
"role": "creative lead",
"task": "Revise the campaign planning brief around a teaser-first cut.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Orbit Thread campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the a... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Orbit Thread working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Orbit Thread approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Orbit Thread la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Orbit Thread working brief",
"Orbit Thread approval thread",
"Orbit Thread launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0150 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Tidal North Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Miles Walker",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Miles Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Noah Walker",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a lightweight review draft for the retrospective workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next r... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Miles Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Miles Walker",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Tidal North Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that l... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0151 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Signal Oak",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-28T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Lucas Nguyen",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Lucas Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Isla Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"t... | {
"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next revi... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Lucas Nguyen",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Signal Oak client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Signal Oak working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Signal Oak approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Signal Oak launch t... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Signal Oak working brief",
"Signal Oak approval thread",
"Signal Oak launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versus over... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0152 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Echoframe Media",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ivy Walker",
"role"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Ivy Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Elijah Walker",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a teaser-first cut for the vendor sync workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Ivy Walker",
"role": "creative lead",
"task": "Revise the vendor sync brief around a teaser-first cut.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what... | {
"email_subject": "Echoframe Media vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0153 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Northbeam Studio",
"meeting_type": "creative review",
"meeting_date": "2026-05-15T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Elijah Morgan",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Liam Diaz",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a proof-first recap for the creative review workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while st... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pr... | [
{
"owner": "Elijah Morgan",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Northbeam Studio creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0154 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Orbit Thread",
"meeting_type": "retrospective",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ethan Kim",
"role"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Ethan Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Ivy Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I ag... | {
"executive_summary": "The team aligned on using a tighter pilot package for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pr... | [
{
"owner": "Ethan Kim",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Orbit Thread retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the appr... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Orbit Thread working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Orbit Thread approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Orbit Thread la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Orbit Thread working brief",
"Orbit Thread approval thread",
"Orbit Thread launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0155 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Harborline Works",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-01T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Zoe Ki... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Zoe Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Lucas Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I ag... | {
"executive_summary": "The team aligned on using a teaser-first cut for the vendor sync workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Zoe Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof and... | [
{
"owner": "Zoe Kim",
"role": "creative lead",
"task": "Revise the vendor sync brief around a teaser-first cut.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what pr... | {
"email_subject": "Harborline Works vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal languag... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0156 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Northbeam Studio",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-12T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ivy Ki... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ivy Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Mia Morris",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I agr... | {
"executive_summary": "The team aligned on using a tighter pilot package for the vendor sync workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Ivy Kim",
"role": "creative lead",
"task": "Revise the vendor sync brief around a tighter pilot package.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Ethan Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wha... | {
"email_subject": "Northbeam Studio vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stak... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0157 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Tidal North Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ava Walker",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Ava Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Liam Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a tighter pilot package for the retrospective workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while ... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ava Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Ava Walker",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Tidal North Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0158 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Juniper Relay",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ivy Mor... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Ivy Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Mia Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a tighter pilot package for the campaign planning workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next ... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Ivy Morris",
"role": "creative lead",
"task": "Revise the campaign planning brief around a tighter pilot package.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Juniper Relay campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0159 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Tidal North Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-05-05T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "No... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Nora Brooks",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Nora Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a tighter pilot package for the retrospective workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while ... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Nora Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Nora Brooks",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Ethan Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Tidal North Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0160 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Lattice Harbor",
"meeting_type": "creative review",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Zoe Lopez",... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Zoe Lopez",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Elijah Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making t... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Zoe Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Zoe Lopez",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"email_subject": "Lattice Harbor creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Lattice Harbor working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Lattice Harbor approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Lattice Har... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Lattice Harbor working brief",
"Lattice Harbor approval thread",
"Lattice Harbor launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0161 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Juniper Relay",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Zoe Morgan",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Zoe Morgan",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Jalen Morris",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"executive_summary": "The team aligned on using a lightweight review draft for the client onboarding workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Zoe Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Zoe Morgan",
"role": "creative lead",
"task": "Revise the client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable a... | {
"email_subject": "Juniper Relay client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0162 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "First Mile Creative",
"meeting_type": "creative review",
"meeting_date": "2026-05-15T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"nam... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Elijah Rivera",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Elijah Brooks",
"role": "stakeholder",
"timestamp": "00:21",
"... | {
"executive_summary": "The team aligned on using a tighter pilot package for the creative review workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved whil... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Elijah Rivera",
"role": "creative lead",
"task": "Revise the creative review brief around a tighter pilot package.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"email_subject": "First Mile Creative creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed th... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0163 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Echoframe Media",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-24T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Lucas... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Lucas Rivera",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-24."
},
{
"speaker": "Elijah Brooks",
"role": "stakeholder",
"timestamp": "00:21",
... | {
"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Lucas Rivera",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Echoframe Media client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0164 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Cinder Atlas",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Isla Sha... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Isla Shah",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Liam Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the ... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Isla Shah",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Cinder Atlas client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Cinder Atlas working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Cinder Atlas approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Cinder Atlas la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Cinder Atlas working brief",
"Cinder Atlas approval thread",
"Cinder Atlas launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0165 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Tidal North Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Noah Rivera",... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Noah Rivera",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Sofia Walker",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a tighter pilot package for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Noah Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Noah Rivera",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Tidal North Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0166 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Echoframe Media",
"meeting_type": "creative review",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ava Nguyen",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ava Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Elijah Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a tighter pilot package for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making th... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ava Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Ava Nguyen",
"role": "creative lead",
"task": "Revise the creative review brief around a tighter pilot package.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Echoframe Media creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Echoframe Media working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Echoframe Media approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Echoframe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Echoframe Media working brief",
"Echoframe Media approval thread",
"Echoframe Media launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast re... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0167 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Lattice Harbor",
"meeting_type": "retrospective",
"meeting_date": "2026-05-15T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mile... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Miles Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Jalen Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a teaser-first cut for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next ... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Miles Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Miles Nguyen",
"role": "creative lead",
"task": "Revise the retrospective brief around a teaser-first cut.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Jalen Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Lattice Harbor retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeho... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Lattice Harbor working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Lattice Harbor approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Lattice Har... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Lattice Harbor working brief",
"Lattice Harbor approval thread",
"Lattice Harbor launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0168 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Northbeam Studio",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Miles... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Miles Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Liam Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"t... | {
"executive_summary": "The team aligned on using a proof-first recap for the campaign planning workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next revi... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Miles Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Miles Nguyen",
"role": "creative lead",
"task": "Revise the campaign planning brief around a proof-first recap.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Mia Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Northbeam Studio campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0169 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Tidal North Labs",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Lucas Diaz",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Lucas Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Jalen Diaz",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I ... | {
"executive_summary": "The team aligned on using a tighter pilot package for the vendor sync workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while st... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Lucas Diaz",
"role": "creative lead",
"task": "Revise the vendor sync brief around a tighter pilot package.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Tidal North Labs vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the sour... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0170 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Juniper Relay",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia Morris",
"role": ... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Mia Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Jalen Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a proof-first recap for the vendor sync workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still ... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Mia Morris",
"role": "creative lead",
"task": "Revise the vendor sync brief around a proof-first recap.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Chen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what pr... | {
"email_subject": "Juniper Relay vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source foot... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0171 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Cinder Atlas",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-08T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ethan Nguyen",
"role":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Ethan Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Mia Morris",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Ethan Nguyen",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"email_subject": "Cinder Atlas vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the sourc... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Cinder Atlas working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Cinder Atlas approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Cinder Atlas la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Cinder Atlas working brief",
"Cinder Atlas approval thread",
"Cinder Atlas launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0172 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Tidal North Labs",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Noah Diaz",
"role"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Noah Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Elijah Morgan",
"role": "stakeholder",
"timestamp": "00:21",
"text": "... | {
"executive_summary": "The team aligned on using a proof-first recap for the vendor sync workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next r... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Noah Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Noah Diaz",
"role": "creative lead",
"task": "Revise the vendor sync brief around a proof-first recap.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what p... | {
"email_subject": "Tidal North Labs vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakehol... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0173 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Signal Oak",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Sofia Nguyen",
"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Sofia Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Nora Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a proof-first recap for the vendor sync workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next r... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Sofia Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Sofia Nguyen",
"role": "creative lead",
"task": "Revise the vendor sync brief around a proof-first recap.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what ... | {
"email_subject": "Signal Oak vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders s... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Signal Oak working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Signal Oak approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Signal Oak launch t... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Signal Oak working brief",
"Signal Oak approval thread",
"Signal Oak launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versus over... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0174 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Harborline Works",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia Morgan",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Mia Morgan",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Nora Chen",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the n... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Mia Morgan",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Harborline Works vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the a... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0175 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "First Mile Creative",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Zo... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Zoe Brooks",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Isla Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a lightweight review draft for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Zoe Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Zoe Brooks",
"role": "creative lead",
"task": "Revise the client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"email_subject": "First Mile Creative client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also ag... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "First Mile Creative working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "First Mile Creative approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "F... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"First Mile Creative working brief",
"First Mile Creative approval thread",
"First Mile Creative launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0176 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Orbit Thread",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ethan Rivera",
"role":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Ethan Rivera",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Isla Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I ... | {
"executive_summary": "The team aligned on using a teaser-first cut for the vendor sync workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Ethan Rivera",
"role": "creative lead",
"task": "Revise the vendor sync brief around a teaser-first cut.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Orbit Thread vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Orbit Thread working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Orbit Thread approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Orbit Thread la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Orbit Thread working brief",
"Orbit Thread approval thread",
"Orbit Thread launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0177 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Orbit Thread",
"meeting_type": "retrospective",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ethan Nguyen",
"ro... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Ethan Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Nora Morgan",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a proof-first recap for the retrospective workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while stil... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Ethan Nguyen",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Orbit Thread retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source f... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Orbit Thread working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Orbit Thread approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Orbit Thread la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Orbit Thread working brief",
"Orbit Thread approval thread",
"Orbit Thread launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0178 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Glowforge Labs",
"meeting_type": "creative review",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ivy Kim",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Ivy Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Elijah Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making t... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Ivy Kim",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Ethan Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Glowforge Labs creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Glowforge Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Glowforge Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Glowforge L... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Glowforge Labs working brief",
"Glowforge Labs approval thread",
"Glowforge Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0179 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Orbit Thread",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-01T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Elijah Rivera",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Nora Brooks",
"role": "stakeholder",
"timestamp": "00:21",
"... | {
"executive_summary": "The team aligned on using a lightweight review draft for the campaign planning workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team w... | [
{
"owner": "Elijah Rivera",
"role": "creative lead",
"task": "Revise the campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable... | {
"email_subject": "Orbit Thread campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed th... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Orbit Thread working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Orbit Thread approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Orbit Thread la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Orbit Thread working brief",
"Orbit Thread approval thread",
"Orbit Thread launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0180 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Tidal North Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-05-08T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Nora Morris"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Nora Morris",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Ava Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a tighter pilot package for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Nora Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Nora Morris",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Tidal North Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0181 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Harborline Works",
"meeting_type": "creative review",
"meeting_date": "2026-05-08T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Jalen Pa... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Jalen Patel",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-08."
},
{
"speaker": "Zoe Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making t... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Jalen Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Jalen Patel",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"email_subject": "Harborline Works creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed th... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0182 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Juniper Relay",
"meeting_type": "creative review",
"meeting_date": "2026-04-22T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "E... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Ethan Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Noah Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text":... | {
"executive_summary": "The team aligned on using a teaser-first cut for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next ... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Ethan Diaz",
"role": "creative lead",
"task": "Revise the creative review brief around a teaser-first cut.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Juniper Relay creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the appr... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0183 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Orbit Thread",
"meeting_type": "creative review",
"meeting_date": "2026-05-12T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name": "Noah Walker"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Noah Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Noah Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"text... | {
"executive_summary": "The team aligned on using a teaser-first cut for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next ... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Noah Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Noah Walker",
"role": "creative lead",
"task": "Revise the creative review brief around a teaser-first cut.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Orbit Thread creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the appro... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Orbit Thread working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Orbit Thread approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Orbit Thread la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a teaser-first cut as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty"... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Orbit Thread working brief",
"Orbit Thread approval thread",
"Orbit Thread launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0184 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Cinder Atlas",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-12T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Nora Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Elijah Patel",
"role": "stakeholder",
"timestamp": "00:21",
"t... | {
"executive_summary": "The team aligned on using a lightweight review draft for the client onboarding workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still maki... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Nora Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Nora Nguyen",
"role": "creative lead",
"task": "Revise the client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable ... | {
"email_subject": "Cinder Atlas client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed th... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Cinder Atlas working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Cinder Atlas approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Cinder Atlas la... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Cinder Atlas working brief",
"Cinder Atlas approval thread",
"Cinder Atlas launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versu... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0185 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Velora Motion",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-22T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Jalen Ng... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Jalen Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-22."
},
{
"speaker": "Elijah Diaz",
"role": "stakeholder",
"timestamp": "00:21",
"t... | {
"executive_summary": "The team aligned on using a proof-first recap for the campaign planning workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Jalen Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Jalen Nguyen",
"role": "creative lead",
"task": "Revise the campaign planning brief around a proof-first recap.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"email_subject": "Velora Motion campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Velora Motion working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Velora Motion approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Velora Motion... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Velora Motion working brief",
"Velora Motion approval thread",
"Velora Motion launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0186 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Northbeam Studio",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-28T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"na... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Jalen Patel",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Jalen Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"t... | {
"executive_summary": "The team aligned on using a tighter pilot package for the campaign planning workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved wh... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Jalen Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Jalen Patel",
"role": "creative lead",
"task": "Revise the campaign planning brief around a tighter pilot package.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"email_subject": "Northbeam Studio campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0187 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Juniper Relay",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-01T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Lucas Sha... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Lucas Shah",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Lucas Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a tighter pilot package for the vendor sync workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Lucas Shah",
"role": "creative lead",
"task": "Revise the vendor sync brief around a tighter pilot package.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Juniper Relay vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approve... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Juniper Relay working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Juniper Relay approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Juniper Relay... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Juniper Relay working brief",
"Juniper Relay approval thread",
"Juniper Relay launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0188 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Harborline Works",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-28T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ava Diaz",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ava Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Jalen Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text"... | {
"executive_summary": "The team aligned on using a lightweight review draft for the campaign planning workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still maki... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ava Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Ava Diaz",
"role": "creative lead",
"task": "Revise the campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"email_subject": "Harborline Works campaign planning: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agree... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0189 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Signal Oak",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia Walker"... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Mia Walker",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Ethan Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the ne... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Mia Walker",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Signal Oak client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the ap... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Signal Oak working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Signal Oak approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Signal Oak launch t... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Signal Oak working brief",
"Signal Oak approval thread",
"Signal Oak launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versus over... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0190 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Tidal North Labs",
"meeting_type": "creative review",
"meeting_date": "2026-04-28T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ava Brooks",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Ava Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I... | {
"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ava Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Ava Brooks",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"email_subject": "Tidal North Labs creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed th... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0191 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Velora Motion",
"meeting_type": "retrospective",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Isla Chen",
"role... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Isla Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Jalen Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a proof-first recap for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next r... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Isla Chen",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wha... | {
"email_subject": "Velora Motion retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approve... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Velora Motion working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Velora Motion approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Velora Motion... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Velora Motion working brief",
"Velora Motion approval thread",
"Velora Motion launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0192 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Harborline Works",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-28T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Mia Kim",
"role": ... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Mia Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Ethan Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a tighter pilot package for the vendor sync workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Mia Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Mia Kim",
"role": "creative lead",
"task": "Revise the vendor sync brief around a tighter pilot package.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what... | {
"email_subject": "Harborline Works vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the appr... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0193 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Signal Oak",
"meeting_type": "retrospective",
"meeting_date": "2026-05-05T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Lucas Kim",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Lucas Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Noah Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a lightweight review draft for the retrospective workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Lucas Kim",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Signal Oak retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the app... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Signal Oak working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Signal Oak approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Signal Oak launch t... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Signal Oak working brief",
"Signal Oak approval thread",
"Signal Oak launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versus over... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0194 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Tidal North Labs",
"meeting_type": "creative review",
"meeting_date": "2026-05-15T00:00:00",
"channel": "conference room review",
"objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.",
"participants": [
{
"name":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Zoe Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Ivy Shah",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I ... | {
"executive_summary": "The team aligned on using a tighter pilot package for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making th... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Zoe Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Zoe Diaz",
"role": "creative lead",
"task": "Revise the creative review brief around a tighter pilot package.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Tidal North Labs creative review: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that ... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0195 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Signal Oak",
"meeting_type": "retrospective",
"meeting_date": "2026-05-15T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ava Kim",
"r... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ava Kim",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Nora Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a lightweight review draft for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making t... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ava Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Ava Kim",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Signal Oak retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two sta... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Signal Oak working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Signal Oak approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Signal Oak launch t... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Signal Oak working brief",
"Signal Oak approval thread",
"Signal Oak launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap versus over... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0196 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Harborline Works",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Luca... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Lucas Nguyen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Sofia Morris",
"role": "stakeholder",
"timestamp": "00:21",
"... | {
"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved wh... | [
{
"decision": "Use a tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Lucas Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Lucas Nguyen",
"role": "creative lead",
"task": "Revise the client onboarding brief around a tighter pilot package.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable a... | {
"email_subject": "Harborline Works client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed t... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Harborline Works working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Harborline Works approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Harborl... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a tighter pilot package as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certa... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Harborline Works working brief",
"Harborline Works approval thread",
"Harborline Works launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0197 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Tidal North Labs",
"meeting_type": "retrospective",
"meeting_date": "2026-04-28T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ivy Chen",
... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ivy Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Elijah Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"executive_summary": "The team aligned on using a proof-first recap for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof a... | [
{
"owner": "Ivy Chen",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what pr... | {
"email_subject": "Tidal North Labs retrospective: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stak... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Tidal North Labs working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Tidal North Labs approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Tidal N... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Tidal North Labs working brief",
"Tidal North Labs approval thread",
"Tidal North Labs launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Hard rows for meeting summary, decisions, and action capture 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",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change",
"stress-case"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope",
"multi-constraint-pressure"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was.",
"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 summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
... |
zarn_meeting_to_actions_train_0198 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Velora Motion",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-24T00:00:00",
"channel": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.",
"participants": [
{
"name": "Jalen D... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Jalen Diaz",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-24."
},
{
"speaker": "Jalen Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next revi... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Jalen Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Jalen Diaz",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Jalen Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Velora Motion client onboarding: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that leg... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Velora Motion working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Velora Motion approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Velora Motion... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a proof-first recap as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising certainty... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Velora Motion working brief",
"Velora Motion approval thread",
"Velora Motion launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast recap ve... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Easy rows for meeting summary, decisions, and action capture still require grounded execution, but the main blocker is explicit and the gold path is comparatively direct. | [
"high-context",
"constraint-dense",
"difficulty-easy",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
zarn_meeting_to_actions_train_0199 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Northbeam Studio",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-01T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ava Chen",
"role":... | [
{
"slot": 1,
"topic": "What the first deliverable should actually cover",
"goal": "Reduce scope while preserving the core proof."
},
{
"slot": 2,
"topic": "What is still unresolved",
"goal": "Keep two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ava Chen",
"role": "creative lead",
"timestamp": "00:00",
"text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Lucas Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ava Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Ava Chen",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Northbeam Studio vendor sync: scoped recap and next review step",
"followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two s... | [
"Does the approval group want one review slot or two options?",
"Which proof beat is non-negotiable in the first scoped pass?",
"What would force the project back into broader scope before the first review?"
] | {
"primary_metric": "action_item_f1",
"secondary_metrics": [
"summary_faithfulness",
"decision_recall",
"owner_accuracy",
"followup_consistency",
"blocker_preservation"
],
"automatic_failures": [
"Invents consensus on unresolved blockers",
"Drops owner or due-date information",
"... | {
"documents": [
{
"name": "Northbeam Studio working brief",
"note": "Current scope is wider than the review team wants."
},
{
"name": "Northbeam Studio approval thread",
"note": "Stakeholders want fewer rounds and lower-friction recap language."
},
{
"name": "Northbe... | [
{
"tradeoff": "narrow first pass versus broader stakeholder coverage",
"why_it_mattered": "A broader first deliverable would create another slow feedback cycle.",
"resolved_direction": "Use a lightweight review draft as the first deliverable."
},
{
"tradeoff": "fast recap versus overpromising ce... | [
"A recap that sounds too polished could hide the blocker and trigger pushback.",
"If owners are omitted, the scoped-first decision may get reinterpreted as vague planning.",
"If the next step sounds too broad, stakeholders may delay instead of replying quickly."
] | [
"Summary preserves both the scoped-first decision and the blocker.",
"Action items include owners, dependencies, and due dates.",
"The follow-up package sounds aligned with the tone concerns raised in the meeting."
] | {
"modality": "meeting-transcript-plus-preread",
"source_artifacts": [
"Northbeam Studio working brief",
"Northbeam Studio approval thread",
"Northbeam Studio launch tracker"
],
"speaker_count": 4,
"decision_pressure_points": [
"narrow first pass versus broader stakeholder coverage",
"fast... | [
{
"label": "executive recap variant",
"rationale": "Acceptable when the summary compresses more aggressively but keeps the same blocker and next-step fidelity.",
"outputs": {
"summary_style": "shorter executive recap",
"followup_tone": "more concise and stakeholder-friendly"
}
},
{
... | [
{
"label": "fake consensus",
"why_bad": "Claims the team fully resolved the blocker when the transcript shows caution or deferral.",
"conflicting_rule": "The summary should preserve both decisions and unresolved blockers."
},
{
"label": "action drift",
"why_bad": "Drops owners or due dates a... | Medium rows for meeting summary, decisions, and action capture mix multiple constraints or artifact dependencies, so a strong answer has to stay coordinated rather than merely plausible. | [
"high-context",
"constraint-dense",
"difficulty-medium",
"decision-tension",
"blocker-preservation",
"owner-date-extraction",
"tone-sensitive-followup",
"scope-change"
] | [
"mixed-consensus",
"owner-and-deadline-coupling",
"soft-pushback-in-transcript",
"deferred-scope"
] | [
"Polishes away unresolved blockers in the summary.",
"Drops owners, due dates, or dependencies from action items.",
"Writes a follow-up that sounds more resolved than the meeting actually was."
] | {
"status": "starter-train-ready",
"gold_candidate": false,
"recommended_reviewers": 1,
"adjudication_mode": "single-review-spot-check",
"required_checks": [
"The summary preserves both the decision and what is still unresolved.",
"Action items are attributable, dated, and dependency-aware.",
"Fol... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.