---
id: ATS-MBR-STR-010
scope: CAP-MBR-STR-010
product_area: membership
module: structure
revision: 2
status: proposed
approved_by: null
approved_at: null
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
scenarios:
  - id: ATS-MBR-STR-010-01
    title: Program requirements replace at the read version
    level: api
    proves:
      - BR-CAP-MBR-STR-010-01
    preconditions: >-
      An isolated Membership-licensed workspace contains the relevant records, with caller permissions
      selected for the case.
    steps: Replace unit requirements with the current program version and repeat with the earlier version.
    expected: 'The list saves once, advances the program version and rejects the stale retry.'
    negative: true
    data_needs: The FAA example records or equivalent records prepared within the isolated workspace.
    bound_to: []
    provenance: proposed
    source: >-
      services-membership:modules/configuration/services/configuration/configuration-records.ts:replaceProgramUnitTypesOf
    category: concurrency
  - id: ATS-MBR-STR-010-02
    title: Non-affiliation programs reject populated requirements
    level: api
    proves:
      - BR-CAP-MBR-STR-010-02
    preconditions: >-
      An isolated Membership-licensed workspace contains the relevant records, with caller permissions
      selected for the case.
    steps: Submit a nonempty category list for a program without unit binding.
    expected: The request fails without changing the program list.
    negative: true
    data_needs: The FAA example records or equivalent records prepared within the isolated workspace.
    bound_to: []
    provenance: proposed
    source: >-
      services-membership:modules/configuration/services/configuration/configuration-records.ts:replaceProgramUnitTypesOf
    category: validation
  - id: ATS-MBR-STR-010-03
    title: All invalid unit rows are reported
    level: api
    proves:
      - BR-CAP-MBR-STR-010-03
    preconditions: >-
      An isolated Membership-licensed workspace contains the relevant records, with caller permissions
      selected for the case.
    steps: 'Submit an affiliation-disabled category, a repeated category and contradictory counts together.'
    expected: The refusal identifies all detected row problems.
    negative: true
    data_needs: The FAA example records or equivalent records prepared within the isolated workspace.
    bound_to: []
    provenance: proposed
    source: >-
      services-membership:modules/configuration/services/configuration/configuration-records.ts:unitTypeProblems
    category: validation
  - id: ATS-MBR-STR-010-04
    title: Current affiliations protect their category
    level: api
    proves:
      - BR-CAP-MBR-STR-010-04
    preconditions: >-
      An isolated Membership-licensed workspace contains the relevant records, with caller permissions
      selected for the case.
    steps: Remove a kind still used by an open qualifying affiliation.
    expected: The list replacement fails and retains the category.
    negative: true
    data_needs: The FAA example records or equivalent records prepared within the isolated workspace.
    bound_to:
      - >-
        services-membership:modules/memberships/tests/integration/services/affiliations.integration.spec.ts#the
        term affiliations in the database › refuses to drop a unit type from the program while an
        affiliation uses it (unit_type_in_use)
      - TST-MBR-STR-002
    provenance: test
    source: >-
      services-membership:modules/memberships/tests/integration/services/affiliations.integration.spec.ts#the
      term affiliations in the database › refuses to drop a unit type from the program while an
      affiliation uses it (unit_type_in_use)
    category: interaction
  - id: ATS-MBR-STR-010-05
    title: Package counts specialize retained program choices
    category: interaction
    level: api
    proves:
      - BR-CAP-MBR-STR-010-03
      - BR-CAP-MBR-STR-013-06
    preconditions: An isolated workspace contains the records and current versions needed for the case.
    steps: >-
      Set program chapter maximum to two and a package maximum to one; read effective requirements, then
      clear package requirements.
    expected: >-
      The package maximum applies first while program primary choices remain; clearing restores the
      program maximum.
    negative: false
    data_needs: Separate fixture records for the accepted and refused operations.
    bound_to: []
    provenance: proposed
    source:
      - >-
        services-membership:modules/configuration/services/configuration/configuration-records.ts:unitTypeProblems
      - 'services-membership:modules/memberships/services/affiliations/unit-rules.ts'
    exercises:
      - CAP-MBR-STR-010
      - CAP-MBR-STR-013
  - id: ATS-MBR-STR-010-06
    title: Workspace authority gates this capability
    category: permission
    level: api
    proves:
      - BR-CAP-MBR-STR-019-02
    preconditions: An isolated workspace contains the records and current versions needed for the case.
    steps: >-
      Exercise the capability’s exposed operations with its read-only and management callers, then repeat
      with application access removed, an unlicensed workspace and an unavailable workspace.
    expected: >-
      Each named operation requires its declared authority; admission failures occur before any record or
      calculated result is exposed.
    negative: true
    data_needs: Separate fixture records for the accepted and refused operations.
    bound_to: []
    provenance: proposed
    source:
      - >-
        services-membership:tests/unit/route-authorization.spec.ts#route authorization: every Membership
        operation names its permission › requires membership.structure.read of every structure read and
        membership.structure.manage of every change
      - >-
        services-membership:modules/configuration/aws/api/configuration.routes.ts:configurationModuleRoutes
      - >-
        services-membership:tests/e2e/terms-api.e2e.spec.ts#the terms API, end to end in process ›
        refuses a caller who holds no key in the tenant
    exercises:
      - CAP-MBR-STR-010
      - CAP-MBR-STR-019
