Responsibilities are their own module and grant no access

Context

Accountability should explain who looks after work without granting the ability to perform it.

Decision

Store responsibilities in their own Platform module and keep them outside the authorizer and authorization package.

Alternatives Considered

Represent accountability as security roles: Security roles carry permissions and would couple accountability to access.

Let each application store its own independent responsibilities: Shared attention would need application-specific audience resolution.

Consequences

Import-boundary tests protect the separation. Responsibility membership affects audience visibility only. The management screen explains that assignments do not grant access.