---
id: TST-PFM-QRY-194
title: Platform reconcile coverage
kind: integration
product_area: platform
module: queries
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  rhythm-v2-docs: 99376625d3e7ac26936413cfc31a88fba6562464
repository: services-platform
files:
  - modules/data-exports/tests/integration/services/export-coverage/reconcile-coverage.integration.spec.js
implements:
  - ATS-PFM-QRY-018-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/data-exports/tests/integration/services/export-coverage/reconcile-coverage.integration.spec.js
assertion_bindings:
  - scenario: ATS-PFM-QRY-018-10
    source:
      - >-
        services-platform:modules/data-exports/tests/integration/services/export-coverage/reconcile-coverage.integration.spec.js#records
        each new dataset with the registry’s next version, and reads it back with its labels and without its
        absent reason and retirement
      - >-
        services-platform:modules/data-exports/tests/integration/services/export-coverage/reconcile-coverage.integration.spec.js#refuses
        a shape changed under an unchanged version, logged at error and counted, leaving the registry as it
        was
      - >-
        services-platform:modules/data-exports/tests/integration/services/export-coverage/reconcile-coverage.integration.spec.js#retires
        a dataset no longer declared and restores it when declared again, the registry’s version moving each
        time
    scope: assertions cited by the scenario
    provenance: test
fixture_seams:
  - >-
    services-platform:modules/data-exports/tests/integration/services/export-coverage/reconcile-coverage.integration.spec.js:123
---

# Platform reconcile coverage

## Verification Boundary

The file invokes its service or persistence boundary against local integration fixtures.

## What This Suite Proves

Its assertions check reconcile coverage. 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 service or persistence operation whose behavior is asserted real. Database constraints and transactions cannot be replaced by fixture answers when they are the subject of the check.