evidence:
  - 'services-membership:modules/memberships/tests/integration/services/affiliations.integration.spec.ts'
  - >-
    services-membership:modules/configuration/services/configuration/configuration-records.ts:replaceProgramUnitTypesOf
  - >-
    services-membership:modules/configuration/services/configuration/configuration-records.ts:unitTypeProblems
  - >-
    services-membership:modules/configuration/services/configuration/configuration-records.ts:programUnitTypesContent
  - 'react-console:acceptance/membership/journeys/configuration/MBR-ACC-0096.json'
  - >-
    services-membership:modules/memberships/tests/integration/services/affiliations.integration.spec.ts#the
    term affiliations in the database › refuses to drop a unit type from the program while an affiliation
    uses it (unit_type_in_use)
  - 'services-membership:modules/memberships/services/affiliations/unit-rules.ts'
  - membership.programs.manage
  - membership.programs.read
  - membership.application.access
  - >-
    services-membership:tests/unit/route-authorization.spec.ts#route authorization: every Membership
    operation names its permission › requires membership.structure.read of every structure read and
    membership.structure.manage of every change
  - 'services-membership:modules/configuration/aws/api/configuration.routes.ts:configurationModuleRoutes'
  - >-
    services-membership:tests/e2e/terms-api.e2e.spec.ts#the terms API, end to end in process › refuses a
    caller who holds no key in the tenant
coverage:
  rule: 'gap: FND-MBR-STR-063'
  transition: not-applicable
  validation: covered
  permission: covered
  edge: 'gap: FND-MBR-STR-063'
  failure: 'gap: FND-MBR-STR-063'
  boundary: 'gap: FND-MBR-STR-063'
  concurrency: covered
  invariant: 'gap: FND-MBR-STR-063'
  interaction: covered
coverage_notes:
  rule: >-
    No dedicated scenario establishes this category across the capability’s declared operations and
    design obligations.
  transition: >-
    This capability reads or changes facets without owning a standing transition; the owning lifecycle
    specification carries those transitions.
  edge: >-
    No dedicated scenario establishes this category across the capability’s declared operations and
    design obligations.
  failure: >-
    No dedicated scenario establishes this category across the capability’s declared operations and
    design obligations.
  boundary: >-
    No dedicated scenario establishes this category across the capability’s declared operations and
    design obligations.
  invariant: >-
    No dedicated scenario establishes this category across the capability’s declared operations and
    design obligations.
