---
id: TST-MBR-MEM-017
title: Membership reconstruction from recorded knowledge
kind: integration
product_area: membership
module: memberships
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
repository: services-membership
files:
  - modules/history/tests/integration/membership-as-of.integration.spec.ts
implements:
  - ATS-MBR-MEM-018-06
  - ATS-MBR-MEM-018-07
  - ATS-MBR-MEM-018-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  A suite-owned workspace and test identifiers; suites that use shared seed data
  require the source’s serial execution and cleanup policy.
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/history/tests/integration/membership-as-of.integration.spec.ts
assertion_anchors:
  - scenario: ATS-MBR-MEM-018-06
    source: >-
      services-membership:modules/history/tests/integration/membership-as-of.integration.spec.ts#answers
      Jo’s chapters on the date with each unit’s name, parent and ancestors then
  - scenario: ATS-MBR-MEM-018-06
    source: >-
      services-membership:modules/history/tests/integration/membership-as-of.integration.spec.ts#answers
      the committee seats as unavailable where Committees’ versions do not exist
  - scenario: ATS-MBR-MEM-018-06
    source: >-
      services-membership:modules/history/tests/integration/membership-as-of.integration.spec.ts#answers
      the seats a committee appointment reader holds for the contact on the date
  - scenario: ATS-MBR-MEM-018-06
    source: >-
      services-membership:modules/history/tests/integration/membership-as-of.integration.spec.ts#answers
      a membership custom field as it was recorded at the end of the date
  - scenario: ATS-MBR-MEM-018-06
    source: >-
      services-membership:modules/history/tests/integration/membership-as-of.integration.spec.ts#answers
      the contact as it is now, said to be captured rather than reconstructed
  - scenario: ATS-MBR-MEM-018-07
    source: >-
      services-membership:modules/history/tests/integration/membership-as-of.integration.spec.ts#answers
      every FAA membership as the live read does, known now and as recorded now
  - scenario: ATS-MBR-MEM-018-08
    source: >-
      services-membership:modules/history/tests/integration/membership-as-of.integration.spec.ts#answers
      the term as it was known before the correction, with a known_at before it
  - scenario: ATS-MBR-MEM-018-08
    source: >-
      services-membership:modules/history/tests/integration/membership-as-of.integration.spec.ts#answers
      the corrected term with a known_at after the correction
---

# Membership reconstruction from recorded knowledge

## Verification Boundary

Attributed revisions and dated reconstruction run against the prepared database.

## 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 local pass does not prove live Committees history or history for every undeclared owner stream. Registration records existing code and leaves execution and conformance unverified.

## Real Dependencies and Test Doubles

Version capture, revision settlement and membership persistence remain real. Neighbor records, supplied callers and any appointment reader are controlled fixtures.

## Must Not Be Doubled

Keep the prepared database, workspace boundary, exercised owner constraints and the business operation under test real. A partner double cannot substitute for the Membership write this suite claims to exercise.