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_0000 | train | easy | 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-04-28T00: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": "Miles 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-04-28."
},
{
"speaker": "Lucas Walker",
"role": "stakeholder",
"timestamp": "00:21",
"... | {
"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": "Miles Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Miles Walker",
"role": "creative lead",
"task": "Revise the client onboarding brief around a teaser-first cut.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"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... | 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_0001 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Signal Oak",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-28T00: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 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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Mia 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-28."
},
{
"speaker": "Ivy Morris",
"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": "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 campaign planning brief around a tighter pilot package.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Signal Oak 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 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": "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... | 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_0002 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Juniper Relay",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-05T00: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": "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 campaign planning. Right now the draft is too broad for the review window on 2026-05-05."
},
{
"speaker": "Lucas Diaz",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"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 Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Elijah Lopez",
"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": "Ivy Walker",
"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... | 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_0003 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Echoframe Media",
"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": "Zoe 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": "Zoe Patel",
"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": "Noah Diaz",
"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 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": "Zoe Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof a... | [
{
"owner": "Zoe Patel",
"role": "creative lead",
"task": "Revise the vendor sync brief around a teaser-first cut.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Rivera",
"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 two stakeholde... | [
"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... | 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_0004 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"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": "Ava Nguy... | [
{
"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-05-15."
},
{
"speaker": "Mia 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 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": "Ava Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Ava Nguyen",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Mia Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"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 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": "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_0005 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Harborline Works",
"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": "Lucas Di... | [
{
"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 creative review. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Isla Nguyen",
"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 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": "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 creative review brief around a tighter pilot package.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"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... | 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_0006 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Cinder Atlas",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-12T00: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 Pat... | [
{
"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 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-05-12."
},
{
"speaker": "Nora 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 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": "Miles Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Miles Patel",
"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": "Jalen Morris",
"role": "editor",
"task": "Prepare the first scoped deliverabl... | {
"email_subject": "Cinder Atlas 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": "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_0007 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Lattice Harbor",
"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": "Zoe 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 the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Zoe 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": "Miles Nguyen",
"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 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 revi... | [
{
"decision": "Use a teaser-first cut 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 proof an... | [
{
"owner": "Zoe Diaz",
"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": "Jalen Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what p... | {
"email_subject": "Lattice Harbor 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 the approver wa... | [
"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... | 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_0008 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Glowforge Labs",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-28T00: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": "Elijah... | [
{
"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 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-04-28."
},
{
"speaker": "Ethan Patel",
"role": "stakeholder",
"timestamp": "00:21",
"... | {
"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": "Elijah Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team w... | [
{
"owner": "Elijah Morris",
"role": "creative lead",
"task": "Revise the client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Mia Morris",
"role": "editor",
"task": "Prepare the first scoped deliverabl... | {
"email_subject": "Glowforge Labs 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 ... | [
"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_0009 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Glowforge Labs",
"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": "Liam Walke... | [
{
"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 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-08."
},
{
"speaker": "Miles Morris",
"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 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": "Liam Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Liam Walker",
"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": "Jalen Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"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... | 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_0010 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Glowforge Labs",
"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": "Nora Morga... | [
{
"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": "Nora 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": "Miles Nguyen",
"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 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": "Nora Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Nora 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": "Jalen Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Glowforge Labs 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 ... | [
"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 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": [
"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_0011 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Harborline Works",
"meeting_type": "retrospective",
"meeting_date": "2026-05-05T00: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": "Nora 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": "Nora 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": "Elijah 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 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": "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 retrospective brief around a lightweight review draft.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Jalen Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Harborline Works 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 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 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_0012 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Northbeam Studio",
"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": "Etha... | [
{
"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 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-01."
},
{
"speaker": "Jalen Shah",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"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": "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 campaign planning brief around a proof-first recap.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"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_0013 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "First Mile Creative",
"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": "Et... | [
{
"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 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-01."
},
{
"speaker": "Miles Rivera",
"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": "Ethan Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Ethan Patel",
"role": "creative lead",
"task": "Revise the client onboarding brief around a tighter pilot package.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Patel",
"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_0014 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Orbit Thread",
"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": "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 source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Sofia 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": "Noah Brooks",
"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 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": "Sofia Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Sofia Nguyen",
"role": "creative lead",
"task": "Revise the client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverab... | {
"email_subject": "Orbit Thread 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": "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_0015 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Lattice Harbor",
"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": "Ava Ngu... | [
{
"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": "Ava 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": "Liam Lopez",
"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": "Ava Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Ava Nguyen",
"role": "creative lead",
"task": "Revise the client onboarding brief around a teaser-first cut.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Lattice Harbor 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": "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... | 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_0016 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Velora Motion",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-22T00: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 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": "Liam 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-04-22."
},
{
"speaker": "Nora Morris",
"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 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 Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Liam Rivera",
"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": "Ethan Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wha... | {
"email_subject": "Velora Motion 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 wa... | [
"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... | 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_0017 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Northbeam Studio",
"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": "Is... | [
{
"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 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-05-01."
},
{
"speaker": "Lucas Morgan",
"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 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 ea... | [
{
"decision": "Use a teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Isla Rivera",
"role": "creative lead",
"task": "Revise the retrospective brief around a teaser-first cut.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Northbeam Studio 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 legal lan... | [
"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 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": [
"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_0018 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Echoframe Media",
"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": "Ava 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-15."
},
{
"speaker": "Sofia Morgan",
"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": "Ava Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Ava Lopez",
"role": "creative lead",
"task": "Revise the creative review brief around a lightweight review draft.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Ethan Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"email_subject": "Echoframe Media 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 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": "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_0019 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Signal Oak",
"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": "Isla Morgan",
"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": "Isla Morgan",
"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": "Jalen Morgan",
"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 source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved whi... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Isla Morgan",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and ... | {
"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 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": "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_0020 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Lattice Harbor",
"meeting_type": "retrospective",
"meeting_date": "2026-05-15T00: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 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": "Noah Diaz",
"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 Morgan",
"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": "Noah Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pr... | [
{
"owner": "Noah Diaz",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Lopez",
"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 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 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": "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_0021 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Signal Oak",
"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": "Ivy 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 the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Ivy 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": "Elijah 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 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 teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ivy Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Ivy Brooks",
"role": "creative lead",
"task": "Revise the retrospective brief around a teaser-first cut.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wha... | {
"email_subject": "Signal Oak 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 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": "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 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": [
"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_0022 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Lattice Harbor",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-24T00: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": "Lucas 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": "Lucas Lopez",
"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": "Noah Patel",
"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 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 Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Lucas Lopez",
"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 Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Lattice Harbor 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 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": "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 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": [
"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_0023 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"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": "Isla... | [
{
"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 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-05-15."
},
{
"speaker": "Nora Nguyen",
"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 source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved whi... | [
{
"decision": "Use a lightweight review draft as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Isla Rivera",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Jalen Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable an... | {
"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... | 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_0024 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Orbit Thread",
"meeting_type": "retrospective",
"meeting_date": "2026-04-28T00: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 Walker",
"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 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": "Lucas 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 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 teaser-first cut as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Ethan Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Ethan Walker",
"role": "creative lead",
"task": "Revise the retrospective brief around a teaser-first cut.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Orbit Thread 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 source fo... | [
"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_0025 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Harborline Works",
"meeting_type": "creative review",
"meeting_date": "2026-05-05T00: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": "Jalen 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": "Jalen 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": "Elijah Patel",
"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": "Jalen Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pr... | [
{
"owner": "Jalen Kim",
"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": "Mia Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"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_0026 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Orbit Thread",
"meeting_type": "retrospective",
"meeting_date": "2026-04-24T00: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": "Zoe Sh... | [
{
"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 Shah",
"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-24."
},
{
"speaker": "Liam Morgan",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I... | {
"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": "Zoe Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Zoe Shah",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"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... | 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_0027 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Juniper Relay",
"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": [
{
"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": "Miles Lopez",
"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 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 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 Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Miles Lopez",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Juniper Relay 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... | [
"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... | 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_0028 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Cinder Atlas",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-15T00: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": "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 campaign planning. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Noah Patel",
"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 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": "Liam Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Liam Morris",
"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": "Jalen Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Cinder Atlas 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 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": "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... | 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_0029 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Lattice Harbor",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-28T00: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 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": "Lucas 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-28."
},
{
"speaker": "Nora Nguyen",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"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 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 vendor sync brief around a tighter pilot package.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Lattice Harbor 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 approv... | [
"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_0030 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Orbit Thread",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-15T00: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": "Nora River... | [
{
"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 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": "Ivy Chen",
"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 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 revi... | [
{
"decision": "Use a teaser-first cut 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 proof... | [
{
"owner": "Nora Rivera",
"role": "creative lead",
"task": "Revise the vendor sync brief around a teaser-first cut.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wha... | {
"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 the approver want... | [
"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_0031 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Glowforge Labs",
"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": "Lucas 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": "Lucas 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-12."
},
{
"speaker": "Mia Kim",
"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": "Lucas Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Lucas Morris",
"role": "creative lead",
"task": "Revise the campaign planning brief around a tighter pilot package.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable a... | {
"email_subject": "Glowforge Labs 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 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": "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 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": [
"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_0032 | train | hard | 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": "Slack huddle",
"objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.",
"participants": [
{
"name": "Elijah 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": "Elijah 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-28."
},
{
"speaker": "Liam Diaz",
"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": "Elijah Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Elijah Nguyen",
"role": "creative lead",
"task": "Revise the vendor sync 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 note ... | {
"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_0033 | 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-04-28T00: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 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 source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Elijah 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-28."
},
{
"speaker": "Miles Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"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 Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pr... | [
{
"owner": "Elijah Nguyen",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"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_0034 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Juniper Relay",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-28T00: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": "Zoe Morg... | [
{
"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 Morgan",
"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": "Noah Brooks",
"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": "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 campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable a... | {
"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_0035 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Cinder Atlas",
"meeting_type": "retrospective",
"meeting_date": "2026-05-05T00: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": "Isla 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 the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Isla Patel",
"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": "Liam 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 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": "Isla Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Isla Patel",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Cinder Atlas 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 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": "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_0036 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Echoframe Media",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-15T00: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": "Noah 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": "Noah 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-15."
},
{
"speaker": "Mia Chen",
"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": "Noah Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Noah Morris",
"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": "Noah Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Echoframe Media 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 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 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... | 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_0037 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Cinder Atlas",
"meeting_type": "retrospective",
"meeting_date": "2026-04-24T00: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 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": "Ivy 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-04-24."
},
{
"speaker": "Nora 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 Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Ivy Morris",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Cinder Atlas 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 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": "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_0038 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Harborline Works",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-22T00: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 Lopez",
"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": "Noah Lopez",
"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": "Ethan Shah",
"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 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": "Noah Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Noah Lopez",
"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": "Ivy Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"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 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 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_0039 | train | easy | 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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Ivy Lopez",
"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 Walker",
"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 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": "Ivy Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof a... | [
{
"owner": "Ivy Lopez",
"role": "creative lead",
"task": "Revise the client onboarding brief around a teaser-first cut.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Juniper Relay 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 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": "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... | 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_0040 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Signal Oak",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-28T00: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": "Mia 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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"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-04-28."
},
{
"speaker": "Ava Walker",
"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 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 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 teaser-first cut.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Walker",
"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 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 stakeholders 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": "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 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": [
"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_0041 | 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-01T00: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": "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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Elijah 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-01."
},
{
"speaker": "Ethan Kim",
"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": "Elijah Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pr... | [
{
"owner": "Elijah Walker",
"role": "creative lead",
"task": "Revise the vendor sync brief around a proof-first recap.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what... | {
"email_subject": "Orbit Thread 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... | [
"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... | 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_0042 | train | easy | 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-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": "Noah 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": "Noah 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-04-22."
},
{
"speaker": "Noah Brooks",
"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 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 e... | [
{
"decision": "Use a proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Noah Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Noah Morris",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Rivera",
"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 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 legal la... | [
"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... | 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_0043 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Signal Oak",
"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": "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 the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"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-01."
},
{
"speaker": "Ava Shah",
"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": "Ethan Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Ethan Rivera",
"role": "creative lead",
"task": "Revise the vendor sync brief around a tighter pilot package.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Signal Oak 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 source foo... | [
"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... | 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_0044 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Echoframe Media",
"meeting_type": "retrospective",
"meeting_date": "2026-04-28T00: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 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 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-04-28."
},
{
"speaker": "Zoe Patel",
"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-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Echoframe Media 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 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": "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... | 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_0045 | 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-15T00: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": "Liam 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": "Isla Lopez",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"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": "Liam Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Liam Morgan",
"role": "creative lead",
"task": "Revise the client onboarding brief around a tighter pilot package.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Cinder Atlas 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": "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 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": [
"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_0046 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Cinder Atlas",
"meeting_type": "creative review",
"meeting_date": "2026-04-24T00: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 Chen",
"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": "Ivy 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-04-24."
},
{
"speaker": "Lucas 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 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": "Ivy Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Ivy Chen",
"role": "creative lead",
"task": "Revise the creative review brief around a tighter pilot package.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Chen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Cinder Atlas 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 ... | [
"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 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": [
"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_0047 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "First Mile Creative",
"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": "Lucas 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 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 retrospective. Right now the draft is too broad for the review window on 2026-05-15."
},
{
"speaker": "Miles Lopez",
"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": "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 retrospective brief around a teaser-first cut.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "First Mile Creative 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 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": "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... | 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_0048 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Lattice Harbor",
"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": "Isla 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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Isla Morgan",
"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": "Miles 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 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 tighter pilot package as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Isla Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants ... | [
{
"owner": "Isla Morgan",
"role": "creative lead",
"task": "Revise the retrospective brief around a tighter pilot package.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Jalen Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Lattice Harbor 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 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": "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... | 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_0049 | train | medium | 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-12T00: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": "Mia Kim",
"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": "Isla Morgan",
"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 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": "Mia Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Mia Kim",
"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": "Ivy Patel",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"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... | 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_0050 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Velora Motion",
"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": "Jalen 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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Jalen 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": "Miles Shah",
"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 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": "Jalen Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Jalen Morgan",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"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 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": "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_0051 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Noah 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-08."
},
{
"speaker": "Sofia Morris",
"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 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": "Noah Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Noah Morgan",
"role": "creative lead",
"task": "Revise the client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Mia Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable a... | {
"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... | 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_0052 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Velora Motion",
"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": "Mia 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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Mia 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-04-22."
},
{
"speaker": "Liam 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 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 Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Mia Lopez",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Mia Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what pr... | {
"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 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": "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... | 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_0053 | train | hard | 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": "Google Meet",
"objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.",
"participants": [
{
"name": "Jalen ... | [
{
"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 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-04-28."
},
{
"speaker": "Noah Patel",
"role": "stakeholder",
"timestamp": "00:21",
"te... | {
"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": "Jalen Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Jalen Rivera",
"role": "creative lead",
"task": "Revise the campaign planning brief around a teaser-first cut.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Jalen Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Echoframe Media 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 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": "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_0054 | 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-05-12T00: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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Lucas 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-12."
},
{
"speaker": "Jalen Kim",
"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 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": "Lucas Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Lucas Chen",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Jalen Patel",
"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 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 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 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... | 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_0055 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Signal Oak",
"meeting_type": "retrospective",
"meeting_date": "2026-04-24T00:00:00",
"channel": "Zoom",
"objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.",
"participants": [
{
"name": "Ava 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 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 retrospective. Right now the draft is too broad for the review window on 2026-04-24."
},
{
"speaker": "Mia Kim",
"role": "stakeholder",
"timestamp": "00:21",
"text": "I a... | {
"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": "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 retrospective brief around a tighter pilot package.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Noah Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Signal Oak 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 stakeh... | [
"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... | 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_0056 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Cinder Atlas",
"meeting_type": "retrospective",
"meeting_date": "2026-05-15T00: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": "Nora 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": "Nora 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-15."
},
{
"speaker": "Ivy 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 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": "Nora Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Nora Lopez",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Cinder Atlas 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": "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_0057 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Signal Oak",
"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": "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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Liam 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-08."
},
{
"speaker": "Sofia Lopez",
"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": "Liam Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pr... | [
{
"owner": "Liam Shah",
"role": "creative lead",
"task": "Revise the campaign planning brief around a tighter pilot package.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"email_subject": "Signal Oak 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 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": "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_0058 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Signal Oak",
"meeting_type": "campaign planning",
"meeting_date": "2026-04-24T00: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": "Lucas 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": "Lucas 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-24."
},
{
"speaker": "Noah Kim",
"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": "Lucas Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Lucas Patel",
"role": "creative lead",
"task": "Revise the campaign planning brief around a proof-first recap.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Chen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Signal Oak 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 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": "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_0059 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Orbit Thread",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-05T00: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 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": "Zoe 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-05."
},
{
"speaker": "Isla Morgan",
"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 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": "Zoe Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Zoe Walker",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"email_subject": "Orbit Thread 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": "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_0060 | train | easy | 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-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": "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 the approver wants fewer review rounds visible instead of glossing over it."
},
{
"... | [
{
"speaker": "Miles 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": "Mia Shah",
"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 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 revi... | [
{
"decision": "Use a teaser-first cut 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 wants proo... | [
{
"owner": "Miles Walker",
"role": "creative lead",
"task": "Revise the vendor sync brief around a teaser-first cut.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Diaz",
"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 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 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": "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_0061 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Harborline Works",
"meeting_type": "retrospective",
"meeting_date": "2026-04-24T00: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": "El... | [
{
"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 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-24."
},
{
"speaker": "Miles Walker",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"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 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 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 retrospective brief around a tighter pilot package.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Harborline Works 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 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": "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_0062 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Signal Oak",
"meeting_type": "client onboarding",
"meeting_date": "2026-05-08T00: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": "Ivy 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 two stakeholders still disagree on scope 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": "Ivy 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": "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 proof-first recap.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Morris",
"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 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": "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_0063 | 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-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": "Lucas 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": "Lucas 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-05."
},
{
"speaker": "Miles 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 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": "Lucas Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Lucas Walker",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Orbit Thread 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 la... | [
"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_0064 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Harborline Works",
"meeting_type": "creative review",
"meeting_date": "2026-04-22T00: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": "Isla 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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Isla 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": "Liam Morris",
"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": "Isla Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Isla Diaz",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Harborline Works 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": "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 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": [
"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_0065 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Echoframe Media",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-24T00: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": "Ava 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 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 client onboarding. Right now the draft is too broad for the review window on 2026-04-24."
},
{
"speaker": "Jalen Walker",
"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 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 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 client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Liam Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable ... | {
"email_subject": "Echoframe Media 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... | [
"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... | 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_0066 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Lattice Harbor",
"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": "Sofia 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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Sofia 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-04-28."
},
{
"speaker": "Sofia Walker",
"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 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": "Sofia Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Sofia Walker",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Rivera",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Lattice Harbor 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 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": "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_0067 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Lattice Harbor",
"meeting_type": "creative review",
"meeting_date": "2026-05-15T00: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": "Zoe 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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Zoe 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-05-15."
},
{
"speaker": "Zoe Walker",
"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 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 teaser-first cut 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 wants proof ... | [
{
"owner": "Zoe Brooks",
"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": "Lucas Chen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"email_subject": "Lattice Harbor 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 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": "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... | 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_0068 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Juniper Relay",
"meeting_type": "creative review",
"meeting_date": "2026-05-08T00: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 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": "Ivy 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-08."
},
{
"speaker": "Zoe Brooks",
"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": "Ivy Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Ivy Rivera",
"role": "creative lead",
"task": "Revise the creative review brief around a teaser-first cut.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wh... | {
"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_0069 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Tidal North Labs",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-24T00: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": "Elijah 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": "Elijah 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-04-24."
},
{
"speaker": "Ivy Rivera",
"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 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 proof-first recap as the first deliverable.",
"reason": "It shortens the review burden and makes feedback easier to collect.",
"owner": "Elijah Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Elijah Shah",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and n... | {
"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... | 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_0070 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Orbit Thread",
"meeting_type": "vendor sync",
"meeting_date": "2026-04-22T00: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": "Noah Lopez",
"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": "Noah Lopez",
"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": "Liam Diaz",
"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 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": "Noah Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants p... | [
{
"owner": "Noah Lopez",
"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": "Lucas Shah",
"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 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 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": "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_0071 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Orbit Thread",
"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": "Isla Bro... | [
{
"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 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-28."
},
{
"speaker": "Lucas Rivera",
"role": "stakeholder",
"timestamp": "00:21",
"t... | {
"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": "Isla Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Isla Brooks",
"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": "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 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": "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_0072 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Velora Motion",
"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": "Ivy Lop... | [
{
"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 Lopez",
"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": "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 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": "Ivy Lopez"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pr... | [
{
"owner": "Ivy Lopez",
"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": "Noah Morris",
"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 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": "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 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": [
"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_0073 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Cinder Atlas",
"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": "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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Nora 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-05-08."
},
{
"speaker": "Sofia Brooks",
"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 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": "Nora Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Nora Brooks",
"role": "creative lead",
"task": "Revise the creative review 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 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 la... | [
"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... | 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_0074 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Glowforge Labs",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-08T00: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": "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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Noah Patel",
"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": "Noah Walker",
"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 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 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 vendor sync brief around a tighter pilot package.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Glowforge 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 legal lang... | [
"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 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": [
"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_0075 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "First Mile Creative",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-08T00: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": "Ethan 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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Ethan 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-08."
},
{
"speaker": "Lucas 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 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 tighter pilot package 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 p... | [
{
"owner": "Ethan Diaz",
"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 Diaz",
"role": "editor",
"task": "Prepare the first scoped deliverable and note wha... | {
"email_subject": "First Mile Creative 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 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": "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_0076 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Lattice Harbor",
"meeting_type": "creative review",
"meeting_date": "2026-04-24T00: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": "Sofia 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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Sofia 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-04-24."
},
{
"speaker": "Jalen Kim",
"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": "Sofia Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Sofia Shah",
"role": "creative lead",
"task": "Revise the creative review brief around a proof-first recap.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Elijah Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Lattice Harbor 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 ... | [
"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 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": [
"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_0077 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Tidal North Labs",
"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": "Ivy B... | [
{
"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 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-05-15."
},
{
"speaker": "Noah Walker",
"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 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": "Ivy Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Ivy Brooks",
"role": "creative lead",
"task": "Revise the campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Chen",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"email_subject": "Tidal North Labs 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": "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... | 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_0078 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Orbit Thread",
"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": "Nora Morr... | [
{
"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 client onboarding. Right now the draft is too broad for the review window on 2026-05-01."
},
{
"speaker": "Liam Morgan",
"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": "Nora Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Nora Morris",
"role": "creative lead",
"task": "Revise the client onboarding brief around a proof-first recap.",
"due_date": "2026-04-20T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Orbit Thread 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 ... | [
"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_0079 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Cinder Atlas",
"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": "Lucas 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 the source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Lucas 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": "Isla 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": "Lucas Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Lucas Walker",
"role": "creative lead",
"task": "Revise the vendor sync brief around a lightweight review draft.",
"due_date": "2026-04-21T00:00:00",
"depends_on": "None"
},
{
"owner": "Ethan Brooks",
"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... | 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_0080 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Lattice Harbor",
"meeting_type": "retrospective",
"meeting_date": "2026-05-12T00: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": "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 retrospective. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Sofia 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 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": "Zoe Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Zoe Morgan",
"role": "creative lead",
"task": "Revise the retrospective brief around a proof-first recap.",
"due_date": "2026-04-22T00:00:00",
"depends_on": "None"
},
{
"owner": "Sofia Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and note w... | {
"email_subject": "Lattice Harbor 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... | [
"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 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": [
"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_0081 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Velora Motion",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-08T00: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": "Elijah 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 source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Elijah 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-08."
},
{
"speaker": "Sofia Rivera",
"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": "Elijah Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Elijah Kim",
"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": "Noah Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Velora Motion 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 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": "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 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": [
"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_0082 | 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-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": "Sofia 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 source footage is wider than the launch window allows visible instead of glossing over ... | [
{
"speaker": "Sofia 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-28."
},
{
"speaker": "Ivy Patel",
"role": "stakeholder",
"timestamp": "00:21",
"tex... | {
"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": "Sofia Rivera"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wa... | [
{
"owner": "Sofia Rivera",
"role": "creative lead",
"task": "Revise the client onboarding brief around a lightweight review draft.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Ava Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable... | {
"email_subject": "Glowforge Labs 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 ... | [
"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_0083 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Harborline Works",
"meeting_type": "vendor sync",
"meeting_date": "2026-05-08T00: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 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": "Liam 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-08."
},
{
"speaker": "Zoe Brooks",
"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 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": "Liam Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Liam 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": "Lucas Lopez",
"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 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 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_0084 | train | easy | 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-15T00: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 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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Liam 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-15."
},
{
"speaker": "Zoe 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 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": "Liam Brooks"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof... | [
{
"owner": "Liam Brooks",
"role": "creative lead",
"task": "Revise the vendor sync brief around a teaser-first cut.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what... | {
"email_subject": "Northbeam Studio 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": "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 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": [
"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_0085 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Lattice Harbor",
"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": "Lucas 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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Lucas Shah",
"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": "Ava Nguyen",
"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 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": "Lucas Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team want... | [
{
"owner": "Lucas Shah",
"role": "creative lead",
"task": "Revise the retrospective brief around a lightweight review draft.",
"due_date": "2026-04-27T00:00:00",
"depends_on": "None"
},
{
"owner": "Ivy Chen",
"role": "editor",
"task": "Prepare the first scoped deliverable and not... | {
"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 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": "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_0086 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "Tidal North Labs",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-08T00: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... | [
{
"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 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-05-08."
},
{
"speaker": "Noah Patel",
"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 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": "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 campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-28T00:00:00",
"depends_on": "None"
},
{
"owner": "Ethan Walker",
"role": "editor",
"task": "Prepare the first scoped deliverabl... | {
"email_subject": "Tidal North Labs 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": "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... | 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_0087 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Velora Motion",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-15T00: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": "Elijah ... | [
{
"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 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-05-15."
},
{
"speaker": "Mia Kim",
"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": "Elijah Patel"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Elijah Patel",
"role": "creative lead",
"task": "Revise the campaign planning brief around a tighter pilot package.",
"due_date": "2026-04-16T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable a... | {
"email_subject": "Velora Motion 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": "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 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": [
"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_0088 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Signal Oak",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-08T00: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": "Noah 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 legal language is still pending visible instead of glossing over it."
},
{
"slot": ... | [
{
"speaker": "Noah 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-08."
},
{
"speaker": "Ava Morgan",
"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 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": "Noah Shah"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof a... | [
{
"owner": "Noah Shah",
"role": "creative lead",
"task": "Revise the campaign planning brief around a teaser-first cut.",
"due_date": "2026-04-17T00:00:00",
"depends_on": "None"
},
{
"owner": "Ethan Brooks",
"role": "editor",
"task": "Prepare the first scoped deliverable and note... | {
"email_subject": "Signal Oak 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 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": "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 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": [
"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_0089 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Glowforge Labs",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-05T00: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": "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 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-05."
},
{
"speaker": "Isla Morgan",
"role": "stakeholder",
"timestamp": "00:21",
"t... | {
"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": "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 campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-18T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable a... | {
"email_subject": "Glowforge Labs 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": "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_0090 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"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": "Lucas 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": "Lucas 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 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 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": "Lucas Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proo... | [
{
"owner": "Lucas Walker",
"role": "creative lead",
"task": "Revise the creative review brief around a teaser-first cut.",
"due_date": "2026-04-19T00:00:00",
"depends_on": "None"
},
{
"owner": "Miles Brooks",
"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_0091 | train | medium | 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-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": "Elijah Diaz",
"rol... | [
{
"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 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": "Ethan Rivera",
"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": "Elijah Diaz"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wan... | [
{
"owner": "Elijah Diaz",
"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": "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 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": "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_0092 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.85 | {
"brand": "Tidal North Labs",
"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": "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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"speaker": "Elijah 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-04-22."
},
{
"speaker": "Lucas Morris",
"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 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": "Elijah Morris"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team w... | [
{
"owner": "Elijah Morris",
"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": "Noah Lopez",
"role": "editor",
"task": "Prepare the first scoped deliverabl... | {
"email_subject": "Tidal North Labs 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": "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... | 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_0093 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.93 | {
"brand": "Signal Oak",
"meeting_type": "campaign planning",
"meeting_date": "2026-05-12T00: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": "Jalen Walk... | [
{
"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 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": "Ethan Morgan",
"role": "stakeholder",
"timestamp": "00:21",
"... | {
"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 Walker"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants pro... | [
{
"owner": "Jalen Walker",
"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": "Ivy Morgan",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Signal Oak 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 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_0094 | train | medium | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Tidal North Labs",
"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": "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 campaign planning. Right now the draft is too broad for the review window on 2026-04-28."
},
{
"speaker": "Miles Lopez",
"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": "Ivy Kim"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof and... | [
{
"owner": "Ivy Kim",
"role": "creative lead",
"task": "Revise the campaign planning brief around a teaser-first cut.",
"due_date": "2026-04-23T00:00:00",
"depends_on": "None"
},
{
"owner": "Lucas Kim",
"role": "editor",
"task": "Prepare the first scoped deliverable and note what... | {
"email_subject": "Tidal North Labs 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 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_0095 | train | hard | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.88 | {
"brand": "Velora Motion",
"meeting_type": "retrospective",
"meeting_date": "2026-05-12T00: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": "Isla ... | [
{
"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 retrospective. Right now the draft is too broad for the review window on 2026-05-12."
},
{
"speaker": "Jalen Lopez",
"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 source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved whi... | [
{
"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 retrospective brief around a lightweight review draft.",
"due_date": "2026-04-24T00:00:00",
"depends_on": "None"
},
{
"owner": "Zoe Morris",
"role": "editor",
"task": "Prepare the first scoped deliverable and no... | {
"email_subject": "Velora Motion 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": "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 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": [
"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_0096 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.91 | {
"brand": "First Mile Creative",
"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": "Nora 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": "Nora 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": "Isla Nguyen",
"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 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": "Nora Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Nora Chen",
"role": "creative lead",
"task": "Revise the campaign planning brief around a lightweight review draft.",
"due_date": "2026-04-25T00:00:00",
"depends_on": "None"
},
{
"owner": "Isla Shah",
"role": "editor",
"task": "Prepare the first scoped deliverable and... | {
"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... | 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_0097 | 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": "Jalen 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 two stakeholders still disagree on scope visible instead of glossing over it."
},
{
... | [
{
"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-01."
},
{
"speaker": "Jalen Patel",
"role": "stakeholder",
"timestamp": "00:21",
"text": ... | {
"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": "Jalen Morgan"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Jalen Morgan",
"role": "creative lead",
"task": "Revise the vendor sync brief around a tighter pilot package.",
"due_date": "2026-04-26T00:00:00",
"depends_on": "None"
},
{
"owner": "Nora Diaz",
"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 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": "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_0098 | train | hard | 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-08T00: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": "Noah ... | [
{
"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": "Noah 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": "Mia Brooks",
"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": "Noah Chen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants... | [
{
"owner": "Noah Chen",
"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": "Sofia Walker",
"role": "editor",
"task": "Prepare the first scoped deliverable ... | {
"email_subject": "Northbeam Studio 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": "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_0099 | train | easy | Zarn | meeting_actions | apache-2.0 | zarnite-team-reviewed-gold-track-starter | 0.89 | {
"brand": "Orbit Thread",
"meeting_type": "client onboarding",
"meeting_date": "2026-04-24T00: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 Nguye... | [
{
"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 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-24."
},
{
"speaker": "Lucas Kim",
"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 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": "Mia Nguyen"
},
{
"decision": "Push the broader rollout to the next wave after the first scoped pass.",
"reason": "The team wants proof ... | [
{
"owner": "Mia Nguyen",
"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": "Ivy Nguyen",
"role": "editor",
"task": "Prepare the first scoped deliverable and note ... | {
"email_subject": "Orbit Thread 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": "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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.