---
id: TST-PFM-QRY-209
title: Platform explorer preferences api
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/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js
implements:
  - ATS-PFM-QRY-009-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/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js'
assertion_bindings:
  - scenario: ATS-PFM-QRY-009-11
    source:
      - >-
        services-platform:modules/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js#answers the whole
        default arrangement: whose it is, which Explorer, nothing pinned and version zero
      - >-
        services-platform:modules/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js#saves a first
        arrangement at If-Match 0, the version the defaults were answered at (DEF-CRM-0391)
      - >-
        services-platform:modules/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js#refuses a later save
        that states no version as 409, so nothing is overwritten unread
      - >-
        services-platform:modules/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js#refuses more pinned
        views than an Explorer may hold as 400
      - >-
        services-platform:modules/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js#answers such an id
        back on the read that follows, rather than refusing the whole arrangement
      - >-
        services-platform:modules/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js#answers each person
        their own arrangement of the same Explorer
    scope: assertions cited by the scenario
    provenance: test
fixture_seams:
  - 'services-platform:modules/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js:56'
  - 'services-platform:modules/explorer/tests/e2e/explorer-preferences-api.e2e.spec.js:40'
---

# Platform explorer preferences api

## 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 explorer preferences api. 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.