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:
@@ -47,6 +47,20 @@ Every processing step should be understandable.
|
||||
|
||||
Intermediate results should remain inspectable throughout the pipeline.
|
||||
|
||||
## Responsibility Attribution Integrity
|
||||
|
||||
Responsibility, ownership, organizational roles and action-item assignments may
|
||||
be recorded only when meeting evidence explicitly assigns, accepts or confirms
|
||||
them.
|
||||
|
||||
The system must not infer responsibility from thematic proximity,
|
||||
participation in a discussion, mentioning a task, commenting on another
|
||||
department, organizational assumptions, likely job roles, speaker adjacency or
|
||||
model world knowledge.
|
||||
|
||||
When evidence is incomplete or ambiguous, the responsible person remains unset
|
||||
or unclear and the supporting evidence is preserved.
|
||||
|
||||
## Reproducible Experiments
|
||||
|
||||
Experiments must be repeatable.
|
||||
|
||||
Reference in New Issue
Block a user