---
id: TST-PFM-INT-474
title: record facts
kind: integration
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - >-
    services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#answers
      TRUE for a contact whose affiliations satisfy the exists criterion
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#answers
      FALSE for a contact whose affiliations do not
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#answers
      UNKNOWN for a criterion over a fact the contact does not hold
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#answers
      FALSE for a contact of another tenant, which its own tenant answers TRUE
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#answers
      FALSE for an id no record has
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#reads
      relative dates from the today the SDK passes
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#reads
      as the eligibility reader, which is refused without the query reader’s grants or the owner’s
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#lets
      the query layer refuse a dataset it does not register
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#answers
      the rule’s adjustment for a Northeast member, 15 percent of the package in minor units
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#answers
      rule_not_applicable for a member elsewhere
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js#asks
      the query layer once for a record fact the request repeats, and again for another contact
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/extensions/tests/integration/services/rules/record-facts.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# record facts

## Verification Boundary

This database and service suite exercises record facts. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The suite contains executable checks, but no detailed scenario binding is verified in this pass.

## What It Does Not Prove

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.