unproved_rules: []
coverage_obligations:
  permissions:
    - key: membership.programs.manage
      scenario_ids:
        - ATS-MBR-STR-019-02
      local_scenario_ids:
        - ATS-MBR-STR-010-06
      coverage: partial
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
      note: >-
        These cases establish declared authority or representative admission; exhaustive operation and
        caller combinations remain open.
    - key: membership.programs.read
      scenario_ids:
        - ATS-MBR-STR-019-02
      local_scenario_ids:
        - ATS-MBR-STR-010-06
      coverage: partial
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
      note: >-
        These cases establish declared authority or representative admission; exhaustive operation and
        caller combinations remain open.
    - key: membership.application.access
      scenario_ids:
        - ATS-MBR-STR-019-04
      local_scenario_ids:
        - ATS-MBR-STR-010-06
      coverage: partial
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
      note: >-
        These cases establish declared authority or representative admission; exhaustive operation and
        caller combinations remain open.
  state_models: []
  related:
    - capability: CAP-MBR-STR-013
      scenario: ATS-MBR-STR-010-05
      provenance: proposed
  invariants:
    - id: INV-DOM-MBR-STR-003-01
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
    - id: INV-DOM-MBR-STR-003-02
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
    - id: INV-DOM-MBR-STR-003-03
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
    - id: INV-DOM-MBR-STR-003-04
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
    - id: INV-DOM-MBR-STR-003-05
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
    - id: INV-DOM-MBR-STR-003-06
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
    - id: INV-DOM-MBR-STR-003-07
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
  workflows:
    - id: WF-MBR-STR-005
      scenarios:
        - ATS-MBR-STR-010-01
        - ATS-MBR-STR-010-04
        - ATS-MBR-STR-010-05
      unproved_failure_and_concurrency: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
  workflow_interactions:
    - workflow: WF-MBR-STR-005
      capability: CAP-MBR-STR-018
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
      note: >-
        The shared workflow names both capabilities, but a concrete interaction oracle is not established
        for this pairing.
    - workflow: WF-MBR-STR-005
      capability: CAP-MBR-STR-009
      scenario_ids:
        - ATS-MBR-STR-009-07
      coverage: specified
      gap: null
      provenance: documented
      source:
        - ATS-MBR-STR-009-07
      note: Cross-capability examples are cited from their owning specifications.
    - workflow: WF-MBR-STR-005
      capability: CAP-MBR-STR-011
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
      note: >-
        The shared workflow names both capabilities, but a concrete interaction oracle is not established
        for this pairing.
    - workflow: WF-MBR-STR-005
      capability: CAP-MBR-STR-014
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
      note: >-
        The shared workflow names both capabilities, but a concrete interaction oracle is not established
        for this pairing.
    - workflow: WF-MBR-STR-005
      capability: CAP-MBR-STR-017
      scenario_ids: []
      coverage: gap
      gap: FND-MBR-STR-063
      provenance: unknown
      source: FND-MBR-STR-063
      note: >-
        The shared workflow names both capabilities, but a concrete interaction oracle is not established
        for this pairing.
rule_coverage:
  - rule: BR-CAP-MBR-STR-010-01
    scenarios:
      - ATS-MBR-STR-010-01
    gap: null
    provenance: documented
    source:
      - >-
        services-membership:modules/configuration/services/configuration/configuration-records.ts:replaceProgramUnitTypesOf
  - rule: BR-CAP-MBR-STR-010-02
    scenarios:
      - ATS-MBR-STR-010-02
    gap: null
    provenance: documented
    source:
      - >-
        services-membership:modules/configuration/services/configuration/configuration-records.ts:replaceProgramUnitTypesOf
  - rule: BR-CAP-MBR-STR-010-03
    scenarios:
      - ATS-MBR-STR-010-03
      - ATS-MBR-STR-010-05
    gap: null
    provenance: documented
    source:
      - >-
        services-membership:modules/configuration/services/configuration/configuration-records.ts:unitTypeProblems
      - >-
        services-membership:modules/configuration/services/configuration/configuration-records.ts:unitTypeProblems
      - 'services-membership:modules/memberships/services/affiliations/unit-rules.ts'
  - rule: BR-CAP-MBR-STR-010-04
    scenarios:
      - ATS-MBR-STR-010-04
    gap: null
    provenance: documented
    source:
      - >-
        services-membership:modules/memberships/tests/integration/services/affiliations.integration.spec.ts#the
        term affiliations in the database › refuses to drop a unit type from the program while an
        affiliation uses it (unit_type_in_use)
narrative_sources:
  - section: Coverage
    provenance: documented
    source:
      - CAP-MBR-STR-010
      - FND-MBR-STR-063
  - section: Interactions With Related Capabilities
    provenance: proposed
    source:
      - ATS-MBR-STR-010-04
      - ATS-MBR-STR-010-05
---

# Set a program’s affiliation requirements: Capability Test Specification

## Coverage

The coverage map distinguishes specified examples from missing proof. A covered category means an expected case is specified; executable bindings and their run results remain separate evidence. Each required rule has a proof link or an explicit coverage finding in the structured rule ledger.

| Required Rule | Scenario or Finding |
|---|---|
| `BR-CAP-MBR-STR-010-01` | `ATS-MBR-STR-010-01` |
| `BR-CAP-MBR-STR-010-02` | `ATS-MBR-STR-010-02` |
| `BR-CAP-MBR-STR-010-03` | `ATS-MBR-STR-010-03`, `ATS-MBR-STR-010-05` |
| `BR-CAP-MBR-STR-010-04` | `ATS-MBR-STR-010-04` |

## Interactions With Related Capabilities

Package counts specialize retained program choices. Set program chapter maximum to two and a package maximum to one; read effective requirements, then clear package requirements.