{"example_id": "zarn_meeting_to_actions_validation_0000", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "retrospective", "meeting_date": "2026-05-12", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ava Rivera", "role": "creative lead"}, {"name": "Ivy Morris", "role": "stakeholder"}, {"name": "Lucas Rivera", "role": "operations owner"}, {"name": "Isla Kim", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Ava 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-12."}, {"speaker": "Ivy Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Lucas Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Rivera"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ivy Morris"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Rivera"}], "reference_action_items": [{"owner": "Ava Rivera", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Isla Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Ava Rivera"}, {"owner": "Ivy Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Rivera will send the updated recap and propose a short review before 2026-04-20, while Ava Rivera revises the brief and Isla Kim prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0001", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Signal Oak", "meeting_type": "client onboarding", "meeting_date": "2026-05-01", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Elijah Chen", "role": "creative lead"}, {"name": "Isla Diaz", "role": "stakeholder"}, {"name": "Lucas Lopez", "role": "operations owner"}, {"name": "Mia Brooks", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Elijah Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Isla Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Lucas Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Brooks", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Isla Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Brooks", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Elijah Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Isla Diaz"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Lopez"}], "reference_action_items": [{"owner": "Elijah Chen", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Mia Brooks", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Elijah Chen"}, {"owner": "Isla Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Signal Oak 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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Lopez will send the updated recap and propose a short review before 2026-04-21, while Elijah Chen revises the brief and Mia Brooks prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0002", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "campaign planning", "meeting_date": "2026-04-24", "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": "Mia Nguyen", "role": "creative lead"}, {"name": "Ivy Diaz", "role": "stakeholder"}, {"name": "Ava Morgan", "role": "operations owner"}, {"name": "Noah Patel", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Mia Nguyen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Ivy Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Ava Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft 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 and alignment before expanding scope.", "owner": "Ivy Diaz"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Morgan"}], "reference_action_items": [{"owner": "Mia Nguyen", "role": "creative lead", "task": "Revise the campaign planning brief around a lightweight review draft.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Noah Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Mia Nguyen"}, {"owner": "Ivy Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Morgan will send the updated recap and propose a short review before 2026-04-22, while Mia Nguyen revises the brief and Noah Patel prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0003", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "client onboarding", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Elijah Kim", "role": "creative lead"}, {"name": "Jalen Patel", "role": "stakeholder"}, {"name": "Miles Morgan", "role": "operations owner"}, {"name": "Isla Diaz", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Elijah Kim", "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": "Jalen Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Miles Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 wants proof and alignment before expanding scope.", "owner": "Jalen Patel"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Morgan"}], "reference_action_items": [{"owner": "Elijah Kim", "role": "creative lead", "task": "Revise the client onboarding brief around a lightweight review draft.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Isla Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Elijah Kim"}, {"owner": "Jalen Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Morgan will send the updated recap and propose a short review before 2026-04-23, while Elijah Kim revises the brief and Isla Diaz prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0004", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "client onboarding", "meeting_date": "2026-04-24", "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": "Zoe Chen", "role": "creative lead"}, {"name": "Elijah Morris", "role": "stakeholder"}, {"name": "Sofia Patel", "role": "operations owner"}, {"name": "Elijah Rivera", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Zoe Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Elijah Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Zoe Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Morris"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Patel"}], "reference_action_items": [{"owner": "Zoe Chen", "role": "creative lead", "task": "Revise the client onboarding brief around a teaser-first cut.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Elijah Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Zoe Chen"}, {"owner": "Elijah Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North Labs client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Patel will send the updated recap and propose a short review before 2026-04-24, while Zoe Chen revises the brief and Elijah Rivera prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0005", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "campaign planning", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Ava Shah", "role": "creative lead"}, {"name": "Jalen Morgan", "role": "stakeholder"}, {"name": "Zoe Lopez", "role": "operations owner"}, {"name": "Liam Shah", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Ava 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": "Jalen Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Zoe Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Morgan"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Lopez"}], "reference_action_items": [{"owner": "Ava Shah", "role": "creative lead", "task": "Revise the campaign planning brief around a lightweight review draft.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Liam Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Ava Shah"}, {"owner": "Jalen Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Lopez will send the updated recap and propose a short review before 2026-04-25, while Ava Shah revises the brief and Liam Shah prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0006", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "vendor sync", "meeting_date": "2026-04-24", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Sofia Rivera", "role": "creative lead"}, {"name": "Zoe Walker", "role": "stakeholder"}, {"name": "Ava Nguyen", "role": "operations owner"}, {"name": "Ava Brooks", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Sofia 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-24."}, {"speaker": "Zoe Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ava Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Brooks", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Zoe Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Brooks", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 wants proof and alignment before expanding scope.", "owner": "Zoe Walker"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Nguyen"}], "reference_action_items": [{"owner": "Sofia Rivera", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Ava Brooks", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Sofia Rivera"}, {"owner": "Zoe Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Nguyen will send the updated recap and propose a short review before 2026-04-26, while Sofia Rivera revises the brief and Ava Brooks prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0007", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "client onboarding", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Isla Nguyen", "role": "creative lead"}, {"name": "Mia Morris", "role": "stakeholder"}, {"name": "Mia Chen", "role": "operations owner"}, {"name": "Noah Lopez", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Isla 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-08."}, {"speaker": "Mia Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Mia Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Isla Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Mia Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Isla Nguyen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Mia Morris"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Mia Chen"}], "reference_action_items": [{"owner": "Isla Nguyen", "role": "creative lead", "task": "Revise the client onboarding brief around a teaser-first cut.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Noah Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Isla Nguyen"}, {"owner": "Mia Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Mia Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Mia Chen will send the updated recap and propose a short review before 2026-04-27, while Isla Nguyen revises the brief and Noah Lopez prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0008", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Harborline Works", "meeting_type": "client onboarding", "meeting_date": "2026-05-05", "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": "Ethan Walker", "role": "creative lead"}, {"name": "Miles Morris", "role": "stakeholder"}, {"name": "Nora Kim", "role": "operations owner"}, {"name": "Ethan Diaz", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Ethan Walker", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-05."}, {"speaker": "Miles Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Nora Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 proof and alignment before expanding scope.", "owner": "Miles Morris"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Kim"}], "reference_action_items": [{"owner": "Ethan Walker", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Ethan Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Ethan Walker"}, {"owner": "Miles Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Kim will send the updated recap and propose a short review before 2026-04-28, while Ethan Walker revises the brief and Ethan Diaz prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0009", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Harborline Works", "meeting_type": "campaign planning", "meeting_date": "2026-05-15", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Sofia Chen", "role": "creative lead"}, {"name": "Ethan Nguyen", "role": "stakeholder"}, {"name": "Noah Shah", "role": "operations owner"}, {"name": "Mia Shah", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Sofia 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-15."}, {"speaker": "Ethan Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Noah Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Noah Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Sofia Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ethan Nguyen"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Noah Shah"}], "reference_action_items": [{"owner": "Sofia Chen", "role": "creative lead", "task": "Revise the campaign planning brief around a teaser-first cut.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Mia Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Sofia Chen"}, {"owner": "Ethan Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Noah Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works 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 language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Noah Shah will send the updated recap and propose a short review before 2026-04-16, while Sofia Chen revises the brief and Mia Shah prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0010", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Diaz", "role": "creative lead"}, {"name": "Liam Rivera", "role": "stakeholder"}, {"name": "Miles Walker", "role": "operations owner"}, {"name": "Jalen Nguyen", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Lucas Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-22."}, {"speaker": "Liam Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Miles Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Liam Rivera"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Walker"}], "reference_action_items": [{"owner": "Lucas Diaz", "role": "creative lead", "task": "Revise the vendor sync brief around a tighter pilot package.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Jalen Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Lucas Diaz"}, {"owner": "Liam Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Walker will send the updated recap and propose a short review before 2026-04-17, while Lucas Diaz revises the brief and Jalen Nguyen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0011", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "client onboarding", "meeting_date": "2026-05-05", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Liam Patel", "role": "creative lead"}, {"name": "Sofia Shah", "role": "stakeholder"}, {"name": "Liam Morgan", "role": "operations owner"}, {"name": "Nora Lopez", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Liam 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-05."}, {"speaker": "Sofia Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Liam Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Liam Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Liam Patel"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Sofia Shah"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Morgan"}], "reference_action_items": [{"owner": "Liam Patel", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Nora Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Liam Patel"}, {"owner": "Sofia Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Echoframe Media 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 the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Morgan will send the updated recap and propose a short review before 2026-04-18, while Liam Patel revises the brief and Nora Lopez prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0012", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "client onboarding", "meeting_date": "2026-05-05", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Elijah Nguyen", "role": "creative lead"}, {"name": "Ivy Rivera", "role": "stakeholder"}, {"name": "Miles Lopez", "role": "operations owner"}, {"name": "Liam Chen", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Elijah 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-05."}, {"speaker": "Ivy Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Miles Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Ivy Rivera"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Lopez"}], "reference_action_items": [{"owner": "Elijah Nguyen", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Liam Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Elijah Nguyen"}, {"owner": "Ivy Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Lopez will send the updated recap and propose a short review before 2026-04-19, while Elijah Nguyen revises the brief and Liam Chen prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0013", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "client onboarding", "meeting_date": "2026-04-24", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ava Rivera", "role": "creative lead"}, {"name": "Noah Patel", "role": "stakeholder"}, {"name": "Sofia Rivera", "role": "operations owner"}, {"name": "Sofia Kim", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Ava Rivera", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Noah Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Rivera"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Patel"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Rivera"}], "reference_action_items": [{"owner": "Ava Rivera", "role": "creative lead", "task": "Revise the client onboarding brief around a teaser-first cut.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Sofia Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Ava Rivera"}, {"owner": "Noah Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Rivera will send the updated recap and propose a short review before 2026-04-20, while Ava Rivera revises the brief and Sofia Kim prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0014", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "client onboarding", "meeting_date": "2026-05-05", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Isla Patel", "role": "creative lead"}, {"name": "Elijah Lopez", "role": "stakeholder"}, {"name": "Miles Morris", "role": "operations owner"}, {"name": "Mia Chen", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Isla 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-05."}, {"speaker": "Elijah Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Miles Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Isla Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 wants proof and alignment before expanding scope.", "owner": "Elijah Lopez"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Morris"}], "reference_action_items": [{"owner": "Isla Patel", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Mia Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Isla Patel"}, {"owner": "Elijah Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge 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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Morris will send the updated recap and propose a short review before 2026-04-21, while Isla Patel revises the brief and Mia Chen prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0015", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "creative review", "meeting_date": "2026-05-01", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Zoe Patel", "role": "creative lead"}, {"name": "Ethan Walker", "role": "stakeholder"}, {"name": "Jalen Walker", "role": "operations owner"}, {"name": "Liam Rivera", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Zoe Patel", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Ethan Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Jalen Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 and alignment before expanding scope.", "owner": "Ethan Walker"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Walker"}], "reference_action_items": [{"owner": "Zoe Patel", "role": "creative lead", "task": "Revise the creative review brief around a tighter pilot package.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Liam Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Zoe Patel"}, {"owner": "Ethan Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North Labs creative review: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Walker will send the updated recap and propose a short review before 2026-04-22, while Zoe Patel revises the brief and Liam Rivera prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0016", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "creative review", "meeting_date": "2026-04-24", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Jalen Shah", "role": "creative lead"}, {"name": "Elijah Shah", "role": "stakeholder"}, {"name": "Nora Morgan", "role": "operations owner"}, {"name": "Mia Kim", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Jalen 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": "Elijah Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Nora Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Shah"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Morgan"}], "reference_action_items": [{"owner": "Jalen Shah", "role": "creative lead", "task": "Revise the creative review brief around a proof-first recap.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Mia Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Jalen Shah"}, {"owner": "Elijah Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Echoframe Media 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 language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Morgan will send the updated recap and propose a short review before 2026-04-23, while Jalen Shah revises the brief and Mia Kim prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0017", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Harborline Works", "meeting_type": "vendor sync", "meeting_date": "2026-04-28", "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 Brooks", "role": "creative lead"}, {"name": "Elijah Walker", "role": "stakeholder"}, {"name": "Nora Morris", "role": "operations owner"}, {"name": "Nora Chen", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Lucas 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-04-28."}, {"speaker": "Elijah Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Nora Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Brooks"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Walker"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Morris"}], "reference_action_items": [{"owner": "Lucas Brooks", "role": "creative lead", "task": "Revise the vendor sync brief around a lightweight review draft.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Nora Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Lucas Brooks"}, {"owner": "Elijah Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Morris will send the updated recap and propose a short review before 2026-04-24, while Lucas Brooks revises the brief and Nora Chen prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0018", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Harborline Works", "meeting_type": "vendor sync", "meeting_date": "2026-05-08", "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 Lopez", "role": "creative lead"}, {"name": "Zoe Morgan", "role": "stakeholder"}, {"name": "Zoe Chen", "role": "operations owner"}, {"name": "Mia Walker", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Zoe 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-05-08."}, {"speaker": "Zoe Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Zoe Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Zoe Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Lopez", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Zoe Lopez"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Zoe Morgan"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Chen"}], "reference_action_items": [{"owner": "Zoe Lopez", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Mia Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Zoe Lopez"}, {"owner": "Zoe Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works 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 still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Chen will send the updated recap and propose a short review before 2026-04-25, while Zoe Lopez revises the brief and Mia Walker prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0019", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Harborline Works", "meeting_type": "creative review", "meeting_date": "2026-05-08", "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 Brooks", "role": "creative lead"}, {"name": "Mia Walker", "role": "stakeholder"}, {"name": "Liam Morgan", "role": "operations owner"}, {"name": "Ivy Nguyen", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Lucas 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": "Mia Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Liam Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Brooks"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Mia Walker"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Morgan"}], "reference_action_items": [{"owner": "Lucas Brooks", "role": "creative lead", "task": "Revise the creative review brief around a tighter pilot package.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Ivy Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Lucas Brooks"}, {"owner": "Mia Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Morgan will send the updated recap and propose a short review before 2026-04-26, while Lucas Brooks revises the brief and Ivy Nguyen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0020", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Harborline Works", "meeting_type": "vendor sync", "meeting_date": "2026-05-01", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Ava Morris", "role": "creative lead"}, {"name": "Isla Rivera", "role": "stakeholder"}, {"name": "Liam Rivera", "role": "operations owner"}, {"name": "Nora Morris", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Ava 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-01."}, {"speaker": "Isla Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Liam Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Isla Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the vendor sync workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Morris"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Isla Rivera"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Rivera"}], "reference_action_items": [{"owner": "Ava Morris", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Nora Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Ava Morris"}, {"owner": "Isla Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Rivera will send the updated recap and propose a short review before 2026-04-27, while Ava Morris revises the brief and Nora Morris prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0021", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "retrospective", "meeting_date": "2026-04-24", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Mia Diaz", "role": "creative lead"}, {"name": "Jalen Chen", "role": "stakeholder"}, {"name": "Jalen Morgan", "role": "operations owner"}, {"name": "Liam Rivera", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Mia 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-04-24."}, {"speaker": "Jalen Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Jalen Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a teaser-first cut for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Chen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Morgan"}], "reference_action_items": [{"owner": "Mia Diaz", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Liam Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Mia Diaz"}, {"owner": "Jalen Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Morgan will send the updated recap and propose a short review before 2026-04-28, while Mia Diaz revises the brief and Liam Rivera prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0022", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "creative review", "meeting_date": "2026-04-28", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Sofia Shah", "role": "creative lead"}, {"name": "Lucas Morgan", "role": "stakeholder"}, {"name": "Jalen Nguyen", "role": "operations owner"}, {"name": "Miles Morris", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"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-28."}, {"speaker": "Lucas Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Jalen Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Miles Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Miles Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft 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 and alignment before expanding scope.", "owner": "Lucas Morgan"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Nguyen"}], "reference_action_items": [{"owner": "Sofia Shah", "role": "creative lead", "task": "Revise the creative review brief around a lightweight review draft.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Miles Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Sofia Shah"}, {"owner": "Lucas Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay creative review: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Nguyen will send the updated recap and propose a short review before 2026-04-16, while Sofia Shah revises the brief and Miles Morris prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0023", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "retrospective", "meeting_date": "2026-05-08", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Noah Rivera", "role": "creative lead"}, {"name": "Mia Brooks", "role": "stakeholder"}, {"name": "Noah Rivera", "role": "operations owner"}, {"name": "Lucas Nguyen", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Noah Rivera", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-08."}, {"speaker": "Mia Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Noah Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Lucas Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Noah Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Lucas Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Rivera"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Mia Brooks"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Noah Rivera"}], "reference_action_items": [{"owner": "Noah Rivera", "role": "creative lead", "task": "Revise the retrospective brief around a proof-first recap.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Lucas Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Noah Rivera"}, {"owner": "Mia Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Noah Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Echoframe Media retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Noah Rivera will send the updated recap and propose a short review before 2026-04-17, while Noah Rivera revises the brief and Lucas Nguyen prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0024", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "client onboarding", "meeting_date": "2026-04-28", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ivy Brooks", "role": "creative lead"}, {"name": "Nora Chen", "role": "stakeholder"}, {"name": "Ava Kim", "role": "operations owner"}, {"name": "Ava Morris", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Ivy 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-28."}, {"speaker": "Nora Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Ava Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Nora Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 wants proof and alignment before expanding scope.", "owner": "Nora Chen"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Kim"}], "reference_action_items": [{"owner": "Ivy Brooks", "role": "creative lead", "task": "Revise the client onboarding brief around a lightweight review draft.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Ava Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Ivy Brooks"}, {"owner": "Nora Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North 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 that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Kim will send the updated recap and propose a short review before 2026-04-18, while Ivy Brooks revises the brief and Ava Morris prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0025", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "campaign planning", "meeting_date": "2026-04-28", "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 Morris", "role": "creative lead"}, {"name": "Lucas Shah", "role": "stakeholder"}, {"name": "Ava Shah", "role": "operations owner"}, {"name": "Ivy Shah", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"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-04-28."}, {"speaker": "Lucas Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ava Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut 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 proof and alignment before expanding scope.", "owner": "Lucas Shah"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Shah"}], "reference_action_items": [{"owner": "Lucas Morris", "role": "creative lead", "task": "Revise the campaign planning brief around a teaser-first cut.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Ivy Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Lucas Morris"}, {"owner": "Lucas Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Shah will send the updated recap and propose a short review before 2026-04-19, while Lucas Morris revises the brief and Ivy Shah prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0026", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "vendor sync", "meeting_date": "2026-05-15", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Miles Patel", "role": "creative lead"}, {"name": "Isla Rivera", "role": "stakeholder"}, {"name": "Liam Lopez", "role": "operations owner"}, {"name": "Isla Lopez", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Miles 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-15."}, {"speaker": "Isla Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Liam Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Isla Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut 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 wants proof and alignment before expanding scope.", "owner": "Isla Rivera"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Lopez"}], "reference_action_items": [{"owner": "Miles Patel", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Isla Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Miles Patel"}, {"owner": "Isla Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Lopez will send the updated recap and propose a short review before 2026-04-20, while Miles Patel revises the brief and Isla Lopez prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0027", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "creative review", "meeting_date": "2026-04-28", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Rivera", "role": "creative lead"}, {"name": "Ethan Nguyen", "role": "stakeholder"}, {"name": "Lucas Walker", "role": "operations owner"}, {"name": "Zoe Kim", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Lucas 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-04-28."}, {"speaker": "Ethan Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Lucas Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Zoe Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Zoe Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a teaser-first cut for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Rivera"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ethan Nguyen"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Walker"}], "reference_action_items": [{"owner": "Lucas Rivera", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Zoe Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Lucas Rivera"}, {"owner": "Ethan Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative creative review: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Walker will send the updated recap and propose a short review before 2026-04-21, while Lucas Rivera revises the brief and Zoe Kim prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0028", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Harborline Works", "meeting_type": "campaign planning", "meeting_date": "2026-04-24", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Ava Brooks", "role": "creative lead"}, {"name": "Liam Lopez", "role": "stakeholder"}, {"name": "Ava Chen", "role": "operations owner"}, {"name": "Ava Walker", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Ava Brooks", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Liam Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ava Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut 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 wants proof and alignment before expanding scope.", "owner": "Liam Lopez"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Chen"}], "reference_action_items": [{"owner": "Ava Brooks", "role": "creative lead", "task": "Revise the campaign planning brief around a teaser-first cut.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Ava Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Ava Brooks"}, {"owner": "Liam Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works campaign planning: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Chen will send the updated recap and propose a short review before 2026-04-22, while Ava Brooks revises the brief and Ava Walker prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0029", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Velora Motion", "meeting_type": "creative review", "meeting_date": "2026-05-05", "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 Morris", "role": "creative lead"}, {"name": "Ava Chen", "role": "stakeholder"}, {"name": "Sofia Chen", "role": "operations owner"}, {"name": "Jalen Walker", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Ava Morris", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-05."}, {"speaker": "Ava Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Sofia Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Morris"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ava Chen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Chen"}], "reference_action_items": [{"owner": "Ava Morris", "role": "creative lead", "task": "Revise the creative review brief around a tighter pilot package.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Jalen Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Ava Morris"}, {"owner": "Ava Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion 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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Chen will send the updated recap and propose a short review before 2026-04-23, while Ava Morris revises the brief and Jalen Walker prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0030", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Signal Oak", "meeting_type": "retrospective", "meeting_date": "2026-05-05", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ethan Walker", "role": "creative lead"}, {"name": "Zoe Rivera", "role": "stakeholder"}, {"name": "Nora Nguyen", "role": "operations owner"}, {"name": "Nora Walker", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"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-05-05."}, {"speaker": "Zoe Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Nora Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Zoe Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Zoe Rivera"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Nguyen"}], "reference_action_items": [{"owner": "Ethan Walker", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Nora Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Ethan Walker"}, {"owner": "Zoe Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Nguyen will send the updated recap and propose a short review before 2026-04-24, while Ethan Walker revises the brief and Nora Walker prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0031", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "client onboarding", "meeting_date": "2026-05-05", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ethan Patel", "role": "creative lead"}, {"name": "Lucas Kim", "role": "stakeholder"}, {"name": "Noah Brooks", "role": "operations owner"}, {"name": "Sofia Shah", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"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-05."}, {"speaker": "Lucas Kim", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Noah Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Kim", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Noah Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut 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 proof and alignment before expanding scope.", "owner": "Lucas Kim"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Noah Brooks"}], "reference_action_items": [{"owner": "Ethan Patel", "role": "creative lead", "task": "Revise the client onboarding brief around a teaser-first cut.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Sofia Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Ethan Patel"}, {"owner": "Lucas Kim", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Noah Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Noah Brooks will send the updated recap and propose a short review before 2026-04-25, while Ethan Patel revises the brief and Sofia Shah prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0032", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Velora Motion", "meeting_type": "vendor sync", "meeting_date": "2026-04-28", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Jalen Rivera", "role": "creative lead"}, {"name": "Miles Walker", "role": "stakeholder"}, {"name": "Isla Lopez", "role": "operations owner"}, {"name": "Lucas Shah", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Jalen 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-28."}, {"speaker": "Miles Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Isla Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Lucas Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Isla Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Lucas Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Miles Walker"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Isla Lopez"}], "reference_action_items": [{"owner": "Jalen Rivera", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Lucas Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Jalen Rivera"}, {"owner": "Miles Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Isla Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion 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 wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Isla Lopez will send the updated recap and propose a short review before 2026-04-26, while Jalen Rivera revises the brief and Lucas Shah prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0033", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Harborline Works", "meeting_type": "client onboarding", "meeting_date": "2026-04-28", "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": "Nora Shah", "role": "creative lead"}, {"name": "Liam Brooks", "role": "stakeholder"}, {"name": "Zoe Chen", "role": "operations owner"}, {"name": "Ivy Nguyen", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Nora 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-28."}, {"speaker": "Liam Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Zoe Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Nora Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Nora Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Liam Brooks"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Chen"}], "reference_action_items": [{"owner": "Nora Shah", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Ivy Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Nora Shah"}, {"owner": "Liam Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Chen will send the updated recap and propose a short review before 2026-04-27, while Nora Shah revises the brief and Ivy Nguyen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0034", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Signal Oak", "meeting_type": "vendor sync", "meeting_date": "2026-05-15", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Liam Chen", "role": "creative lead"}, {"name": "Ivy Chen", "role": "stakeholder"}, {"name": "Jalen Rivera", "role": "operations owner"}, {"name": "Zoe Patel", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Liam Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-15."}, {"speaker": "Ivy Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Jalen Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Zoe Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Liam Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Zoe Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Liam Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ivy Chen"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Rivera"}], "reference_action_items": [{"owner": "Liam Chen", "role": "creative lead", "task": "Revise the vendor sync brief around a tighter pilot package.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Zoe Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Liam Chen"}, {"owner": "Ivy Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Rivera will send the updated recap and propose a short review before 2026-04-28, while Liam Chen revises the brief and Zoe Patel prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0035", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "retrospective", "meeting_date": "2026-05-12", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ethan Walker", "role": "creative lead"}, {"name": "Ava Shah", "role": "stakeholder"}, {"name": "Sofia Nguyen", "role": "operations owner"}, {"name": "Miles Kim", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"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-05-12."}, {"speaker": "Ava Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Sofia Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Miles Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Miles Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 proof and alignment before expanding scope.", "owner": "Ava Shah"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Nguyen"}], "reference_action_items": [{"owner": "Ethan Walker", "role": "creative lead", "task": "Revise the retrospective brief around a tighter pilot package.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Miles Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Ethan Walker"}, {"owner": "Ava Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Nguyen will send the updated recap and propose a short review before 2026-04-16, while Ethan Walker revises the brief and Miles Kim prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0036", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "client onboarding", "meeting_date": "2026-05-05", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Zoe Kim", "role": "creative lead"}, {"name": "Miles Nguyen", "role": "stakeholder"}, {"name": "Lucas Walker", "role": "operations owner"}, {"name": "Elijah Walker", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Zoe Kim", "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-05."}, {"speaker": "Miles Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Lucas Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Zoe Kim"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Miles Nguyen"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Walker"}], "reference_action_items": [{"owner": "Zoe Kim", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Elijah Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Zoe Kim"}, {"owner": "Miles Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Northbeam Studio client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Walker will send the updated recap and propose a short review before 2026-04-17, while Zoe Kim revises the brief and Elijah Walker prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0037", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "client onboarding", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Shah", "role": "creative lead"}, {"name": "Ethan Morgan", "role": "stakeholder"}, {"name": "Nora Lopez", "role": "operations owner"}, {"name": "Ivy Diaz", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Lucas Shah", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-08."}, {"speaker": "Ethan Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Nora Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ethan Morgan"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Lopez"}], "reference_action_items": [{"owner": "Lucas Shah", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Ivy Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Lucas Shah"}, {"owner": "Ethan Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Lopez will send the updated recap and propose a short review before 2026-04-18, while Lucas Shah revises the brief and Ivy Diaz prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0038", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Signal Oak", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Ava Brooks", "role": "creative lead"}, {"name": "Miles Morris", "role": "stakeholder"}, {"name": "Mia Chen", "role": "operations owner"}, {"name": "Jalen Walker", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Ava 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-04-22."}, {"speaker": "Miles Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Mia Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Mia Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 wants proof and alignment before expanding scope.", "owner": "Miles Morris"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Mia Chen"}], "reference_action_items": [{"owner": "Ava Brooks", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Jalen Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Ava Brooks"}, {"owner": "Miles Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Mia Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Signal Oak vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Mia Chen will send the updated recap and propose a short review before 2026-04-19, while Ava Brooks revises the brief and Jalen Walker prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0039", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "retrospective", "meeting_date": "2026-05-05", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ivy Morris", "role": "creative lead"}, {"name": "Ethan Nguyen", "role": "stakeholder"}, {"name": "Ivy Diaz", "role": "operations owner"}, {"name": "Ethan Walker", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"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-05-05."}, {"speaker": "Ethan Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Ivy Diaz", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Diaz", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 wants proof and alignment before expanding scope.", "owner": "Ethan Nguyen"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Diaz"}], "reference_action_items": [{"owner": "Ivy Morris", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Ethan Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Ivy Morris"}, {"owner": "Ethan Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Diaz", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Diaz will send the updated recap and propose a short review before 2026-04-20, while Ivy Morris revises the brief and Ethan Walker prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0040", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "client onboarding", "meeting_date": "2026-05-15", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Walker", "role": "creative lead"}, {"name": "Ava Chen", "role": "stakeholder"}, {"name": "Elijah Lopez", "role": "operations owner"}, {"name": "Jalen Shah", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Lucas Walker", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-15."}, {"speaker": "Ava Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Elijah Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 proof and alignment before expanding scope.", "owner": "Ava Chen"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Lopez"}], "reference_action_items": [{"owner": "Lucas Walker", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Jalen Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Lucas Walker"}, {"owner": "Ava Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Northbeam Studio 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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Lopez will send the updated recap and propose a short review before 2026-04-21, while Lucas Walker revises the brief and Jalen Shah prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0041", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Harborline Works", "meeting_type": "retrospective", "meeting_date": "2026-04-28", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ava Brooks", "role": "creative lead"}, {"name": "Miles Diaz", "role": "stakeholder"}, {"name": "Mia Rivera", "role": "operations owner"}, {"name": "Isla Walker", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Ava Brooks", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-28."}, {"speaker": "Miles Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Mia Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Mia Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 wants proof and alignment before expanding scope.", "owner": "Miles Diaz"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Mia Rivera"}], "reference_action_items": [{"owner": "Ava Brooks", "role": "creative lead", "task": "Revise the retrospective brief around a tighter pilot package.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Isla Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Ava Brooks"}, {"owner": "Miles Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Mia Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Mia Rivera will send the updated recap and propose a short review before 2026-04-22, while Ava Brooks revises the brief and Isla Walker prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0042", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "retrospective", "meeting_date": "2026-05-05", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ethan Rivera", "role": "creative lead"}, {"name": "Sofia Morris", "role": "stakeholder"}, {"name": "Ivy Walker", "role": "operations owner"}, {"name": "Nora Nguyen", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Ethan 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-05."}, {"speaker": "Sofia Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Ivy Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft 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 proof and alignment before expanding scope.", "owner": "Sofia Morris"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Walker"}], "reference_action_items": [{"owner": "Ethan Rivera", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Nora Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Ethan Rivera"}, {"owner": "Sofia Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Walker will send the updated recap and propose a short review before 2026-04-23, while Ethan Rivera revises the brief and Nora Nguyen prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0043", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "client onboarding", "meeting_date": "2026-04-24", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ethan Diaz", "role": "creative lead"}, {"name": "Elijah Patel", "role": "stakeholder"}, {"name": "Ethan Chen", "role": "operations owner"}, {"name": "Zoe Nguyen", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Ethan Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Elijah Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ethan Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Zoe Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Zoe Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ethan Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Patel"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Chen"}], "reference_action_items": [{"owner": "Ethan Diaz", "role": "creative lead", "task": "Revise the client onboarding brief around a teaser-first cut.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Zoe Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Ethan Diaz"}, {"owner": "Elijah Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Chen will send the updated recap and propose a short review before 2026-04-24, while Ethan Diaz revises the brief and Zoe Nguyen prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0044", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "client onboarding", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Liam Walker", "role": "creative lead"}, {"name": "Elijah Kim", "role": "stakeholder"}, {"name": "Jalen Morris", "role": "operations owner"}, {"name": "Nora Walker", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Liam Walker", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-08."}, {"speaker": "Elijah Kim", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Kim", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Liam Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Liam Walker"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Kim"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Morris"}], "reference_action_items": [{"owner": "Liam Walker", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Nora Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Liam Walker"}, {"owner": "Elijah Kim", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Morris will send the updated recap and propose a short review before 2026-04-25, while Liam Walker revises the brief and Nora Walker prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0045", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Harborline Works", "meeting_type": "client onboarding", "meeting_date": "2026-05-15", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ava Nguyen", "role": "creative lead"}, {"name": "Ava Nguyen", "role": "stakeholder"}, {"name": "Elijah Rivera", "role": "operations owner"}, {"name": "Sofia Morgan", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"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-15."}, {"speaker": "Ava Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Elijah Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 and alignment before expanding scope.", "owner": "Ava Nguyen"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Rivera"}], "reference_action_items": [{"owner": "Ava Nguyen", "role": "creative lead", "task": "Revise the client onboarding brief around a teaser-first cut.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Sofia Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Ava Nguyen"}, {"owner": "Ava Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Rivera will send the updated recap and propose a short review before 2026-04-26, while Ava Nguyen revises the brief and Sofia Morgan prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0046", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "creative review", "meeting_date": "2026-05-05", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Nora Morgan", "role": "creative lead"}, {"name": "Ethan Morris", "role": "stakeholder"}, {"name": "Sofia Nguyen", "role": "operations owner"}, {"name": "Miles Rivera", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"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-05."}, {"speaker": "Ethan Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Sofia Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Miles Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Nora Morgan", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Miles Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Ethan Morris"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Nguyen"}], "reference_action_items": [{"owner": "Nora Morgan", "role": "creative lead", "task": "Revise the creative review brief around a proof-first recap.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Miles Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Nora Morgan"}, {"owner": "Ethan Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative creative review: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Nguyen will send the updated recap and propose a short review before 2026-04-27, while Nora Morgan revises the brief and Miles Rivera prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0047", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-05-01", "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 Diaz", "role": "creative lead"}, {"name": "Ava Morris", "role": "stakeholder"}, {"name": "Isla Patel", "role": "operations owner"}, {"name": "Ethan Diaz", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Noah Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Ava Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Isla Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Isla Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ava Morris"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Isla Patel"}], "reference_action_items": [{"owner": "Noah Diaz", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Ethan Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Noah Diaz"}, {"owner": "Ava Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Isla Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative 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 still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Isla Patel will send the updated recap and propose a short review before 2026-04-28, while Noah Diaz revises the brief and Ethan Diaz prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0048", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "retrospective", "meeting_date": "2026-04-28", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Jalen Rivera", "role": "creative lead"}, {"name": "Liam Patel", "role": "stakeholder"}, {"name": "Ivy Nguyen", "role": "operations owner"}, {"name": "Zoe Morgan", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Jalen 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-28."}, {"speaker": "Liam Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ivy Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Zoe Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Zoe Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a teaser-first cut for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Liam Patel"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Nguyen"}], "reference_action_items": [{"owner": "Jalen Rivera", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Zoe Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Jalen Rivera"}, {"owner": "Liam Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North Labs retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Nguyen will send the updated recap and propose a short review before 2026-04-16, while Jalen Rivera revises the brief and Zoe Morgan prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0049", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "client onboarding", "meeting_date": "2026-05-15", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Morgan", "role": "creative lead"}, {"name": "Jalen Diaz", "role": "stakeholder"}, {"name": "Nora Brooks", "role": "operations owner"}, {"name": "Elijah Nguyen", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Lucas Morgan", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-15."}, {"speaker": "Jalen Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Nora Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Morgan", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Morgan"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Diaz"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Brooks"}], "reference_action_items": [{"owner": "Lucas Morgan", "role": "creative lead", "task": "Revise the client onboarding brief around a lightweight review draft.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Elijah Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Lucas Morgan"}, {"owner": "Jalen Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North 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 that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Brooks will send the updated recap and propose a short review before 2026-04-17, while Lucas Morgan revises the brief and Elijah Nguyen prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0050", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-05-12", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Shah", "role": "creative lead"}, {"name": "Lucas Rivera", "role": "stakeholder"}, {"name": "Nora Brooks", "role": "operations owner"}, {"name": "Isla Morris", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Lucas Shah", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."}, {"speaker": "Lucas Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Nora Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Lucas Rivera"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Brooks"}], "reference_action_items": [{"owner": "Lucas Shah", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Isla Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Lucas Shah"}, {"owner": "Lucas Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative 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 still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Brooks will send the updated recap and propose a short review before 2026-04-18, while Lucas Shah revises the brief and Isla Morris prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0051", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Harborline Works", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "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": "Ava Brooks", "role": "creative lead"}, {"name": "Isla Chen", "role": "stakeholder"}, {"name": "Ivy Rivera", "role": "operations owner"}, {"name": "Liam Lopez", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Ava 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-04-22."}, {"speaker": "Isla Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ivy Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Isla Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 wants proof and alignment before expanding scope.", "owner": "Isla Chen"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Rivera"}], "reference_action_items": [{"owner": "Ava Brooks", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Liam Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Ava Brooks"}, {"owner": "Isla Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works 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 still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Rivera will send the updated recap and propose a short review before 2026-04-19, while Ava Brooks revises the brief and Liam Lopez prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0052", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Brooks", "role": "creative lead"}, {"name": "Liam Morgan", "role": "stakeholder"}, {"name": "Jalen Morris", "role": "operations owner"}, {"name": "Lucas Patel", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Lucas 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-04-22."}, {"speaker": "Liam Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Lucas Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Lucas Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Brooks"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Liam Morgan"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Morris"}], "reference_action_items": [{"owner": "Lucas Brooks", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Lucas Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Lucas Brooks"}, {"owner": "Liam Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay 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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Morris will send the updated recap and propose a short review before 2026-04-20, while Lucas Brooks revises the brief and Lucas Patel prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0053", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "campaign planning", "meeting_date": "2026-05-05", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Elijah Morgan", "role": "creative lead"}, {"name": "Liam Diaz", "role": "stakeholder"}, {"name": "Ethan Lopez", "role": "operations owner"}, {"name": "Ethan Shah", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Elijah 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-05-05."}, {"speaker": "Liam Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Ethan Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Morgan", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the campaign planning workstream so the project can move without reopening full scope. They agreed that the 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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Elijah Morgan"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Liam Diaz"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Lopez"}], "reference_action_items": [{"owner": "Elijah Morgan", "role": "creative lead", "task": "Revise the campaign planning brief around a tighter pilot package.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Ethan Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Elijah Morgan"}, {"owner": "Liam Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative 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 the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Lopez will send the updated recap and propose a short review before 2026-04-21, while Elijah Morgan revises the brief and Ethan Shah prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0054", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Signal Oak", "meeting_type": "campaign planning", "meeting_date": "2026-05-01", "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": "Mia Rivera", "role": "creative lead"}, {"name": "Mia Chen", "role": "stakeholder"}, {"name": "Zoe Shah", "role": "operations owner"}, {"name": "Miles Kim", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Mia Rivera", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Mia Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Zoe Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Miles Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Miles Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Rivera"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Mia Chen"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Shah"}], "reference_action_items": [{"owner": "Mia Rivera", "role": "creative lead", "task": "Revise the campaign planning brief around a lightweight review draft.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Miles Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Mia Rivera"}, {"owner": "Mia Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Signal Oak 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 that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Shah will send the updated recap and propose a short review before 2026-04-22, while Mia Rivera revises the brief and Miles Kim prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0055", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "campaign planning", "meeting_date": "2026-05-15", "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": "Sofia Chen", "role": "creative lead"}, {"name": "Ivy Walker", "role": "stakeholder"}, {"name": "Jalen Patel", "role": "operations owner"}, {"name": "Ethan Nguyen", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Sofia 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-15."}, {"speaker": "Ivy Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Jalen Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Sofia Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ivy Walker"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Patel"}], "reference_action_items": [{"owner": "Sofia Chen", "role": "creative lead", "task": "Revise the campaign planning brief around a lightweight review draft.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Ethan Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Sofia Chen"}, {"owner": "Ivy Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Patel will send the updated recap and propose a short review before 2026-04-23, while Sofia Chen revises the brief and Ethan Nguyen prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0056", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Signal Oak", "meeting_type": "client onboarding", "meeting_date": "2026-05-12", "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": "Mia Nguyen", "role": "creative lead"}, {"name": "Nora Patel", "role": "stakeholder"}, {"name": "Lucas Diaz", "role": "operations owner"}, {"name": "Elijah Rivera", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"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-05-12."}, {"speaker": "Nora Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Lucas Diaz", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Nora Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Diaz", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 and alignment before expanding scope.", "owner": "Nora Patel"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Diaz"}], "reference_action_items": [{"owner": "Mia Nguyen", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Elijah Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Mia Nguyen"}, {"owner": "Nora Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Diaz", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Signal Oak client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Diaz will send the updated recap and propose a short review before 2026-04-24, while Mia Nguyen revises the brief and Elijah Rivera prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0057", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "campaign planning", "meeting_date": "2026-05-15", "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 Diaz", "role": "creative lead"}, {"name": "Sofia Morris", "role": "stakeholder"}, {"name": "Zoe Walker", "role": "operations owner"}, {"name": "Elijah Kim", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Ivy Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-15."}, {"speaker": "Sofia Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Zoe Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ivy Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Sofia Morris"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Walker"}], "reference_action_items": [{"owner": "Ivy Diaz", "role": "creative lead", "task": "Revise the campaign planning brief around a teaser-first cut.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Elijah Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Ivy Diaz"}, {"owner": "Sofia Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Walker will send the updated recap and propose a short review before 2026-04-25, while Ivy Diaz revises the brief and Elijah Kim prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0058", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "creative review", "meeting_date": "2026-04-28", "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": "Zoe Patel", "role": "creative lead"}, {"name": "Noah Brooks", "role": "stakeholder"}, {"name": "Sofia Rivera", "role": "operations owner"}, {"name": "Ava Patel", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Zoe Patel", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-04-28."}, {"speaker": "Noah Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 and alignment before expanding scope.", "owner": "Noah Brooks"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Rivera"}], "reference_action_items": [{"owner": "Zoe Patel", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Ava Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Zoe Patel"}, {"owner": "Noah Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Echoframe Media creative review: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Rivera will send the updated recap and propose a short review before 2026-04-26, while Zoe Patel revises the brief and Ava Patel prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0059", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Velora Motion", "meeting_type": "creative review", "meeting_date": "2026-04-28", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Miles Diaz", "role": "creative lead"}, {"name": "Noah Diaz", "role": "stakeholder"}, {"name": "Lucas Walker", "role": "operations owner"}, {"name": "Jalen Morgan", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Miles 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-28."}, {"speaker": "Noah Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Lucas Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Miles Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Diaz"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Walker"}], "reference_action_items": [{"owner": "Miles Diaz", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Jalen Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Miles Diaz"}, {"owner": "Noah Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion 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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Walker will send the updated recap and propose a short review before 2026-04-27, while Miles Diaz revises the brief and Jalen Morgan prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0060", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "client onboarding", "meeting_date": "2026-04-22", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ava Morgan", "role": "creative lead"}, {"name": "Lucas Diaz", "role": "stakeholder"}, {"name": "Noah Morgan", "role": "operations owner"}, {"name": "Mia Shah", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Ava 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-04-22."}, {"speaker": "Lucas Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Noah Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Morgan", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Noah Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Morgan"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Lucas Diaz"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Noah Morgan"}], "reference_action_items": [{"owner": "Ava Morgan", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Mia Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Ava Morgan"}, {"owner": "Lucas Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Noah Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Echoframe Media client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Noah Morgan will send the updated recap and propose a short review before 2026-04-28, while Ava Morgan revises the brief and Mia Shah prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0061", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "client onboarding", "meeting_date": "2026-05-01", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Zoe Chen", "role": "creative lead"}, {"name": "Jalen Shah", "role": "stakeholder"}, {"name": "Mia Patel", "role": "operations owner"}, {"name": "Isla Lopez", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Zoe Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Jalen Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Mia Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Mia Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Zoe Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Shah"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Mia Patel"}], "reference_action_items": [{"owner": "Zoe Chen", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Isla Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Zoe Chen"}, {"owner": "Jalen Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Mia Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North Labs client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Mia Patel will send the updated recap and propose a short review before 2026-04-16, while Zoe Chen revises the brief and Isla Lopez prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0062", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "client onboarding", "meeting_date": "2026-04-24", "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": "Elijah Chen", "role": "creative lead"}, {"name": "Nora Walker", "role": "stakeholder"}, {"name": "Miles Kim", "role": "operations owner"}, {"name": "Liam Chen", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Elijah Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Nora Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Miles Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Nora Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Elijah Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Nora Walker"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Kim"}], "reference_action_items": [{"owner": "Elijah Chen", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Liam Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Elijah Chen"}, {"owner": "Nora Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Lattice Harbor 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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Kim will send the updated recap and propose a short review before 2026-04-17, while Elijah Chen revises the brief and Liam Chen prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0063", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "vendor sync", "meeting_date": "2026-04-24", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Ivy Shah", "role": "creative lead"}, {"name": "Nora Morgan", "role": "stakeholder"}, {"name": "Liam Kim", "role": "operations owner"}, {"name": "Ivy Nguyen", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Ivy Shah", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Nora Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Liam Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Nora Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a lightweight review draft for the vendor sync workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ivy Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Nora Morgan"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Kim"}], "reference_action_items": [{"owner": "Ivy Shah", "role": "creative lead", "task": "Revise the vendor sync brief around a lightweight review draft.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Ivy Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Ivy Shah"}, {"owner": "Nora Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Kim will send the updated recap and propose a short review before 2026-04-18, while Ivy Shah revises the brief and Ivy Nguyen prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0064", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Signal Oak", "meeting_type": "client onboarding", "meeting_date": "2026-04-22", "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": "Lucas Lopez", "role": "creative lead"}, {"name": "Lucas Diaz", "role": "stakeholder"}, {"name": "Ethan Nguyen", "role": "operations owner"}, {"name": "Ava Patel", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Lucas 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-04-22."}, {"speaker": "Lucas Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Ethan Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Lopez", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 proof and alignment before expanding scope.", "owner": "Lucas Diaz"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Nguyen"}], "reference_action_items": [{"owner": "Lucas Lopez", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Ava Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Lucas Lopez"}, {"owner": "Lucas Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Signal Oak 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 the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Nguyen will send the updated recap and propose a short review before 2026-04-19, while Lucas Lopez revises the brief and Ava Patel prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0065", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "client onboarding", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Noah Nguyen", "role": "creative lead"}, {"name": "Jalen Diaz", "role": "stakeholder"}, {"name": "Miles Walker", "role": "operations owner"}, {"name": "Nora Lopez", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Noah 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-08."}, {"speaker": "Jalen Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Miles Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Nguyen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Diaz"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Walker"}], "reference_action_items": [{"owner": "Noah Nguyen", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Nora Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Noah Nguyen"}, {"owner": "Jalen Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Walker will send the updated recap and propose a short review before 2026-04-20, while Noah Nguyen revises the brief and Nora Lopez prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0066", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "creative review", "meeting_date": "2026-04-28", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Sofia Kim", "role": "creative lead"}, {"name": "Noah Nguyen", "role": "stakeholder"}, {"name": "Ivy Morgan", "role": "operations owner"}, {"name": "Sofia Kim", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Sofia 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-04-28."}, {"speaker": "Noah Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Ivy Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Sofia Kim"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Nguyen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Morgan"}], "reference_action_items": [{"owner": "Sofia Kim", "role": "creative lead", "task": "Revise the creative review brief around a tighter pilot package.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Sofia Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Sofia Kim"}, {"owner": "Noah Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Northbeam Studio 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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Morgan will send the updated recap and propose a short review before 2026-04-21, while Sofia Kim revises the brief and Sofia Kim prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0067", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "retrospective", "meeting_date": "2026-05-12", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Walker", "role": "creative lead"}, {"name": "Ava Patel", "role": "stakeholder"}, {"name": "Elijah Kim", "role": "operations owner"}, {"name": "Nora Chen", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Lucas Walker", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-12."}, {"speaker": "Ava Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Elijah Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 wants proof and alignment before expanding scope.", "owner": "Ava Patel"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Kim"}], "reference_action_items": [{"owner": "Lucas Walker", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Nora Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Lucas Walker"}, {"owner": "Ava Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Northbeam Studio 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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Kim will send the updated recap and propose a short review before 2026-04-22, while Lucas Walker revises the brief and Nora Chen prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0068", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "client onboarding", "meeting_date": "2026-05-15", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ava Morgan", "role": "creative lead"}, {"name": "Lucas Patel", "role": "stakeholder"}, {"name": "Elijah Chen", "role": "operations owner"}, {"name": "Noah Shah", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Ava 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": "Lucas Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Elijah Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Morgan", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Morgan"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Lucas Patel"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Chen"}], "reference_action_items": [{"owner": "Ava Morgan", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Noah Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Ava Morgan"}, {"owner": "Lucas Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Lattice Harbor client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Chen will send the updated recap and propose a short review before 2026-04-23, while Ava Morgan revises the brief and Noah Shah prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0069", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "campaign planning", "meeting_date": "2026-04-28", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Sofia Lopez", "role": "creative lead"}, {"name": "Isla Rivera", "role": "stakeholder"}, {"name": "Ivy Brooks", "role": "operations owner"}, {"name": "Liam Walker", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Sofia 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-28."}, {"speaker": "Isla Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ivy Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Isla Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Lopez", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Sofia Lopez"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Isla Rivera"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Brooks"}], "reference_action_items": [{"owner": "Sofia Lopez", "role": "creative lead", "task": "Revise the campaign planning brief around a proof-first recap.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Liam Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Sofia Lopez"}, {"owner": "Isla Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Brooks will send the updated recap and propose a short review before 2026-04-24, while Sofia Lopez revises the brief and Liam Walker prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0070", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "creative review", "meeting_date": "2026-05-01", "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": "Isla Diaz", "role": "creative lead"}, {"name": "Mia Walker", "role": "stakeholder"}, {"name": "Ivy Shah", "role": "operations owner"}, {"name": "Noah Diaz", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"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-05-01."}, {"speaker": "Mia Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ivy Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Isla Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut 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 and alignment before expanding scope.", "owner": "Mia Walker"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Shah"}], "reference_action_items": [{"owner": "Isla Diaz", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Noah Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Isla Diaz"}, {"owner": "Mia Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Shah will send the updated recap and propose a short review before 2026-04-25, while Isla Diaz revises the brief and Noah Diaz prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0071", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "client onboarding", "meeting_date": "2026-05-01", "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 Morgan", "role": "creative lead"}, {"name": "Mia Morris", "role": "stakeholder"}, {"name": "Sofia Patel", "role": "operations owner"}, {"name": "Nora Rivera", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"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-01."}, {"speaker": "Mia Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Morgan", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut 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 proof and alignment before expanding scope.", "owner": "Mia Morris"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Patel"}], "reference_action_items": [{"owner": "Jalen Morgan", "role": "creative lead", "task": "Revise the client onboarding brief around a teaser-first cut.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Nora Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Jalen Morgan"}, {"owner": "Mia Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Patel will send the updated recap and propose a short review before 2026-04-26, while Jalen Morgan revises the brief and Nora Rivera prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0072", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "retrospective", "meeting_date": "2026-04-22", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Chen", "role": "creative lead"}, {"name": "Mia Rivera", "role": "stakeholder"}, {"name": "Nora Rivera", "role": "operations owner"}, {"name": "Jalen Patel", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Lucas Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-22."}, {"speaker": "Mia Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Nora Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft 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 and alignment before expanding scope.", "owner": "Mia Rivera"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Rivera"}], "reference_action_items": [{"owner": "Lucas Chen", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Jalen Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Lucas Chen"}, {"owner": "Mia Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Northbeam Studio 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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Rivera will send the updated recap and propose a short review before 2026-04-27, while Lucas Chen revises the brief and Jalen Patel prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0073", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "client onboarding", "meeting_date": "2026-05-12", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Miles Diaz", "role": "creative lead"}, {"name": "Liam Morgan", "role": "stakeholder"}, {"name": "Ava Brooks", "role": "operations owner"}, {"name": "Nora Shah", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Miles Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-12."}, {"speaker": "Liam Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Ava Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Miles Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Liam Morgan"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Brooks"}], "reference_action_items": [{"owner": "Miles Diaz", "role": "creative lead", "task": "Revise the client onboarding brief around a lightweight review draft.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Nora Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Miles Diaz"}, {"owner": "Liam Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Brooks will send the updated recap and propose a short review before 2026-04-28, while Miles Diaz revises the brief and Nora Shah prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0074", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Harborline Works", "meeting_type": "creative review", "meeting_date": "2026-05-12", "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": "Noah Nguyen", "role": "creative lead"}, {"name": "Isla Walker", "role": "stakeholder"}, {"name": "Nora Shah", "role": "operations owner"}, {"name": "Sofia Walker", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Noah 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-12."}, {"speaker": "Isla Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Nora Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Isla Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a teaser-first cut for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Nguyen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Isla Walker"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Shah"}], "reference_action_items": [{"owner": "Noah Nguyen", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Sofia Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Noah Nguyen"}, {"owner": "Isla Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works creative review: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Shah will send the updated recap and propose a short review before 2026-04-16, while Noah Nguyen revises the brief and Sofia Walker prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0075", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Harborline Works", "meeting_type": "vendor sync", "meeting_date": "2026-05-01", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Jalen Shah", "role": "creative lead"}, {"name": "Jalen Morgan", "role": "stakeholder"}, {"name": "Miles Brooks", "role": "operations owner"}, {"name": "Zoe Diaz", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Jalen Shah", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Jalen Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Miles Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Zoe Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Zoe Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Morgan"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Brooks"}], "reference_action_items": [{"owner": "Jalen Shah", "role": "creative lead", "task": "Revise the vendor sync brief around a tighter pilot package.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Zoe Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Jalen Shah"}, {"owner": "Jalen Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Brooks will send the updated recap and propose a short review before 2026-04-17, while Jalen Shah revises the brief and Zoe Diaz prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0076", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "creative review", "meeting_date": "2026-05-01", "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": "Liam Patel", "role": "creative lead"}, {"name": "Ethan Rivera", "role": "stakeholder"}, {"name": "Liam Morgan", "role": "operations owner"}, {"name": "Ethan Nguyen", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Liam Patel", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Ethan Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Liam Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Liam Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Liam Patel"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ethan Rivera"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Morgan"}], "reference_action_items": [{"owner": "Liam Patel", "role": "creative lead", "task": "Revise the creative review brief around a proof-first recap.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Ethan Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Liam Patel"}, {"owner": "Ethan Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Morgan will send the updated recap and propose a short review before 2026-04-18, while Liam Patel revises the brief and Ethan Nguyen prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0077", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Harborline Works", "meeting_type": "campaign planning", "meeting_date": "2026-05-12", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Miles Patel", "role": "creative lead"}, {"name": "Sofia Shah", "role": "stakeholder"}, {"name": "Miles Shah", "role": "operations owner"}, {"name": "Ivy Kim", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"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": "Sofia Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Miles Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 wants proof and alignment before expanding scope.", "owner": "Sofia Shah"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Shah"}], "reference_action_items": [{"owner": "Miles Patel", "role": "creative lead", "task": "Revise the campaign planning brief around a proof-first recap.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Ivy Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Miles Patel"}, {"owner": "Sofia Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works 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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Shah will send the updated recap and propose a short review before 2026-04-19, while Miles Patel revises the brief and Ivy Kim prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0078", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "creative review", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Elijah Chen", "role": "creative lead"}, {"name": "Sofia Walker", "role": "stakeholder"}, {"name": "Lucas Walker", "role": "operations owner"}, {"name": "Elijah Nguyen", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Elijah Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-08."}, {"speaker": "Sofia Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Lucas Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Elijah Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Sofia Walker"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Walker"}], "reference_action_items": [{"owner": "Elijah Chen", "role": "creative lead", "task": "Revise the creative review brief around a tighter pilot package.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Elijah Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Elijah Chen"}, {"owner": "Sofia Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay 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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Walker will send the updated recap and propose a short review before 2026-04-20, while Elijah Chen revises the brief and Elijah Nguyen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0079", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "vendor sync", "meeting_date": "2026-05-05", "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 Kim", "role": "creative lead"}, {"name": "Noah Shah", "role": "stakeholder"}, {"name": "Ethan Walker", "role": "operations owner"}, {"name": "Elijah Morris", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Zoe Kim", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-05."}, {"speaker": "Noah Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ethan Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Zoe Kim"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Shah"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Walker"}], "reference_action_items": [{"owner": "Zoe Kim", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Elijah Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Zoe Kim"}, {"owner": "Noah Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Walker will send the updated recap and propose a short review before 2026-04-21, while Zoe Kim revises the brief and Elijah Morris prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0080", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Velora Motion", "meeting_type": "vendor sync", "meeting_date": "2026-05-15", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Jalen Shah", "role": "creative lead"}, {"name": "Miles Kim", "role": "stakeholder"}, {"name": "Miles Shah", "role": "operations owner"}, {"name": "Jalen Shah", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Jalen Shah", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-15."}, {"speaker": "Miles Kim", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Miles Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Kim", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Miles Kim"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Shah"}], "reference_action_items": [{"owner": "Jalen Shah", "role": "creative lead", "task": "Revise the vendor sync brief around a lightweight review draft.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Jalen Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Jalen Shah"}, {"owner": "Miles Kim", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Shah will send the updated recap and propose a short review before 2026-04-22, while Jalen Shah revises the brief and Jalen Shah prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0081", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "client onboarding", "meeting_date": "2026-05-01", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Liam Diaz", "role": "creative lead"}, {"name": "Ava Brooks", "role": "stakeholder"}, {"name": "Nora Patel", "role": "operations owner"}, {"name": "Miles Shah", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Liam Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Ava Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Nora Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Miles Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Liam Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Miles Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Liam Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ava Brooks"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Patel"}], "reference_action_items": [{"owner": "Liam Diaz", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Miles Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Liam Diaz"}, {"owner": "Ava Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Patel will send the updated recap and propose a short review before 2026-04-23, while Liam Diaz revises the brief and Miles Shah prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0082", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Velora Motion", "meeting_type": "retrospective", "meeting_date": "2026-04-24", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ava Morris", "role": "creative lead"}, {"name": "Noah Shah", "role": "stakeholder"}, {"name": "Ivy Patel", "role": "operations owner"}, {"name": "Isla Shah", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Ava 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": "Noah Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ivy Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a teaser-first cut for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Morris"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Shah"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Patel"}], "reference_action_items": [{"owner": "Ava Morris", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Isla Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Ava Morris"}, {"owner": "Noah Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Patel will send the updated recap and propose a short review before 2026-04-24, while Ava Morris revises the brief and Isla Shah prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0083", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Velora Motion", "meeting_type": "retrospective", "meeting_date": "2026-05-01", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Mia Chen", "role": "creative lead"}, {"name": "Zoe Lopez", "role": "stakeholder"}, {"name": "Nora Walker", "role": "operations owner"}, {"name": "Ivy Nguyen", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Mia Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Zoe Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Nora Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Zoe Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Zoe Lopez"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Walker"}], "reference_action_items": [{"owner": "Mia Chen", "role": "creative lead", "task": "Revise the retrospective brief around a tighter pilot package.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Ivy Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Mia Chen"}, {"owner": "Zoe Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion 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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Walker will send the updated recap and propose a short review before 2026-04-25, while Mia Chen revises the brief and Ivy Nguyen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0084", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "retrospective", "meeting_date": "2026-04-24", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Noah Brooks", "role": "creative lead"}, {"name": "Liam Diaz", "role": "stakeholder"}, {"name": "Zoe Morris", "role": "operations owner"}, {"name": "Lucas Lopez", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Noah Brooks", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for retrospective. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Liam Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Zoe Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Lucas Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Lucas Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Brooks"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Liam Diaz"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Morris"}], "reference_action_items": [{"owner": "Noah Brooks", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Lucas Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Noah Brooks"}, {"owner": "Liam Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Orbit Thread 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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Morris will send the updated recap and propose a short review before 2026-04-26, while Noah Brooks revises the brief and Lucas Lopez prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0085", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "creative review", "meeting_date": "2026-04-24", "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": "Jalen Lopez", "role": "creative lead"}, {"name": "Elijah Walker", "role": "stakeholder"}, {"name": "Zoe Walker", "role": "operations owner"}, {"name": "Ava Chen", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Jalen 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-04-24."}, {"speaker": "Elijah Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Zoe Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Lopez", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Lopez"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Walker"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Walker"}], "reference_action_items": [{"owner": "Jalen Lopez", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Ava Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Jalen Lopez"}, {"owner": "Elijah Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Walker will send the updated recap and propose a short review before 2026-04-27, while Jalen Lopez revises the brief and Ava Chen prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0086", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "campaign planning", "meeting_date": "2026-04-24", "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 Morris", "role": "creative lead"}, {"name": "Zoe Morris", "role": "stakeholder"}, {"name": "Zoe Rivera", "role": "operations owner"}, {"name": "Elijah Walker", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Jalen 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-24."}, {"speaker": "Zoe Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Zoe Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Zoe Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Morris"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Zoe Morris"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Rivera"}], "reference_action_items": [{"owner": "Jalen Morris", "role": "creative lead", "task": "Revise the campaign planning brief around a proof-first recap.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Elijah Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Jalen Morris"}, {"owner": "Zoe Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay 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 stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Rivera will send the updated recap and propose a short review before 2026-04-28, while Jalen Morris revises the brief and Elijah Walker prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0087", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Velora Motion", "meeting_type": "retrospective", "meeting_date": "2026-05-12", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ivy Rivera", "role": "creative lead"}, {"name": "Ava Walker", "role": "stakeholder"}, {"name": "Lucas Brooks", "role": "operations owner"}, {"name": "Isla Kim", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Ivy 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-12."}, {"speaker": "Ava Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Lucas Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 and alignment before expanding scope.", "owner": "Ava Walker"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Brooks"}], "reference_action_items": [{"owner": "Ivy Rivera", "role": "creative lead", "task": "Revise the retrospective brief around a proof-first recap.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Isla Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Ivy Rivera"}, {"owner": "Ava Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Brooks will send the updated recap and propose a short review before 2026-04-16, while Ivy Rivera revises the brief and Isla Kim prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0088", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "client onboarding", "meeting_date": "2026-04-22", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Lopez", "role": "creative lead"}, {"name": "Elijah Chen", "role": "stakeholder"}, {"name": "Ethan Shah", "role": "operations owner"}, {"name": "Nora Morris", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Lucas 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-04-22."}, {"speaker": "Elijah Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ethan Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Lopez", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Elijah Chen"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Shah"}], "reference_action_items": [{"owner": "Lucas Lopez", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Nora Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Lucas Lopez"}, {"owner": "Elijah Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Shah will send the updated recap and propose a short review before 2026-04-17, while Lucas Lopez revises the brief and Nora Morris prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0089", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "client onboarding", "meeting_date": "2026-05-01", "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": "Isla Brooks", "role": "creative lead"}, {"name": "Sofia Walker", "role": "stakeholder"}, {"name": "Ivy Morgan", "role": "operations owner"}, {"name": "Nora Patel", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Isla Brooks", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Sofia Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Ivy Morgan", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Isla Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Morgan", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 and alignment before expanding scope.", "owner": "Sofia Walker"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Morgan"}], "reference_action_items": [{"owner": "Isla Brooks", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Nora Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Isla Brooks"}, {"owner": "Sofia Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Morgan", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Lattice Harbor client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Morgan will send the updated recap and propose a short review before 2026-04-18, while Isla Brooks revises the brief and Nora Patel prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0090", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "vendor sync", "meeting_date": "2026-05-08", "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": "Ava Morgan", "role": "creative lead"}, {"name": "Noah Brooks", "role": "stakeholder"}, {"name": "Sofia Rivera", "role": "operations owner"}, {"name": "Nora Morris", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Ava 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": "Noah Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Morgan", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Morgan"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Brooks"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Rivera"}], "reference_action_items": [{"owner": "Ava Morgan", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Nora Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Ava Morgan"}, {"owner": "Noah Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Rivera will send the updated recap and propose a short review before 2026-04-19, while Ava Morgan revises the brief and Nora Morris prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0091", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "retrospective", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ethan Chen", "role": "creative lead"}, {"name": "Lucas Brooks", "role": "stakeholder"}, {"name": "Noah Diaz", "role": "operations owner"}, {"name": "Jalen Patel", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Ethan 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-08."}, {"speaker": "Lucas Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Noah Diaz", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Noah Diaz", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ethan Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Lucas Brooks"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Noah Diaz"}], "reference_action_items": [{"owner": "Ethan Chen", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Jalen Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Ethan Chen"}, {"owner": "Lucas Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Noah Diaz", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Noah Diaz will send the updated recap and propose a short review before 2026-04-20, while Ethan Chen revises the brief and Jalen Patel prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0092", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "campaign planning", "meeting_date": "2026-04-22", "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": "Miles Chen", "role": "creative lead"}, {"name": "Ethan Chen", "role": "stakeholder"}, {"name": "Ava Nguyen", "role": "operations owner"}, {"name": "Ivy Diaz", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Miles Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-22."}, {"speaker": "Ethan Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ava Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Miles Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ethan Chen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Nguyen"}], "reference_action_items": [{"owner": "Miles Chen", "role": "creative lead", "task": "Revise the campaign planning brief around a teaser-first cut.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Ivy Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Miles Chen"}, {"owner": "Ethan Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Nguyen will send the updated recap and propose a short review before 2026-04-21, while Miles Chen revises the brief and Ivy Diaz prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0093", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Velora Motion", "meeting_type": "campaign planning", "meeting_date": "2026-04-28", "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": "Zoe Rivera", "role": "creative lead"}, {"name": "Ivy Lopez", "role": "stakeholder"}, {"name": "Sofia Nguyen", "role": "operations owner"}, {"name": "Nora Nguyen", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Zoe 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": "Ivy Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Zoe Rivera"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ivy Lopez"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Nguyen"}], "reference_action_items": [{"owner": "Zoe Rivera", "role": "creative lead", "task": "Revise the campaign planning brief around a teaser-first cut.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Nora Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Zoe Rivera"}, {"owner": "Ivy Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion campaign planning: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Nguyen will send the updated recap and propose a short review before 2026-04-22, while Zoe Rivera revises the brief and Nora Nguyen prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0094", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-05-12", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Isla Walker", "role": "creative lead"}, {"name": "Liam Walker", "role": "stakeholder"}, {"name": "Ethan Morris", "role": "operations owner"}, {"name": "Liam Morris", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Isla 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": "Liam Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ethan Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Isla Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Isla Walker"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Liam Walker"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Morris"}], "reference_action_items": [{"owner": "Isla Walker", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Liam Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Isla Walker"}, {"owner": "Liam Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative 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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Morris will send the updated recap and propose a short review before 2026-04-23, while Isla Walker revises the brief and Liam Morris prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0095", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Cinder Atlas", "meeting_type": "vendor sync", "meeting_date": "2026-05-08", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Ivy Nguyen", "role": "creative lead"}, {"name": "Jalen Nguyen", "role": "stakeholder"}, {"name": "Jalen Morris", "role": "operations owner"}, {"name": "Isla Morgan", "role": "editor"}], "source_artifacts": ["Cinder Atlas working brief", "Cinder Atlas approval thread", "Cinder Atlas review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Ivy Nguyen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-08."}, {"speaker": "Jalen Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ivy Nguyen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Nguyen"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Morris"}], "reference_action_items": [{"owner": "Ivy Nguyen", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Isla Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Ivy Nguyen"}, {"owner": "Jalen Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Cinder Atlas 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 still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Morris will send the updated recap and propose a short review before 2026-04-24, while Ivy Nguyen revises the brief and Isla Morgan prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0096", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "retrospective", "meeting_date": "2026-05-08", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Elijah Nguyen", "role": "creative lead"}, {"name": "Liam Lopez", "role": "stakeholder"}, {"name": "Sofia Walker", "role": "operations owner"}, {"name": "Ava Diaz", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Elijah 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-08."}, {"speaker": "Liam Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Liam Lopez"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Walker"}], "reference_action_items": [{"owner": "Elijah Nguyen", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Ava Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Elijah Nguyen"}, {"owner": "Liam Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay 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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Walker will send the updated recap and propose a short review before 2026-04-25, while Elijah Nguyen revises the brief and Ava Diaz prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0097", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Velora Motion", "meeting_type": "retrospective", "meeting_date": "2026-04-24", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Miles Morgan", "role": "creative lead"}, {"name": "Nora Lopez", "role": "stakeholder"}, {"name": "Ethan Shah", "role": "operations owner"}, {"name": "Elijah Patel", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Miles 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-24."}, {"speaker": "Nora Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Ethan Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Nora Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Morgan", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Miles Morgan"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Nora Lopez"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Shah"}], "reference_action_items": [{"owner": "Miles Morgan", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Elijah Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Miles Morgan"}, {"owner": "Nora Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Shah will send the updated recap and propose a short review before 2026-04-26, while Miles Morgan revises the brief and Elijah Patel prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0098", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "client onboarding", "meeting_date": "2026-04-28", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ava Patel", "role": "creative lead"}, {"name": "Ava Chen", "role": "stakeholder"}, {"name": "Elijah Nguyen", "role": "operations owner"}, {"name": "Miles Chen", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Ava 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-04-28."}, {"speaker": "Ava Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Elijah Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Miles Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Miles Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Patel"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ava Chen"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Nguyen"}], "reference_action_items": [{"owner": "Ava Patel", "role": "creative lead", "task": "Revise the client onboarding brief around a lightweight review draft.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Miles Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Ava Patel"}, {"owner": "Ava Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Nguyen will send the updated recap and propose a short review before 2026-04-27, while Ava Patel revises the brief and Miles Chen prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0099", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Harborline Works", "meeting_type": "campaign planning", "meeting_date": "2026-05-05", "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": "Mia Walker", "role": "creative lead"}, {"name": "Ivy Patel", "role": "stakeholder"}, {"name": "Ethan Shah", "role": "operations owner"}, {"name": "Sofia Diaz", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Mia 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-05."}, {"speaker": "Ivy Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ethan Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Walker"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ivy Patel"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Shah"}], "reference_action_items": [{"owner": "Mia Walker", "role": "creative lead", "task": "Revise the campaign planning brief around a proof-first recap.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Sofia Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Mia Walker"}, {"owner": "Ivy Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works 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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Shah will send the updated recap and propose a short review before 2026-04-28, while Mia Walker revises the brief and Sofia Diaz prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0100", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "campaign planning", "meeting_date": "2026-04-24", "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": "Sofia Rivera", "role": "creative lead"}, {"name": "Jalen Chen", "role": "stakeholder"}, {"name": "Sofia Brooks", "role": "operations owner"}, {"name": "Liam Diaz", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Sofia 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-24."}, {"speaker": "Jalen Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Sofia Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Liam Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Liam Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 wants proof and alignment before expanding scope.", "owner": "Jalen Chen"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Brooks"}], "reference_action_items": [{"owner": "Sofia Rivera", "role": "creative lead", "task": "Revise the campaign planning brief around a proof-first recap.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Liam Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Sofia Rivera"}, {"owner": "Jalen Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay 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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Brooks will send the updated recap and propose a short review before 2026-04-16, while Sofia Rivera revises the brief and Liam Diaz prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0101", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "campaign planning", "meeting_date": "2026-05-12", "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 Walker", "role": "creative lead"}, {"name": "Ethan Shah", "role": "stakeholder"}, {"name": "Zoe Chen", "role": "operations owner"}, {"name": "Elijah Lopez", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Noah 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 Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Zoe Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Walker"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ethan Shah"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Chen"}], "reference_action_items": [{"owner": "Noah Walker", "role": "creative lead", "task": "Revise the campaign planning brief around a lightweight review draft.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Elijah Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Noah Walker"}, {"owner": "Ethan Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Echoframe Media campaign planning: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Chen will send the updated recap and propose a short review before 2026-04-17, while Noah Walker revises the brief and Elijah Lopez prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0102", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "creative review", "meeting_date": "2026-04-28", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Noah Kim", "role": "creative lead"}, {"name": "Nora Morris", "role": "stakeholder"}, {"name": "Zoe Chen", "role": "operations owner"}, {"name": "Mia Patel", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Noah 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-04-28."}, {"speaker": "Nora Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Zoe Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Nora Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Kim"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Nora Morris"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Chen"}], "reference_action_items": [{"owner": "Noah Kim", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Mia Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Noah Kim"}, {"owner": "Nora Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Chen will send the updated recap and propose a short review before 2026-04-18, while Noah Kim revises the brief and Mia Patel prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0103", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "campaign planning", "meeting_date": "2026-05-01", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Noah Brooks", "role": "creative lead"}, {"name": "Sofia Diaz", "role": "stakeholder"}, {"name": "Liam Morris", "role": "operations owner"}, {"name": "Isla Morgan", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Noah 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-01."}, {"speaker": "Sofia Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Liam Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the campaign planning workstream so the project can move without reopening full scope. They agreed that the 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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Brooks"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Sofia Diaz"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Morris"}], "reference_action_items": [{"owner": "Noah Brooks", "role": "creative lead", "task": "Revise the campaign planning brief around a tighter pilot package.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Isla Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Noah Brooks"}, {"owner": "Sofia Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay campaign planning: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Morris will send the updated recap and propose a short review before 2026-04-19, while Noah Brooks revises the brief and Isla Morgan prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0104", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "client onboarding", "meeting_date": "2026-04-28", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Nguyen", "role": "creative lead"}, {"name": "Liam Chen", "role": "stakeholder"}, {"name": "Ava Shah", "role": "operations owner"}, {"name": "Lucas Chen", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Lucas Nguyen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-04-28."}, {"speaker": "Liam Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Ava Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Lucas Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Lucas Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Liam Chen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Shah"}], "reference_action_items": [{"owner": "Lucas Nguyen", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Lucas Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Lucas Nguyen"}, {"owner": "Liam Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Shah will send the updated recap and propose a short review before 2026-04-20, while Lucas Nguyen revises the brief and Lucas Chen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0105", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "retrospective", "meeting_date": "2026-04-24", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ethan Morris", "role": "creative lead"}, {"name": "Jalen Walker", "role": "stakeholder"}, {"name": "Elijah Kim", "role": "operations owner"}, {"name": "Ivy Shah", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Ethan 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": "Jalen Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Elijah Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a teaser-first cut for the retrospective workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ethan Morris"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Walker"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Kim"}], "reference_action_items": [{"owner": "Ethan Morris", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Ivy Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Ethan Morris"}, {"owner": "Jalen Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North Labs retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Kim will send the updated recap and propose a short review before 2026-04-21, while Ethan Morris revises the brief and Ivy Shah prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0106", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "retrospective", "meeting_date": "2026-05-08", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ivy Patel", "role": "creative lead"}, {"name": "Miles Diaz", "role": "stakeholder"}, {"name": "Miles Lopez", "role": "operations owner"}, {"name": "Elijah Rivera", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Ivy 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-08."}, {"speaker": "Miles Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Miles Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ivy Patel"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Miles Diaz"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Lopez"}], "reference_action_items": [{"owner": "Ivy Patel", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Elijah Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Ivy Patel"}, {"owner": "Miles Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Lopez will send the updated recap and propose a short review before 2026-04-22, while Ivy Patel revises the brief and Elijah Rivera prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0107", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Velora Motion", "meeting_type": "creative review", "meeting_date": "2026-05-12", "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": "Mia Patel", "role": "creative lead"}, {"name": "Sofia Lopez", "role": "stakeholder"}, {"name": "Ethan Brooks", "role": "operations owner"}, {"name": "Ivy Morgan", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Mia Patel", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-12."}, {"speaker": "Sofia Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ethan Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a teaser-first cut for the creative review workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Patel"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Sofia Lopez"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Brooks"}], "reference_action_items": [{"owner": "Mia Patel", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Ivy Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Mia Patel"}, {"owner": "Sofia Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion creative review: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Brooks will send the updated recap and propose a short review before 2026-04-23, while Mia Patel revises the brief and Ivy Morgan prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0108", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "campaign planning", "meeting_date": "2026-05-12", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Isla Rivera", "role": "creative lead"}, {"name": "Jalen Kim", "role": "stakeholder"}, {"name": "Nora Lopez", "role": "operations owner"}, {"name": "Ava Morris", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Isla Rivera", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-12."}, {"speaker": "Jalen Kim", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Nora Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Kim", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Isla Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 and alignment before expanding scope.", "owner": "Jalen Kim"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Lopez"}], "reference_action_items": [{"owner": "Isla Rivera", "role": "creative lead", "task": "Revise the campaign planning brief around a teaser-first cut.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Ava Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Isla Rivera"}, {"owner": "Jalen Kim", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Lattice Harbor campaign planning: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Lopez will send the updated recap and propose a short review before 2026-04-24, while Isla Rivera revises the brief and Ava Morris prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0109", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Velora Motion", "meeting_type": "retrospective", "meeting_date": "2026-05-12", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ava Chen", "role": "creative lead"}, {"name": "Lucas Rivera", "role": "stakeholder"}, {"name": "Jalen Morris", "role": "operations owner"}, {"name": "Elijah Patel", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Ava 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": "Lucas Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Lucas Rivera"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Morris"}], "reference_action_items": [{"owner": "Ava Chen", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Elijah Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Ava Chen"}, {"owner": "Lucas Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Morris will send the updated recap and propose a short review before 2026-04-25, while Ava Chen revises the brief and Elijah Patel prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0110", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Jalen Chen", "role": "creative lead"}, {"name": "Sofia Brooks", "role": "stakeholder"}, {"name": "Noah Walker", "role": "operations owner"}, {"name": "Ivy Brooks", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Jalen Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-22."}, {"speaker": "Sofia Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Noah Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Brooks", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Noah Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Brooks", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Sofia Brooks"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Noah Walker"}], "reference_action_items": [{"owner": "Jalen Chen", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Ivy Brooks", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Jalen Chen"}, {"owner": "Sofia Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Noah Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative 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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Noah Walker will send the updated recap and propose a short review before 2026-04-26, while Jalen Chen revises the brief and Ivy Brooks prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0111", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "vendor sync", "meeting_date": "2026-05-08", "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 Nguyen", "role": "creative lead"}, {"name": "Sofia Brooks", "role": "stakeholder"}, {"name": "Sofia Kim", "role": "operations owner"}, {"name": "Ethan Rivera", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Mia Nguyen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-08."}, {"speaker": "Sofia Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Sofia Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the vendor sync workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 and alignment before expanding scope.", "owner": "Sofia Brooks"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Kim"}], "reference_action_items": [{"owner": "Mia Nguyen", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Ethan Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Mia Nguyen"}, {"owner": "Sofia Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Kim will send the updated recap and propose a short review before 2026-04-27, while Mia Nguyen revises the brief and Ethan Rivera prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0112", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "vendor sync", "meeting_date": "2026-04-28", "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 Nguyen", "role": "creative lead"}, {"name": "Noah Nguyen", "role": "stakeholder"}, {"name": "Nora Nguyen", "role": "operations owner"}, {"name": "Sofia Shah", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Zoe 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": "Noah Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Nora Nguyen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Zoe Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Nguyen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Zoe Nguyen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Nguyen"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Nguyen"}], "reference_action_items": [{"owner": "Zoe Nguyen", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Sofia Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Zoe Nguyen"}, {"owner": "Noah Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Nguyen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Nguyen will send the updated recap and propose a short review before 2026-04-28, while Zoe Nguyen revises the brief and Sofia Shah prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0113", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "vendor sync", "meeting_date": "2026-05-05", "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 Morris", "role": "creative lead"}, {"name": "Liam Chen", "role": "stakeholder"}, {"name": "Isla Lopez", "role": "operations owner"}, {"name": "Noah Shah", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Elijah Morris", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-05."}, {"speaker": "Liam Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Isla Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Isla Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 wants proof and alignment before expanding scope.", "owner": "Liam Chen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Isla Lopez"}], "reference_action_items": [{"owner": "Elijah Morris", "role": "creative lead", "task": "Revise the vendor sync brief around a tighter pilot package.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Noah Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Elijah Morris"}, {"owner": "Liam Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Isla Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Isla Lopez will send the updated recap and propose a short review before 2026-04-16, while Elijah Morris revises the brief and Noah Shah prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0114", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "vendor sync", "meeting_date": "2026-05-01", "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 Rivera", "role": "creative lead"}, {"name": "Ivy Patel", "role": "stakeholder"}, {"name": "Ava Lopez", "role": "operations owner"}, {"name": "Elijah Chen", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Jalen 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": "Ivy Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Ava Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 proof and alignment before expanding scope.", "owner": "Ivy Patel"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Lopez"}], "reference_action_items": [{"owner": "Jalen Rivera", "role": "creative lead", "task": "Revise the vendor sync brief around a tighter pilot package.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Elijah Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Jalen Rivera"}, {"owner": "Ivy Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Lopez will send the updated recap and propose a short review before 2026-04-17, while Jalen Rivera revises the brief and Elijah Chen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0115", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "retrospective", "meeting_date": "2026-05-15", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Nora Shah", "role": "creative lead"}, {"name": "Ava Brooks", "role": "stakeholder"}, {"name": "Elijah Kim", "role": "operations owner"}, {"name": "Ava Morris", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Nora 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-05-15."}, {"speaker": "Ava Brooks", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Elijah Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ava Morris", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Brooks", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Nora Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ava Morris", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Nora Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ava Brooks"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Kim"}], "reference_action_items": [{"owner": "Nora Shah", "role": "creative lead", "task": "Revise the retrospective brief around a lightweight review draft.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Ava Morris", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Nora Shah"}, {"owner": "Ava Brooks", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay 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 stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Kim will send the updated recap and propose a short review before 2026-04-18, while Nora Shah revises the brief and Ava Morris prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0116", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-05-01", "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 Kim", "role": "creative lead"}, {"name": "Noah Shah", "role": "stakeholder"}, {"name": "Noah Chen", "role": "operations owner"}, {"name": "Sofia Morgan", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Liam Kim", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Noah Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Noah Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Liam Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Noah Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Liam Kim"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Shah"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Noah Chen"}], "reference_action_items": [{"owner": "Liam Kim", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Sofia Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Liam Kim"}, {"owner": "Noah Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Noah Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative 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 wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Noah Chen will send the updated recap and propose a short review before 2026-04-19, while Liam Kim revises the brief and Sofia Morgan prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0117", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-04-24", "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 Kim", "role": "creative lead"}, {"name": "Miles Patel", "role": "stakeholder"}, {"name": "Lucas Diaz", "role": "operations owner"}, {"name": "Elijah Nguyen", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Miles Kim", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Miles Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Lucas Diaz", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Diaz", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Miles Kim"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Miles Patel"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Diaz"}], "reference_action_items": [{"owner": "Miles Kim", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Elijah Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Miles Kim"}, {"owner": "Miles Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Diaz", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Diaz will send the updated recap and propose a short review before 2026-04-20, while Miles Kim revises the brief and Elijah Nguyen prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0118", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "retrospective", "meeting_date": "2026-04-22", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Ivy Morris", "role": "creative lead"}, {"name": "Mia Rivera", "role": "stakeholder"}, {"name": "Ethan Patel", "role": "operations owner"}, {"name": "Jalen Kim", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"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-22."}, {"speaker": "Mia Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ethan Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ivy Morris"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Mia Rivera"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Patel"}], "reference_action_items": [{"owner": "Ivy Morris", "role": "creative lead", "task": "Revise the retrospective brief around a teaser-first cut.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Jalen Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Ivy Morris"}, {"owner": "Mia Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Patel will send the updated recap and propose a short review before 2026-04-21, while Ivy Morris revises the brief and Jalen Kim prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0119", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Nora Nguyen", "role": "creative lead"}, {"name": "Noah Morris", "role": "stakeholder"}, {"name": "Elijah Walker", "role": "operations owner"}, {"name": "Lucas Walker", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Nora Nguyen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-22."}, {"speaker": "Noah Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Elijah Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Lucas Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Nora Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Lucas Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package 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 wants proof and alignment before expanding scope.", "owner": "Noah Morris"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Walker"}], "reference_action_items": [{"owner": "Nora Nguyen", "role": "creative lead", "task": "Revise the vendor sync brief around a tighter pilot package.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Lucas Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Nora Nguyen"}, {"owner": "Noah Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Walker will send the updated recap and propose a short review before 2026-04-22, while Nora Nguyen revises the brief and Lucas Walker prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0120", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "creative review", "meeting_date": "2026-05-15", "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", "role": "creative lead"}, {"name": "Jalen Chen", "role": "stakeholder"}, {"name": "Zoe Shah", "role": "operations owner"}, {"name": "Noah Chen", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"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-15."}, {"speaker": "Jalen Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Zoe Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a lightweight review draft for the creative review workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft 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 proof and alignment before expanding scope.", "owner": "Jalen Chen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Shah"}], "reference_action_items": [{"owner": "Jalen Kim", "role": "creative lead", "task": "Revise the creative review brief around a lightweight review draft.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Noah Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Jalen Kim"}, {"owner": "Jalen Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Shah will send the updated recap and propose a short review before 2026-04-23, while Jalen Kim revises the brief and Noah Chen prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0121", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "creative review", "meeting_date": "2026-05-15", "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": "Noah Walker", "role": "creative lead"}, {"name": "Noah Patel", "role": "stakeholder"}, {"name": "Zoe Patel", "role": "operations owner"}, {"name": "Noah Shah", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Noah Walker", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-15."}, {"speaker": "Noah Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Zoe Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the creative review workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Noah Walker"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Patel"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Patel"}], "reference_action_items": [{"owner": "Noah Walker", "role": "creative lead", "task": "Revise the creative review brief around a proof-first recap.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Noah Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Noah Walker"}, {"owner": "Noah Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Patel will send the updated recap and propose a short review before 2026-04-24, while Noah Walker revises the brief and Noah Shah prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0122", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "campaign planning", "meeting_date": "2026-04-28", "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 Nguyen", "role": "creative lead"}, {"name": "Noah Diaz", "role": "stakeholder"}, {"name": "Isla Patel", "role": "operations owner"}, {"name": "Mia Brooks", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Ivy Nguyen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-28."}, {"speaker": "Noah Diaz", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Isla Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Brooks", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Diaz", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Isla Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Brooks", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ivy Nguyen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Diaz"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Isla Patel"}], "reference_action_items": [{"owner": "Ivy Nguyen", "role": "creative lead", "task": "Revise the campaign planning brief around a lightweight review draft.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Mia Brooks", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Ivy Nguyen"}, {"owner": "Noah Diaz", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Isla Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Isla Patel will send the updated recap and propose a short review before 2026-04-25, while Ivy Nguyen revises the brief and Mia Brooks prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0123", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "campaign planning", "meeting_date": "2026-04-28", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Mia Walker", "role": "creative lead"}, {"name": "Ethan Chen", "role": "stakeholder"}, {"name": "Elijah Shah", "role": "operations owner"}, {"name": "Lucas Shah", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Mia Walker", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-28."}, {"speaker": "Ethan Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Elijah Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Lucas Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Elijah Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Lucas Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Walker"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ethan Chen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Elijah Shah"}], "reference_action_items": [{"owner": "Mia Walker", "role": "creative lead", "task": "Revise the campaign planning brief around a lightweight review draft.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Lucas Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Mia Walker"}, {"owner": "Ethan Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Elijah Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Elijah Shah will send the updated recap and propose a short review before 2026-04-26, while Mia Walker revises the brief and Lucas Shah prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0124", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Signal Oak", "meeting_type": "campaign planning", "meeting_date": "2026-05-05", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Nora Shah", "role": "creative lead"}, {"name": "Ava Patel", "role": "stakeholder"}, {"name": "Liam Patel", "role": "operations owner"}, {"name": "Mia Morgan", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Nora 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-05."}, {"speaker": "Ava Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Liam Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ava Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Nora Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Nora Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ava Patel"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Patel"}], "reference_action_items": [{"owner": "Nora Shah", "role": "creative lead", "task": "Revise the campaign planning brief around a proof-first recap.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Mia Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Nora Shah"}, {"owner": "Ava Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Patel will send the updated recap and propose a short review before 2026-04-27, while Nora Shah revises the brief and Mia Morgan prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0125", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "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": "Sofia Lopez", "role": "creative lead"}, {"name": "Elijah Shah", "role": "stakeholder"}, {"name": "Sofia Walker", "role": "operations owner"}, {"name": "Sofia Chen", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Sofia 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": "Elijah Shah", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Shah", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Lopez", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Sofia Lopez"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Shah"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Walker"}], "reference_action_items": [{"owner": "Sofia Lopez", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Sofia Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Sofia Lopez"}, {"owner": "Elijah Shah", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Walker will send the updated recap and propose a short review before 2026-04-28, while Sofia Lopez revises the brief and Sofia Chen prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0126", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Velora Motion", "meeting_type": "vendor sync", "meeting_date": "2026-05-01", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Mia Brooks", "role": "creative lead"}, {"name": "Zoe Walker", "role": "stakeholder"}, {"name": "Ava Patel", "role": "operations owner"}, {"name": "Nora Nguyen", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Mia Brooks", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Zoe Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ava Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Zoe Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Brooks", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ava Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Brooks"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Zoe Walker"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ava Patel"}], "reference_action_items": [{"owner": "Mia Brooks", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Nora Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Mia Brooks"}, {"owner": "Zoe Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Ava Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion 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 still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ava Patel will send the updated recap and propose a short review before 2026-04-16, while Mia Brooks revises the brief and Nora Nguyen prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0127", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Velora Motion", "meeting_type": "creative review", "meeting_date": "2026-05-08", "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": "Jalen Diaz", "role": "creative lead"}, {"name": "Liam Chen", "role": "stakeholder"}, {"name": "Sofia Brooks", "role": "operations owner"}, {"name": "Noah Nguyen", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Jalen 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-08."}, {"speaker": "Liam Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Sofia Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Liam Chen"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Brooks"}], "reference_action_items": [{"owner": "Jalen Diaz", "role": "creative lead", "task": "Revise the creative review brief around a tighter pilot package.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Noah Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Jalen Diaz"}, {"owner": "Liam Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Velora Motion 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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Brooks will send the updated recap and propose a short review before 2026-04-17, while Jalen Diaz revises the brief and Noah Nguyen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0128", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "campaign planning", "meeting_date": "2026-04-24", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Nguyen", "role": "creative lead"}, {"name": "Ethan Lopez", "role": "stakeholder"}, {"name": "Ethan Diaz", "role": "operations owner"}, {"name": "Ethan Chen", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Lucas Nguyen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-04-24."}, {"speaker": "Ethan Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ethan Diaz", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ethan Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Diaz", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Nguyen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ethan Lopez"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Diaz"}], "reference_action_items": [{"owner": "Lucas Nguyen", "role": "creative lead", "task": "Revise the campaign planning brief around a proof-first recap.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Ethan Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Lucas Nguyen"}, {"owner": "Ethan Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Diaz", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay 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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Diaz will send the updated recap and propose a short review before 2026-04-18, while Lucas Nguyen revises the brief and Ethan Chen prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0129", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "creative review", "meeting_date": "2026-04-24", "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": "Ivy Shah", "role": "creative lead"}, {"name": "Mia Nguyen", "role": "stakeholder"}, {"name": "Zoe Walker", "role": "operations owner"}, {"name": "Isla Nguyen", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Ivy 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": "Mia Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Zoe Walker", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Isla Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Shah", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Walker", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Isla Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ivy Shah"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Mia Nguyen"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Walker"}], "reference_action_items": [{"owner": "Ivy Shah", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Isla Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Ivy Shah"}, {"owner": "Mia Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Walker", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs 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 approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Walker will send the updated recap and propose a short review before 2026-04-19, while Ivy Shah revises the brief and Isla Nguyen prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0130", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "campaign planning", "meeting_date": "2026-05-01", "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": "Noah Diaz", "role": "creative lead"}, {"name": "Miles Patel", "role": "stakeholder"}, {"name": "Ivy Kim", "role": "operations owner"}, {"name": "Zoe Lopez", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Noah Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Miles Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Ivy Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Zoe Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Noah Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Zoe Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the campaign planning workstream so the project can move without reopening full scope. They agreed that the 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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Miles Patel"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Kim"}], "reference_action_items": [{"owner": "Noah Diaz", "role": "creative lead", "task": "Revise the campaign planning brief around a tighter pilot package.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Zoe Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Noah Diaz"}, {"owner": "Miles Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Kim will send the updated recap and propose a short review before 2026-04-20, while Noah Diaz revises the brief and Zoe Lopez prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0131", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Mia Rivera", "role": "creative lead"}, {"name": "Lucas Morgan", "role": "stakeholder"}, {"name": "Liam Lopez", "role": "operations owner"}, {"name": "Ivy Lopez", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Mia 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": "Lucas Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Liam Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Lucas Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Rivera", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Liam Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Rivera"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Lucas Morgan"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Liam Lopez"}], "reference_action_items": [{"owner": "Mia Rivera", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Ivy Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Mia Rivera"}, {"owner": "Lucas Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Liam Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative 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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Liam Lopez will send the updated recap and propose a short review before 2026-04-21, while Mia Rivera revises the brief and Ivy Lopez prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0132", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Glowforge Labs", "meeting_type": "retrospective", "meeting_date": "2026-05-05", "channel": "conference room review", "objective": "Use the meeting to narrow the first deliverable for retrospective without losing the proof or hiding blockers.", "participants": [{"name": "Sofia Chen", "role": "creative lead"}, {"name": "Ivy Nguyen", "role": "stakeholder"}, {"name": "Lucas Patel", "role": "operations owner"}, {"name": "Noah Walker", "role": "editor"}], "source_artifacts": ["Glowforge Labs working brief", "Glowforge Labs approval thread", "Glowforge Labs review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Sofia 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-05."}, {"speaker": "Ivy Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Lucas Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Noah Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Sofia Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Lucas Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Noah Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the retrospective workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Sofia Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ivy Nguyen"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Lucas Patel"}], "reference_action_items": [{"owner": "Sofia Chen", "role": "creative lead", "task": "Revise the retrospective brief around a tighter pilot package.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Noah Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Sofia Chen"}, {"owner": "Ivy Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Lucas Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Glowforge Labs retrospective: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for retrospective, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Lucas Patel will send the updated recap and propose a short review before 2026-04-22, while Sofia Chen revises the brief and Noah Walker prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0133", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Northbeam Studio", "meeting_type": "client onboarding", "meeting_date": "2026-04-28", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Ava Morris", "role": "creative lead"}, {"name": "Ivy Rivera", "role": "stakeholder"}, {"name": "Zoe Rivera", "role": "operations owner"}, {"name": "Elijah Brooks", "role": "editor"}], "source_artifacts": ["Northbeam Studio working brief", "Northbeam Studio approval thread", "Northbeam Studio review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Ava 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": "Ivy Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Zoe Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Elijah Brooks", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Ava Morris", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Elijah Brooks", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the client onboarding workstream so the project can move without reopening full scope. They agreed that legal language is still pending is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ava Morris"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ivy Rivera"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Rivera"}], "reference_action_items": [{"owner": "Ava Morris", "role": "creative lead", "task": "Revise the client onboarding brief around a proof-first recap.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Elijah Brooks", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Ava Morris"}, {"owner": "Ivy Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Northbeam Studio client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Rivera will send the updated recap and propose a short review before 2026-04-23, while Ava Morris revises the brief and Elijah Brooks prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Northbeam Studio launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0134", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "creative review", "meeting_date": "2026-05-05", "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": "Ethan Lopez", "role": "creative lead"}, {"name": "Ivy Nguyen", "role": "stakeholder"}, {"name": "Ethan Chen", "role": "operations owner"}, {"name": "Sofia Morgan", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Ethan Lopez", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-05-05."}, {"speaker": "Ivy Nguyen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ethan Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Nguyen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ethan Lopez", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ethan Lopez"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Ivy Nguyen"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Chen"}], "reference_action_items": [{"owner": "Ethan Lopez", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Sofia Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Ethan Lopez"}, {"owner": "Ivy Nguyen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North Labs 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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Chen will send the updated recap and propose a short review before 2026-04-24, while Ethan Lopez revises the brief and Sofia Morgan prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0135", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "vendor sync", "meeting_date": "2026-04-28", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Elijah Kim", "role": "creative lead"}, {"name": "Ivy Patel", "role": "stakeholder"}, {"name": "Ethan Diaz", "role": "operations owner"}, {"name": "Ethan Rivera", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"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-04-28."}, {"speaker": "Ivy Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ethan Diaz", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Ivy Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Diaz", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap 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 wants proof and alignment before expanding scope.", "owner": "Ivy Patel"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Diaz"}], "reference_action_items": [{"owner": "Elijah Kim", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Ethan Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Elijah Kim"}, {"owner": "Ivy Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Diaz", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Lattice Harbor 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 still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Diaz will send the updated recap and propose a short review before 2026-04-25, while Elijah Kim revises the brief and Ethan Rivera prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0136", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "client onboarding", "meeting_date": "2026-05-12", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Elijah Patel", "role": "creative lead"}, {"name": "Mia Kim", "role": "stakeholder"}, {"name": "Noah Diaz", "role": "operations owner"}, {"name": "Zoe Diaz", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Elijah 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-12."}, {"speaker": "Mia Kim", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Noah Diaz", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Zoe Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Mia Kim", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Elijah Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Noah Diaz", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Zoe Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the client onboarding workstream so the project can move without reopening full scope. They agreed that two stakeholders still disagree on scope is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Mia Kim"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Noah Diaz"}], "reference_action_items": [{"owner": "Elijah Patel", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Zoe Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Elijah Patel"}, {"owner": "Mia Kim", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Noah Diaz", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a tighter pilot package as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Noah Diaz will send the updated recap and propose a short review before 2026-04-26, while Elijah Patel revises the brief and Zoe Diaz prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0137", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "campaign planning", "meeting_date": "2026-05-05", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Mia Diaz", "role": "creative lead"}, {"name": "Jalen Morgan", "role": "stakeholder"}, {"name": "Miles Shah", "role": "operations owner"}, {"name": "Ivy Morgan", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Mia Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for campaign planning. Right now the draft is too broad for the review window on 2026-05-05."}, {"speaker": "Jalen Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Miles Shah", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Morgan", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Shah", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-27. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Morgan", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Morgan"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Shah"}], "reference_action_items": [{"owner": "Mia Diaz", "role": "creative lead", "task": "Revise the campaign planning brief around a teaser-first cut.", "due_date": "2026-04-27", "depends_on": "None"}, {"owner": "Ivy Morgan", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-16", "depends_on": "Updated brief from Mia Diaz"}, {"owner": "Jalen Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-27", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Shah", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-28", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative campaign planning: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for campaign planning, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Shah will send the updated recap and propose a short review before 2026-04-27, while Mia Diaz revises the brief and Ivy Morgan prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0138", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Juniper Relay", "meeting_type": "client onboarding", "meeting_date": "2026-05-05", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Mia Walker", "role": "creative lead"}, {"name": "Sofia Rivera", "role": "stakeholder"}, {"name": "Mia Lopez", "role": "operations owner"}, {"name": "Lucas Rivera", "role": "editor"}], "source_artifacts": ["Juniper Relay working brief", "Juniper Relay approval thread", "Juniper Relay review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Mia Walker", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-05."}, {"speaker": "Sofia Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Mia Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Lucas Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Sofia Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Walker", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Mia Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-28. I will also log the blocker explicitly in the tracker."}, {"speaker": "Lucas Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a lightweight review draft for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Walker"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Sofia Rivera"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Mia Lopez"}], "reference_action_items": [{"owner": "Mia Walker", "role": "creative lead", "task": "Revise the client onboarding brief around a lightweight review draft.", "due_date": "2026-04-28", "depends_on": "None"}, {"owner": "Lucas Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-17", "depends_on": "Updated brief from Mia Walker"}, {"owner": "Sofia Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-28", "depends_on": "Internal stakeholder availability"}, {"owner": "Mia Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-16", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Juniper Relay client onboarding: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a lightweight review draft as the first deliverable for client onboarding, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Mia Lopez will send the updated recap and propose a short review before 2026-04-28, while Mia Walker revises the brief and Lucas Rivera prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0139", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Velora Motion", "meeting_type": "vendor sync", "meeting_date": "2026-05-01", "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 Diaz", "role": "creative lead"}, {"name": "Noah Walker", "role": "stakeholder"}, {"name": "Ethan Brooks", "role": "operations owner"}, {"name": "Jalen Patel", "role": "editor"}], "source_artifacts": ["Velora Motion working brief", "Velora Motion approval thread", "Velora Motion review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Jalen Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Noah Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ethan Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Patel", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Noah Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ethan Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-16. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Patel", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Noah Walker"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ethan Brooks"}], "reference_action_items": [{"owner": "Jalen Diaz", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-16", "depends_on": "None"}, {"owner": "Jalen Patel", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-18", "depends_on": "Updated brief from Jalen Diaz"}, {"owner": "Noah Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-16", "depends_on": "Internal stakeholder availability"}, {"owner": "Ethan Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-17", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Ethan Brooks will send the updated recap and propose a short review before 2026-04-16, while Jalen Diaz revises the brief and Jalen Patel prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0140", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "vendor sync", "meeting_date": "2026-05-01", "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 Diaz", "role": "creative lead"}, {"name": "Miles Morris", "role": "stakeholder"}, {"name": "Mia Diaz", "role": "operations owner"}, {"name": "Ethan Lopez", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Jalen Diaz", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-01."}, {"speaker": "Miles Morris", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Mia Diaz", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that legal language is still pending. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Morris", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Mia Diaz", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-17. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["legal language is still pending", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Jalen Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Miles Morris"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Mia Diaz"}], "reference_action_items": [{"owner": "Jalen Diaz", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-17", "depends_on": "None"}, {"owner": "Ethan Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-19", "depends_on": "Updated brief from Jalen Diaz"}, {"owner": "Miles Morris", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-17", "depends_on": "Internal stakeholder availability"}, {"owner": "Mia Diaz", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-18", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "First Mile Creative 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 legal language is still pending, so the recap and review request should stay practical rather than overstate certainty. Next step: Mia Diaz will send the updated recap and propose a short review before 2026-04-17, while Jalen Diaz revises the brief and Ethan Lopez prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: legal language is still pending. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0141", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "client onboarding", "meeting_date": "2026-05-12", "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 Kim", "role": "creative lead"}, {"name": "Elijah Patel", "role": "stakeholder"}, {"name": "Zoe Patel", "role": "operations owner"}, {"name": "Mia Walker", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Jalen Kim", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for client onboarding. Right now the draft is too broad for the review window on 2026-05-12."}, {"speaker": "Elijah Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Zoe Patel", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Walker", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Jalen Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Patel", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-18. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Walker", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 the next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"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 proof and alignment before expanding scope.", "owner": "Elijah Patel"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Patel"}], "reference_action_items": [{"owner": "Jalen Kim", "role": "creative lead", "task": "Revise the client onboarding brief around a tighter pilot package.", "due_date": "2026-04-18", "depends_on": "None"}, {"owner": "Mia Walker", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-20", "depends_on": "Updated brief from Jalen Kim"}, {"owner": "Elijah Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-18", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Patel", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-19", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Orbit Thread 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 the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Patel will send the updated recap and propose a short review before 2026-04-18, while Jalen Kim revises the brief and Mia Walker prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0142", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Tidal North Labs", "meeting_type": "vendor sync", "meeting_date": "2026-05-12", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Nora Patel", "role": "creative lead"}, {"name": "Elijah Chen", "role": "stakeholder"}, {"name": "Sofia Lopez", "role": "operations owner"}, {"name": "Ivy Rivera", "role": "editor"}], "source_artifacts": ["Tidal North Labs working brief", "Tidal North Labs approval thread", "Tidal North Labs review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Nora 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-12."}, {"speaker": "Elijah Chen", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Sofia Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Rivera", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Chen", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Nora Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-19. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Rivera", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Nora Patel"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Chen"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Lopez"}], "reference_action_items": [{"owner": "Nora Patel", "role": "creative lead", "task": "Revise the vendor sync brief around a teaser-first cut.", "due_date": "2026-04-19", "depends_on": "None"}, {"owner": "Ivy Rivera", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-21", "depends_on": "Updated brief from Nora Patel"}, {"owner": "Elijah Chen", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-19", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-20", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Tidal North Labs vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Lopez will send the updated recap and propose a short review before 2026-04-19, while Nora Patel revises the brief and Ivy Rivera prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 North Labs launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0143", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Orbit Thread", "meeting_type": "creative review", "meeting_date": "2026-04-22", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Ivy Nguyen", "role": "creative lead"}, {"name": "Isla Morgan", "role": "stakeholder"}, {"name": "Nora Chen", "role": "operations owner"}, {"name": "Jalen Kim", "role": "editor"}], "source_artifacts": ["Orbit Thread working brief", "Orbit Thread approval thread", "Orbit Thread review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Ivy Nguyen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for creative review. Right now the draft is too broad for the review window on 2026-04-22."}, {"speaker": "Isla Morgan", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Nora Chen", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Kim", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Isla Morgan", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Ivy Nguyen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Nora Chen", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-20. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Kim", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 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 making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Ivy Nguyen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Isla Morgan"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Nora Chen"}], "reference_action_items": [{"owner": "Ivy Nguyen", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-20", "depends_on": "None"}, {"owner": "Jalen Kim", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-22", "depends_on": "Updated brief from Ivy Nguyen"}, {"owner": "Isla Morgan", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-20", "depends_on": "Internal stakeholder availability"}, {"owner": "Nora Chen", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-21", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Nora Chen will send the updated recap and propose a short review before 2026-04-20, while Ivy Nguyen revises the brief and Jalen Kim prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0144", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "campaign planning", "meeting_date": "2026-04-22", "channel": "Google Meet", "objective": "Use the meeting to narrow the first deliverable for campaign planning without losing the proof or hiding blockers.", "participants": [{"name": "Nora Kim", "role": "creative lead"}, {"name": "Jalen Kim", "role": "stakeholder"}, {"name": "Jalen Morris", "role": "operations owner"}, {"name": "Nora Lopez", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the first review under 30 minutes."}], "transcript": [{"speaker": "Nora 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-22."}, {"speaker": "Jalen Kim", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Nora Lopez", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Jalen Kim", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the first review under 30 minutes. I do not want a message that reads more resolved than we are."}, {"speaker": "Nora Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Jalen Morris", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-21. I will also log the blocker explicitly in the tracker."}, {"speaker": "Nora Lopez", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a tighter pilot package for the campaign planning workstream so the project can move without reopening full scope. They agreed that the 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 review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Nora Kim"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Jalen Kim"}, {"decision": "Keep the recap practical and keep the first review under 30 minutes.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Jalen Morris"}], "reference_action_items": [{"owner": "Nora Kim", "role": "creative lead", "task": "Revise the campaign planning brief around a tighter pilot package.", "due_date": "2026-04-21", "depends_on": "None"}, {"owner": "Nora Lopez", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-23", "depends_on": "Updated brief from Nora Kim"}, {"owner": "Jalen Kim", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-21", "depends_on": "Internal stakeholder availability"}, {"owner": "Jalen Morris", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-22", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Lattice Harbor 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 the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Jalen Morris will send the updated recap and propose a short review before 2026-04-21, while Nora Kim revises the brief and Nora Lopez prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the first review under 30 minutes."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0145", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.88, "meeting_context": {"brand": "First Mile Creative", "meeting_type": "client onboarding", "meeting_date": "2026-04-22", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for client onboarding without losing the proof or hiding blockers.", "participants": [{"name": "Lucas Patel", "role": "creative lead"}, {"name": "Zoe Walker", "role": "stakeholder"}, {"name": "Sofia Brooks", "role": "operations owner"}, {"name": "Mia Shah", "role": "editor"}], "source_artifacts": ["First Mile Creative working brief", "First Mile Creative approval thread", "First Mile Creative review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Lucas 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-04-22."}, {"speaker": "Zoe Walker", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Sofia Brooks", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Mia Shah", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Zoe Walker", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Lucas Patel", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Sofia Brooks", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-22. I will also log the blocker explicitly in the tracker."}, {"speaker": "Mia Shah", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a lightweight review draft for the client onboarding workstream so the project can move without reopening full scope. They agreed that the approver wants fewer review rounds is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "practical and forward-moving", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Lucas Patel"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Zoe Walker"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Sofia Brooks"}], "reference_action_items": [{"owner": "Lucas Patel", "role": "creative lead", "task": "Revise the client onboarding brief around a lightweight review draft.", "due_date": "2026-04-22", "depends_on": "None"}, {"owner": "Mia Shah", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-24", "depends_on": "Updated brief from Lucas Patel"}, {"owner": "Zoe Walker", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-22", "depends_on": "Internal stakeholder availability"}, {"owner": "Sofia Brooks", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-23", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Sofia Brooks will send the updated recap and propose a short review before 2026-04-22, while Lucas Patel revises the brief and Mia Shah prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "First Mile Creative launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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", "fast recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0146", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.91, "meeting_context": {"brand": "Lattice Harbor", "meeting_type": "vendor sync", "meeting_date": "2026-05-05", "channel": "Zoom", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Miles Kim", "role": "creative lead"}, {"name": "Elijah Rivera", "role": "stakeholder"}, {"name": "Miles Lopez", "role": "operations owner"}, {"name": "Sofia Diaz", "role": "editor"}], "source_artifacts": ["Lattice Harbor working brief", "Lattice Harbor approval thread", "Lattice Harbor review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and avoid pricing language in the recap."}], "transcript": [{"speaker": "Miles 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-05."}, {"speaker": "Elijah Rivera", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a lightweight review draft instead of the full package."}, {"speaker": "Miles Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Sofia Diaz", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Elijah Rivera", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to avoid pricing language in the recap. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Kim", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a lightweight review draft, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Miles Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-23. I will also log the blocker explicitly in the tracker."}, {"speaker": "Sofia Diaz", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a lightweight review draft as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Miles Kim"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Elijah Rivera"}, {"decision": "Keep the recap practical and avoid pricing language in the recap.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Miles Lopez"}], "reference_action_items": [{"owner": "Miles Kim", "role": "creative lead", "task": "Revise the vendor sync brief around a lightweight review draft.", "due_date": "2026-04-23", "depends_on": "None"}, {"owner": "Sofia Diaz", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-25", "depends_on": "Updated brief from Miles Kim"}, {"owner": "Elijah Rivera", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-23", "depends_on": "Internal stakeholder availability"}, {"owner": "Miles Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-24", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Miles Lopez will send the updated recap and propose a short review before 2026-04-23, while Miles Kim revises the brief and Sofia Diaz prepares the scoped cut.", "slack_recap": "Locked: a lightweight review draft first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Harbor launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and avoid pricing language in the recap."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0147", "benchmark_split": "validation", "difficulty": "easy", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.85, "meeting_context": {"brand": "Echoframe Media", "meeting_type": "creative review", "meeting_date": "2026-04-22", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for creative review without losing the proof or hiding blockers.", "participants": [{"name": "Mia Diaz", "role": "creative lead"}, {"name": "Liam Lopez", "role": "stakeholder"}, {"name": "Ivy Rivera", "role": "operations owner"}, {"name": "Ivy Brooks", "role": "editor"}], "source_artifacts": ["Echoframe Media working brief", "Echoframe Media approval thread", "Echoframe Media review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and keep the ask to one concrete next move."}], "transcript": [{"speaker": "Mia 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 Lopez", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a teaser-first cut instead of the full package."}, {"speaker": "Ivy Rivera", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the approver wants fewer review rounds. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ivy Brooks", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Liam Lopez", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to keep the ask to one concrete next move. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Diaz", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a teaser-first cut, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Rivera", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-24. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ivy Brooks", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 review easy to accept.", "stakeholder_temperature": "supportive with approval sensitivity", "blockers": ["the approver wants fewer review rounds", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a teaser-first cut as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Diaz"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Liam Lopez"}, {"decision": "Keep the recap practical and keep the ask to one concrete next move.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Rivera"}], "reference_action_items": [{"owner": "Mia Diaz", "role": "creative lead", "task": "Revise the creative review brief around a teaser-first cut.", "due_date": "2026-04-24", "depends_on": "None"}, {"owner": "Ivy Brooks", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-26", "depends_on": "Updated brief from Mia Diaz"}, {"owner": "Liam Lopez", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-24", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Rivera", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-25", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Echoframe Media creative review: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a teaser-first cut as the first deliverable for creative review, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the approver wants fewer review rounds, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Rivera will send the updated recap and propose a short review before 2026-04-24, while Mia Diaz revises the brief and Ivy Brooks prepares the scoped cut.", "slack_recap": "Locked: a teaser-first cut first, wider rollout later. Main blocker stays visible: the approver wants fewer review rounds. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 Media launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and keep the ask to one concrete next move."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-easy", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0148", "benchmark_split": "validation", "difficulty": "medium", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.93, "meeting_context": {"brand": "Harborline Works", "meeting_type": "vendor sync", "meeting_date": "2026-05-12", "channel": "Slack huddle", "objective": "Use the meeting to narrow the first deliverable for vendor sync without losing the proof or hiding blockers.", "participants": [{"name": "Mia Chen", "role": "creative lead"}, {"name": "Zoe Kim", "role": "stakeholder"}, {"name": "Ivy Kim", "role": "operations owner"}, {"name": "Ethan Nguyen", "role": "editor"}], "source_artifacts": ["Harborline Works working brief", "Harborline Works approval thread", "Harborline Works review tracker"]}, "agenda": [{"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 it."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Mia Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-05-12."}, {"speaker": "Zoe Kim", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a proof-first recap instead of the full package."}, {"speaker": "Ivy Kim", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that the source footage is wider than the launch window allows. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Ethan Nguyen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Zoe Kim", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Mia Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a proof-first recap, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Ivy Kim", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-25. I will also log the blocker explicitly in the tracker."}, {"speaker": "Ethan Nguyen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"executive_summary": "The team aligned on using a proof-first recap for the vendor sync workstream so the project can move without reopening full scope. They agreed that the source footage is wider than the launch window allows is still live, so the follow-up has to stay honest about what is unresolved while still making the next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["the source footage is wider than the launch window allows", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a proof-first recap as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Mia Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Zoe Kim"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Ivy Kim"}], "reference_action_items": [{"owner": "Mia Chen", "role": "creative lead", "task": "Revise the vendor sync brief around a proof-first recap.", "due_date": "2026-04-25", "depends_on": "None"}, {"owner": "Ethan Nguyen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-27", "depends_on": "Updated brief from Mia Chen"}, {"owner": "Zoe Kim", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-25", "depends_on": "Internal stakeholder availability"}, {"owner": "Ivy Kim", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-26", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"email_subject": "Harborline Works vendor sync: scoped recap and next review step", "followup_email": "Thanks everyone. We aligned on using a proof-first recap as the first deliverable for vendor sync, then revisiting the broader package once we have reactions to the tighter pass. We also agreed that the source footage is wider than the launch window allows, so the recap and review request should stay practical rather than overstate certainty. Next step: Ivy Kim will send the updated recap and propose a short review before 2026-04-25, while Mia Chen revises the brief and Ethan Nguyen prepares the scoped cut.", "slack_recap": "Locked: a proof-first recap first, wider rollout later. Main blocker stays visible: the source footage is wider than the launch window allows. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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": "Harborline Works launch tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 recap versus overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-medium", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}
{"example_id": "zarn_meeting_to_actions_validation_0149", "benchmark_split": "validation", "difficulty": "hard", "product_scope": "Zarn", "task_family": "meeting_actions", "dataset_license": "apache-2.0", "annotation_status": "zarnite-team-reviewed-gold-track-starter", "confidence": 0.89, "meeting_context": {"brand": "Signal Oak", "meeting_type": "vendor sync", "meeting_date": "2026-04-22", "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 Chen", "role": "creative lead"}, {"name": "Miles Patel", "role": "stakeholder"}, {"name": "Zoe Lopez", "role": "operations owner"}, {"name": "Jalen Chen", "role": "editor"}], "source_artifacts": ["Signal Oak working brief", "Signal Oak approval thread", "Signal Oak review tracker"]}, "agenda": [{"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."}, {"slot": 3, "topic": "How to frame the follow-up", "goal": "Agree on one practical next step and do not imply launch timing yet."}], "transcript": [{"speaker": "Miles Chen", "role": "creative lead", "timestamp": "00:00", "text": "We need a tighter plan for vendor sync. Right now the draft is too broad for the review window on 2026-04-22."}, {"speaker": "Miles Patel", "role": "stakeholder", "timestamp": "00:21", "text": "I agree. The team can react faster if the first deliverable is just a tighter pilot package instead of the full package."}, {"speaker": "Zoe Lopez", "role": "operations owner", "timestamp": "00:46", "text": "The blocker I do not want us to hide is that two stakeholders still disagree on scope. If the follow-up ignores that, it will sound disconnected from reality."}, {"speaker": "Jalen Chen", "role": "editor", "timestamp": "01:12", "text": "From the production side, the cleanest move is to keep one proof beat visible and remove every extra branch that needs another approval pass."}, {"speaker": "Miles Patel", "role": "stakeholder", "timestamp": "01:41", "text": "That works for me, but the recap has to do not imply launch timing yet. I do not want a message that reads more resolved than we are."}, {"speaker": "Miles Chen", "role": "creative lead", "timestamp": "02:04", "text": "Then let us lock the first deliverable as a tighter pilot package, hold the broader rollout for later, and assign the recap to ops so the tracker stays current."}, {"speaker": "Zoe Lopez", "role": "operations owner", "timestamp": "02:31", "text": "I will send a recap with one next step and propose a short review before 2026-04-26. I will also log the blocker explicitly in the tracker."}, {"speaker": "Jalen Chen", "role": "editor", "timestamp": "02:52", "text": "I will prepare the scoped cut once the revised brief lands. If scope expands again, I want that called out in the notes rather than assumed away."}], "reference_summary": {"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 next review easy to accept.", "stakeholder_temperature": "aligned but cautious", "blockers": ["two stakeholders still disagree on scope", "The broader rollout is intentionally deferred until the first scoped pass is reviewed."], "why_scope_changed": "The group wanted a first deliverable that can be reviewed quickly without another full decision cycle."}, "reference_decisions": [{"decision": "Use a tighter pilot package as the first deliverable.", "reason": "It shortens the review burden and makes feedback easier to collect.", "owner": "Miles Chen"}, {"decision": "Push the broader rollout to the next wave after the first scoped pass.", "reason": "The team wants proof and alignment before expanding scope.", "owner": "Miles Patel"}, {"decision": "Keep the recap practical and do not imply launch timing yet.", "reason": "The stakeholder explicitly pushed back on vague or inflated language.", "owner": "Zoe Lopez"}], "reference_action_items": [{"owner": "Miles Chen", "role": "creative lead", "task": "Revise the vendor sync brief around a tighter pilot package.", "due_date": "2026-04-26", "depends_on": "None"}, {"owner": "Jalen Chen", "role": "editor", "task": "Prepare the first scoped deliverable and note what proof must stay visible.", "due_date": "2026-04-28", "depends_on": "Updated brief from Miles Chen"}, {"owner": "Miles Patel", "role": "stakeholder", "task": "Confirm whether the proposed review window works for the approval group.", "due_date": "2026-04-26", "depends_on": "Internal stakeholder availability"}, {"owner": "Zoe Lopez", "role": "operations owner", "task": "Send the recap and log unresolved blockers in the tracker.", "due_date": "2026-04-27", "depends_on": "Meeting notes finalized"}], "reference_followup_package": {"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 two stakeholders still disagree on scope, so the recap and review request should stay practical rather than overstate certainty. Next step: Zoe Lopez will send the updated recap and propose a short review before 2026-04-26, while Miles Chen revises the brief and Jalen Chen prepares the scoped cut.", "slack_recap": "Locked: a tighter pilot package first, wider rollout later. Main blocker stays visible: two stakeholders still disagree on scope. Ops will send recap and short review options.", "internal_note": "Keep the tracker aligned to the scoped-first decision. Do not mark timing or approval as final until the stakeholder review confirms it.", "external_summary_bullets": ["We aligned on a smaller first pass rather than a wider rollout.", "The blocker remains visible and will stay explicit in the follow-up.", "The next review ask should be singular and easy to answer."]}, "open_questions": ["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?"], "rubric": {"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", "Turns the recap into a broader plan than the meeting approved"]}, "pre_read_context": {"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 tracker", "note": "The review sequence still depends on one unresolved blocker."}], "known_tensions": ["The team wants speed, but not at the cost of fake certainty.", "The first deliverable needs to feel useful without reopening the full scope."]}, "decision_tensions": [{"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 certainty", "why_it_mattered": "The team wanted momentum, but not language that outruns approvals.", "resolved_direction": "Keep the recap practical and do not imply launch timing yet."}], "followup_risks": ["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."], "quality_checks": ["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."], "evidence_manifest": {"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 overpromising certainty"], "output_contract": ["one faithful summary", "one decision list", "one action table", "one follow-up package"]}, "reference_variants": [{"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": "ops-heavy recap variant", "rationale": "Acceptable when the response foregrounds owners, due dates, and tracker hygiene over prose polish.", "outputs": {"summary_style": "action-led recap", "followup_tone": "more operational and checklist-oriented"}}], "negative_examples": [{"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 and turns the result into vague notes.", "conflicting_rule": "Action items must include owners, due dates, and meaningful dependencies."}, {"label": "tone inflation", "why_bad": "Writes the follow-up with more confidence than the meeting supports.", "conflicting_rule": "The follow-up package should reflect the tone concerns raised inside the meeting."}], "difficulty_rationale": "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 behaves like a holdout-style gold candidate.", "benchmark_slices": ["high-context", "constraint-dense", "difficulty-hard", "decision-tension", "blocker-preservation", "owner-date-extraction", "tone-sensitive-followup", "scope-change", "holdout-candidate", "stress-case"], "adversarial_features": ["mixed-consensus", "owner-and-deadline-coupling", "soft-pushback-in-transcript", "deferred-scope", "audit-split", "multi-constraint-pressure"], "expected_failure_modes": ["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.", "Looks acceptable in isolation but fails a stricter holdout review for faithfulness or completeness.", "Collapses several real constraints into a generic polished answer that sounds smoother than the source allows."], "review_readiness": {"status": "ready-for-holdout-review", "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.", "Follow-up artifacts match the tone and caution level from the meeting."]}}