admin
06f0e7e651
Introduce Meeting Context V1 with YAML schema, validation and template. Support optional --meeting-context during chunk extraction. Inject authoritative Meeting Context into extraction prompts. Record Meeting Context provenance in extraction output. Activate todos.md in shared prompt assembly. Strengthen responsibility attribution and decision/todo boundaries. Add focused Gold scenarios and validation tests. Update architecture and pipeline documentation.
responsibility_attribution_negative
Tests that thematic proximity, department discussion and objection do not create an action-item owner.
The scenario includes a Marketing participant who comments critically on Business Development criteria. No one assigns that participant responsibility for defining the criteria, and the participant does not accept such a task.
Scope:
- Do not assign Business Development criteria to the Marketing participant.
- Do not reclassify the Marketing participant as Business Development.
- Keep responsibility open unless explicitly assigned.
- Preserve the agreed next step to ask Business Development for an owner.
Exclusions:
- This scenario does not test whether the objection is extracted as a position.
- Position extraction is covered by
position_explicit_objection.