---
id: TST-PFM-ELG-508
title: Responsibility request schemas checks
kind: unit
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/responsibilities/tests/unit/request-schemas.spec.js
implements: []
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:modules/responsibilities/tests/unit/request-schemas.spec.js
    cases:
      - 'takes the columns a client states, trimmed'
      - 'keeps team_id, so the service refuses it in words'
      - 'refuses the source, which is the server’s'
      - 'refuses a status, which is the server’s'
      - 'refuses a derivation, which only the derivation function writes'
      - refuses a scope type outside its closed list
      - refuses a kind outside its closed list
      - clears a blank note rather than storing it
      - takes the version read and the reason
      - refuses a body without the version read
      - 'takes the delegate, the window and the reason'
      - requires the end of the window
      - 'refuses the assignment in the body, which is the path’s'
      - reads the assignment list filters
      - refuses a page larger than 200
      - requires the key of the effective holders
  - provenance: documented
    source: >-
      services-platform:modules/responsibilities/tests/unit/request-schemas.spec.js:suite
      header
    note: >-
      The source header describes the verification boundary and declared
      substitutions.
proof_limit: >-
  No complete capability or feature scenario is mapped to this file; case-level
  ownership remains a coverage finding.
---

# Responsibility request schemas 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 file contains executable checks, but no complete scenario mapping is established here. Its source test titles identify the remaining mapping work.

## 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.