Meeting Action Item Extraction
The model captures what was discussed. You need what was committed to.
Meeting Action Item Extraction
There's a specific failure mode in meeting transcripts: the model extracts discussion
points as action items. "We talked about migrating to the new auth system" becomes
[ACTION] Migrate to new auth system. Nobody owns it. Nobody has a deadline. It will
never happen.
Meanwhile, the actual commitments are buried mid-sentence: "I can take a look at that this week" — implicit owner, implicit timeline, no explicit "action item" label.
This example optimizes an extraction module to catch real commitments (ownership + intent + timeline, however implicit) and ignore stated discussions.
Optimizer: PromptGradOptimizer
Difficulty: Intermediate
The Problem
Without optimization:
After optimization:
Carol saying "someone should probably" is not a commitment. Alice noting a recurring issue is not a commitment. Only Bob made one.
Full Example
Why This Is Hard
The line between discussion and commitment is entirely in linguistic register:
| Phrase | Commitment? |
|---|---|
"I'll handle that" | Yes — first person + future intent |
"Someone should look at this" | No — no owner |
"We've been meaning to fix it" | No — historical observation |
"Can you take that?" + "Sure" | Yes — explicit acceptance |
"That needs to be done" | No — passive voice, no owner |
"I can put together a spec by Friday" | Yes — first person + capability + deadline |
The model doesn't know this unless told. The optimizer's feedback explicitly describes the linguistic pattern that marks a commitment, and PromptGrad accumulates this as a rule across multiple training batches.
The error_type field distinguishes "missed_commitment" from "false_commitment" —
enabling the optimizer to see both failure modes in each gradient batch.