--- id: TST-PFM-SEC-259 title: Provisioning notices 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/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js implements: - ATS-PFM-SEC-003-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/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#telling the staff member who asked for a tenant how its provisioning ended - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#a provisioning that opened the tenant - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#is a provisioning that succeeded for a requester with an e-mail address - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#sends the requester one message - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#names the tenant and says the tenant is ready in the subject - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#links to the job’s own page in Rhythm HQ, so the requester can read the steps - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#records one delivered notice of the succeeded outcome, against the requester - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#sends nothing a second time when the activate task runs again - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#leaves the notice row exactly as the first run left it - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#a provisioning that failed - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#is a provisioning that failed with a summary of its own - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#tells the requester it failed, naming the tenant - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#repeats the failure summary the job recorded, so the requester reads why - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#says the tenant is left standing and can be retried or deleted - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#records one delivered notice of the failed outcome - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#sends nothing more when the reconciler applies the same consequence afterwards - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#a notice this environment withholds - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#records the notice as suppressed, which counts as handled - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#still says when it was handled, so nothing claims it again - provenance: test source: >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js#builds the message all the same, which is what the delivery policy then withholds dependency_evidence: >- The prepared PostgreSQL database supplies the persisted fixtures and constraints exercised here. The suite controls Cognito, message delivery, workflow execution, remote service participants at the declared seams; those collaborators remain outside its live proof. evidence: - >- services-platform:modules/tenants/tests/integration/services/provisioning/provisioning-notices.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/tenants/tests/integration/services/provisioning/provisioning-notices.integration.spec.js explicit_no_doubles: false identified_double_boundaries: - Cognito - message delivery - workflow execution - remote service participants --- # Provisioning notices 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 provisioning notices. ## 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 controls Cognito, message delivery, workflow execution, remote service participants at the declared seams; those collaborators remain outside its live proof. ## 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.