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

tests/gold/responsibility_attribution_negative/README.md

@@ -0,0 +1,15 @@
+# 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.
+
+Expected behavior:
+
+- Do not assign Business Development criteria to the Marketing participant.
+- Do not reclassify the Marketing participant as Business Development.
+- Preserve the objection as a position.
+- Keep responsibility open unless explicitly assigned.

tests/gold/responsibility_attribution_negative/expected.json

@@ -0,0 +1,39 @@
+{
+  "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": []
+}

tests/gold/responsibility_attribution_negative/transcript.txt

@@ -0,0 +1,11 @@
+Mara: For the new partner intake, we still need criteria for Business Development projects.
+
+Noah: From Marketing, I can tell you that generic criteria will not work. A digital campaign and a physical product launch need different checks.
+
+Mara: Right, so the Business Development criteria remain open.
+
+Noah: I am not taking that on. I only want to flag that the criteria cannot be generic.
+
+Lea: Then we should keep the owner open until Business Development confirms who will define them.
+
+Mara: Agreed. Responsibility stays open for now, and we will ask Business Development for an owner.