---
id: TST-PFM-QRY-467
title: Platform snapshots
kind: api-lifecycle
product_area: platform
module: queries
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  rhythm-v2-docs: 99376625d3e7ac26936413cfc31a88fba6562464
repository: services-platform
files:
  - modules/snapshots/tests/e2e/snapshots.e2e.spec.js
implements:
  - ATS-PFM-QRY-019-01
  - ATS-PFM-QRY-019-02
  - ATS-PFM-QRY-019-05
  - ATS-PFM-QRY-019-10
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: 'The suite’s database fixtures, controlled execution contexts and file-owned external dependency seams.'
evidence:
  - 'services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js'
assertion_bindings:
  - scenario: ATS-PFM-QRY-019-01
    source:
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#lets the tenant’s own people read
        its periods
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#refuses another customer’s user
        the tenant’s periods
    scope: contributing assertions; the scenario combines multiple files
    provenance: test
  - scenario: ATS-PFM-QRY-019-02
    source:
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#lets a Rhythm Administrator list
        the runs
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#lets a Support Representative read
        the runs, through the HQ reader policy
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#refuses a Support Representative a
        request, which is managing snapshots
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#refuses a customer’s own
        administrator every HQ route, which are staff-only
    scope: assertions cited by the scenario
    provenance: test
  - scenario: ATS-PFM-QRY-019-05
    source:
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#plans a manual run as version 1 of
        a captured run, for the dispatcher to start
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#refuses a second request for the
        same month while the first is under way (409)
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#back-fills one run for each month
        of the range
    scope: assertions cited by the scenario
    provenance: test
  - scenario: ATS-PFM-QRY-019-10
    source:
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#refuses a request with no reason,
        naming the field
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#refuses a period that is not a
        month
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#refuses a snapshot type this
        environment does not run
      - >-
        services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js#refuses a page of 1,001 runs,
        naming the limit
    scope: assertions cited by the scenario
    provenance: test
fixture_seams:
  - 'services-platform:modules/snapshots/tests/e2e/snapshots.e2e.spec.js:24'
---

# Platform snapshots

## Verification Boundary

The file dispatches requests through the real route table and signed execution contexts against its local fixtures.

## What This Suite Proves

Its assertions check snapshots. The assertion bindings identify the corresponding acceptance examples and retain their original test-title citations.

## What It Does Not Prove

Local execution does not establish deployed queue scheduling, every external provider response or a passing result at the pinned revision.

## Real Dependencies and Test Doubles

The integration fixture and any imported dependency seams define the environment. Database-oriented checks use PostgreSQL; file-owned transport, clock, provider or worker seams isolate the explicitly controlled boundary.

## Must Not Be Doubled

Keep the dispatcher, route requirements and the handler behavior named by the assertions real. Review any new substitutions before treating the same acceptance bindings as unchanged.