---
id: TST-MBR-MEM-034
title: Package grant date and overlap decisions
kind: unit
product_area: membership
module: memberships
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
repository: services-membership
files:
  - modules/memberships/tests/unit/grant-plan.spec.ts
implements:
  - ATS-MBR-MEM-006-02
  - ATS-MBR-MEM-006-03
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/memberships/tests/unit/grant-plan.spec.ts'
assertion_anchors:
  - scenario: ATS-MBR-MEM-006-02
    source: >-
      services-membership:modules/memberships/tests/unit/grant-plan.spec.ts#plans
      a granted term with the primary term’s dates for a grant same as primary
  - scenario: ATS-MBR-MEM-006-02
    source: >-
      services-membership:modules/memberships/tests/unit/grant-plan.spec.ts#plans
      a granted term by the grant’s own rule, never starting before the primary
      term
  - scenario: ATS-MBR-MEM-006-02
    source: >-
      services-membership:modules/memberships/tests/unit/grant-plan.spec.ts#plans
      the next granted term on a renewal of the granting package
  - scenario: ATS-MBR-MEM-006-03
    source: >-
      services-membership:modules/memberships/tests/unit/grant-plan.spec.ts#skips
      a grant the member already holds for those dates, naming the term
---

# Package grant date and overlap 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.