---
id: TST-MBR-MEM-009
title: Purchase audience and proration decisions
kind: unit
product_area: membership
module: memberships
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
repository: services-membership
files:
  - modules/commerce-participant/tests/unit/pricing-policy.spec.ts
implements:
  - ATS-MBR-MEM-009-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Literal fixtures local to each test.
verification_notes: >-
  Bindings describe the assertions reviewed at the pinned commit; the suite is
  not executed by this documentation job.
coverage_gap: null
evidence:
  - >-
    services-membership:modules/commerce-participant/tests/unit/pricing-policy.spec.ts
assertion_anchors:
  - scenario: ATS-MBR-MEM-009-08
    source: >-
      services-membership:modules/commerce-participant/tests/unit/pricing-policy.spec.ts#prices
      an enrolment as new
  - scenario: ATS-MBR-MEM-009-08
    source: >-
      services-membership:modules/commerce-participant/tests/unit/pricing-policy.spec.ts#prices
      a renewal as renewing
  - scenario: ATS-MBR-MEM-009-08
    source: >-
      services-membership:modules/commerce-participant/tests/unit/pricing-policy.spec.ts#falls
      back to new when the grid has no row for the operation’s audience (D-5: a
      blank rejoining inherits new)
  - scenario: ATS-MBR-MEM-009-08
    source: >-
      services-membership:modules/commerce-participant/tests/unit/pricing-policy.spec.ts#prorates
      a first term by the package’s enrolment proration, on the original price,
      for new members
  - scenario: ATS-MBR-MEM-009-08
    source: >-
      services-membership:modules/commerce-participant/tests/unit/pricing-policy.spec.ts#never
      prorates a renewal: the proration is null, as contracts 0.3.0 says "none"
---

# Purchase audience and proration decisions

## Verification Boundary

The suite exercises pure membership decisions against literal inputs and expected outputs.

## What This Suite Proves

The structured bindings identify the capability and feature cases whose reviewed assertions this suite executes. Source anchors preserve the evidence for each binding.

## What It Does Not Prove

A pure-rule pass does not prove persistence, permission enforcement through the API or a complete business lifecycle. Registration records existing code and leaves execution and conformance unverified.

## Real Dependencies and Test Doubles

The decision functions and schemas are real. Literal inputs and checked-in fixtures supply their data; this boundary does not call live owners.

## Must Not Be Doubled

Keep the decision function or schema under test real; replacing its result would remove the proof.