Files
meeting-lab/tests/gold/responsibility_attribution_negative/expected.json
T
admin 63075eaca9 Enforce explicit responsibility attribution
- document responsibility attribution as a project-wide invariant
- prevent inferred ownership in protocol rendering
- add negative gold regression for false responsibility assignment
- document future responsibility evidence and attribution model
- record the real-life benchmark finding
2026-07-31 13:01:11 +02:00

40 lines
1.5 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": [
{
"speaker": "Noah",
"position": "Noah says generic criteria will not work for different Marketing and product contexts.",
"evidence": "Noah: From Marketing, I can tell you that generic criteria will not work. A digital campaign and a physical product launch need different checks."
}
],
"technical": []
}