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
This commit is contained in:
2026-07-31 13:01:11 +02:00
parent 40f390ebfe
commit 63075eaca9
13 changed files with 359 additions and 0 deletions
@@ -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.