---
id: ADR-PFM-ELG-011
title: Responsibilities are their own module and grant no access
product_area: platform
module: eligibility
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Store responsibilities in their own Platform module and keep them outside the
  authorizer and authorization package.
constrains:
  - DOM-PFM-ELG-004
  - SVC-PFM-ELG-responsibilities
  - RESP-PFM
origin: >-
  Responsibilities and attention architecture D-01 (a separate Platform module
  never read by the authorizer), approved by Andrew 2026-10-18 (PLAT-M15
  "Decisions")
alternatives:
  - option: Represent accountability as security roles
    why_not: >-
      Security roles carry permissions and would couple accountability to
      access.
  - option: Let each application store its own independent responsibilities
    why_not: 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.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a6:
    docs/proposals/responsibilities-and-attention/16-decisions.md;
    docs/milestones/PLAT-M15-home-attention-and-responsibilities.md (Decisions)
  - >-
    services-platform at ad3f6a6: docs/responsibilities.md §1;
    tests/unit/responsibilities-not-in-authorization.spec.ts
---
# 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.