---
id: TST-PFM-ELG-512
title: Responsibility responsibilities not in authorization checks
kind: unit
product_area: platform
module: eligibility
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - tests/unit/responsibilities-not-in-authorization.spec.ts
implements:
  - ATS-PFM-ELG-013-01
environment: mock
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 1
isolation: One process with suite-local inputs.
evidence:
  - provenance: test
    source: 'services-platform:tests/unit/responsibilities-not-in-authorization.spec.ts'
    cases:
      - walks the authorizer and finds its sources
      - 'walks the security assignments persistence, where the grant slice is read'
      - walks the installed evaluator package and finds its modules
      - 'finds the responsibilities module it keeps out, so the absence below means something'
      - 'finds the attention module it keeps out, so the absence below means something'
      - >-
        imports nothing of the responsibilities module into the authorizer or the grant slice, and
        names none of its tables
      - keeps the shared evaluator free of the module and its tables
      - refuses a static import of the module
      - refuses a require of the module from compiled code
      - refuses a statement that reads a responsibility table
      - refuses a call of a responsibilities read function
      - refuses a static import of the attention module
      - refuses a statement that reads an attention table
      - refuses a call of an attention write function
      - allows a file that mentions responsibilities in prose only
  - provenance: documented
    source: 'services-platform:tests/unit/responsibilities-not-in-authorization.spec.ts:suite header'
    note: The source header describes the verification boundary and declared substitutions.
proof_limit: >-
  Only the named scenario checkpoints have a verified source binding; execution has not been
  attempted.
---

# Responsibility responsibilities not in authorization checks

## Verification Boundary

This suite checks isolated decisions and validation using the imported inputs. It cannot establish a complete service or browser lifecycle.

## What This Suite Proves

The mapped scenarios identify the capability and feature checkpoints this file exercises. The source test titles preserve the assertion-level evidence.

## What It Does Not Prove

Registration supplies no execution result or conformance decision. Passing isolated checks does not establish deployed dependencies or cross-application delivery.

## Real Dependencies and Test Doubles

The suite runs isolated checks; its imported fixtures and injected collaborators define the substitutions. The source imports and suite header identify the exact dependencies.

## Must Not Be Doubled

The decision or validator being asserted remains real; returning the expected answer from a substitute defeats the check.