---
id: TST-PFM-QRY-307
title: Platform start and reconcile generations
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/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js
implements:
  - ATS-PFM-QRY-003-10
  - ATS-PFM-QRY-003-11
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/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js
assertion_bindings:
  - scenario: ATS-PFM-QRY-003-10
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js#fails
        the generation no worker is going to settle, with the code an operator reads
      - >-
        services-platform:modules/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js#gives
        a generation the worker’s whole timeout and a margin before calling it abandoned
      - >-
        services-platform:modules/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js#deletes
        the generation past its thirtieth day, request and outcome together
      - >-
        services-platform:modules/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js#leaves
        a verdict already written alone, so a worker that finished mid-sweep wins
    scope: assertions cited by the scenario
    provenance: test
  - scenario: ATS-PFM-QRY-003-11
    source:
      - >-
        services-platform:modules/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js#refuses
        a query on screen naming a field nobody can query, listing the problem under the property it is about
      - >-
        services-platform:modules/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js#refuses
        a query on screen built for another dataset, which is not the query this request is about
      - >-
        services-platform:modules/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js#fails
        the generation at once when the worker cannot be started, and says so to the caller
    scope: assertions cited by the scenario
    provenance: test
fixture_seams:
  - >-
    services-platform:modules/queries/tests/integration/services/generate/start-and-reconcile-generations.integration.spec.js:372
---

# Platform start and reconcile generations

## Verification Boundary

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

## What This Suite Proves

Its assertions check start and reconcile generations. 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.