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.
34 lines
1.2 KiB
JSON
34 lines
1.2 KiB
JSON
{
|
|
"facts": [
|
|
{
|
|
"fact": "Criteria are still needed for Business Development projects.",
|
|
"evidence": "Mara: For the new partner intake, we still need criteria for Business Development projects."
|
|
},
|
|
{
|
|
"fact": "Noah is speaking from Marketing.",
|
|
"evidence": "Noah: From Marketing, I can tell you that generic criteria will not work."
|
|
},
|
|
{
|
|
"fact": "Noah is not taking responsibility for defining the Business Development criteria.",
|
|
"evidence": "Noah: I am not taking that on."
|
|
}
|
|
],
|
|
"decisions": [
|
|
{
|
|
"decision": "Responsibility for defining the Business Development criteria remains open until Business Development confirms an owner.",
|
|
"evidence": "Mara: Agreed. Responsibility stays open for now, and we will ask Business Development for an owner."
|
|
}
|
|
],
|
|
"todos": [
|
|
{
|
|
"task": "Ask Business Development for an owner for defining the Business Development criteria.",
|
|
"responsible": null,
|
|
"deadline": null,
|
|
"evidence": "Mara: Agreed. Responsibility stays open for now, and we will ask Business Development for an owner."
|
|
}
|
|
],
|
|
"questions": [],
|
|
"positions": [],
|
|
"technical": []
|
|
}
|