---
id: TST-MBR-STR-057
title: Program structure-reference validation acceptance
kind: api-lifecycle
product_area: membership
module: structure
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-membership
files:
  - tests/acceptance/configuration/MBR-ACC-0120.acceptance.ts
implements:
  - ATS-MBR-STR-009-01
  - ATS-MBR-STR-009-02
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 10
isolation: A uniquely named local workspace and its seeded records; the suite owns its fixture data and cleanup.
evidence:
  - 'services-membership:tests/acceptance/configuration/MBR-ACC-0120.acceptance.ts'
  - 'react-console:acceptance/membership/journeys/configuration/MBR-ACC-0120.json'
bindings:
  - scenario: ATS-MBR-STR-009-01
    source: >-
      services-membership:tests/acceptance/configuration/MBR-ACC-0120.acceptance.ts#MBR-ACC-0120:
      Scenario 11 through the route: an identity-bound Chapter Membership program names its chapter unit
      type and its owning unit, refuses the wrong structure references in plain words and the missing
      identity type raw, and Kim holds a National and an Atlanta membership side by side
    provenance: test
  - scenario: ATS-MBR-STR-009-02
    source: >-
      services-membership:tests/acceptance/configuration/MBR-ACC-0120.acceptance.ts#MBR-ACC-0120:
      Scenario 11 through the route: an identity-bound Chapter Membership program names its chapter unit
      type and its owning unit, refuses the wrong structure references in plain words and the missing
      identity type raw, and Kim holds a National and an Atlanta membership side by side
    provenance: test
invocation: Manual Mocha invocation; the acceptance directory is outside the ordinary npm test tiers.
coverage_limit: >-
  Bindings identify the concrete cases executed in this file. A compound specification may also depend on
  other registered suites or remain partly proposed; registration is not a passing execution result.
catalogue: 'react-console:acceptance/membership/journeys/configuration/MBR-ACC-0120.json'
provenance: test
source:
  - 'services-membership:tests/acceptance/configuration/MBR-ACC-0120.acceptance.ts'
  - 'react-console:acceptance/membership/journeys/configuration/MBR-ACC-0120.json'
---

# Program structure-reference validation acceptance

## Verification Boundary

This acceptance program runs API steps through a manually invoked Mocha suite and uses the pinned console journey catalogue as its oracle. Program structure-reference validation acceptance defines the scope of its examples.

## What This Suite Proves

The suite executes the concrete examples named by its binding ledger. Those examples contribute to the linked capability or feature scenarios within the boundary of the test assertions.

## What It Does Not Prove

Registration supplies no fresh execution result or deployed conformance verdict. Browser behavior, deployed infrastructure and unasserted variants require separate evidence.

## Real Dependencies and Test Doubles

PostgreSQL, local Membership services and the suite’s persistence path are real. The business clock and caller fixtures are controlled by the harness. API requests enter the real dispatcher with contexts signed by a test key rather than Platform’s production signer. Accounting tables or product functions are local stand-ins; this suite does not certify the deployed Accounting service.

## Must Not Be Doubled

The Membership path under examination, transaction behavior and database constraints stay real. Replacing those boundaries would remove the persisted proof the suite is intended to supply.