---
id: TST-PFM-SEC-175
title: Contact match database and service checks
kind: integration
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/security/tests/integration/services/portal/contact-match.integration.spec.js
implements:
  - ATS-PFM-SEC-020-01
  - ATS-PFM-SEC-020-02
  - ATS-PFM-SEC-020-03
  - ATS-PFM-SEC-020-04
  - ATS-PFM-SEC-020-06
  - ATS-PFM-SEC-020-07
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: Use the prepared test database and suite-owned fixture rows; retain shared seed records.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#security
      capability: portal likely-match
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#while
      CRM’s functions are not installed
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#answers
      none and links nothing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#with
      CRM’s functions
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#links
      the one contact holding the member’s own address without asking
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#creates
      and links a new contact when CRM finds nobody likely, recording no declined pair
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#never
      offers a contact another member of the tenant already links
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#a
      member who has to choose
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#is
      offered each candidate’s masked hints and channels, best first
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#is
      never shown a contact id
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#is
      refused a channel the candidate does not offer
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#is
      refused a candidate id that was not sealed for them
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#proving
      a candidate by e-mail
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#sends
      the code to that contact’s own address
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#answers
      the challenge and when its code expires
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#refuses
      a wrong code, saying how many attempts are left
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#links
      the member to the contact on the right code
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#refuses
      another challenge once the member is linked
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#a
      member who declines every candidate
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#is
      linked to a contact CRM created from the sign-up details
  - provenance: test
    source: >-
      services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js#names
      the best declined candidate, so staff review the pair
dependency_evidence: >-
  The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here.
  The suite’s own dependency setup determines which external collaborators are controlled;
  registration alone does not certify them as live.
evidence:
  - >-
    services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: >-
    services-platform:modules/security/tests/integration/services/portal/contact-match.integration.spec.js
  explicit_no_doubles: false
  identified_double_boundaries: []
---
# Contact match database and service checks

## Verification Boundary

The file exercises database or service behavior through the local integration harness. The assertion references identify the source checks for contact match.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite’s own dependency setup determines which external collaborators are controlled; registration alone does not certify them as live.

## Must Not Be Doubled

Keep the queried database, applicable constraints and transaction boundaries real. Provider substitutes cannot establish delivery, cloud execution or cross-service recovery.