---
id: TST-PFM-TNL-025
title: Crm activity defaults
kind: integration
product_area: platform
module: tenant-lifecycle
revision: 1
status: draft
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
repository: services-crm
files:
  - >-
    modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.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: >-
  Run-owned target and comparison workspace records in the prepared test database; owner access is limited to
  fixture arrangement, independent inspection and cleanup of those records.
evidence:
  - >-
    services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js
  - >-
    services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js
    imports ../../../../../activities/db/activity-types.table
  - >-
    services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js
    imports ../../../../../activities/db/activity-outcomes.table
  - >-
    services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js
    imports ../../../../../activities/services/persistence/activity-types
  - >-
    services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js
    imports ../../../../services/participants/activities-participant
  - >-
    services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js
    imports ../../../../services/participants/activity-type-seeds
  - >-
    services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js
    imports ../../support
binding_scope: >-
  No complete ATS or FAS scenario implementation is claimed for this file. Partial assertions, if present,
  remain evidence rather than implements links.
partial_scenario_evidence:
  - scenario: ATS-PFM-TNL-008-03
    references:
      - >-
        services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js#adopts
        a type the customer made first under a seed’s id, rather than overwriting it
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
---
# Crm activity defaults

## Verification Boundary

The suite invokes production lifecycle services or persistence against its test database. Each fixture and directly called participant belongs to the repository named in the register; this is a local integration boundary.

## What This Suite Proves

Activity defaults is the inspected subject. The inspected engineering checks remain available in the register. Some may contribute partial assertions to capability scenarios, but the file is not claimed to implement any complete scenario; the unbound inventory records that remaining mapping work.

## What It Does Not Prove

Source inspection supplies no passing run. The suite does not establish console behavior, deployment configuration, complete removal in every application or recovery from a provider failure beyond its declared seams. A local zero inventory covers declared and seeded resources only.

## Real Dependencies and Test Doubles

The suite retains its database and production functions as shown by the cited source. Fixture clocks, contexts, seeded Platform facts or callback dependencies remain test inputs. The imported support is recorded as evidence; no external provider result is inferred from a local fixture.

## Must Not Be Doubled

Keep the production service or persistence function and the database constraints, row policies and guarded removal functions under test real. For dispatcher cases, keep route selection and authorization real as well. Provider and remote-application seams must remain explicit and cannot stand in for deployed cross-application qualification.