---
id: TST-PFM-INT-493
title: integration audit events table
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/integrations/tests/integration/db/integration-audit-events.table.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/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#refuses
      a target kind outside its list
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#refuses
      an actor wall outside its list
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#trims
      the action it stores
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#answers
      the tenant its own events through the persistence service, with the actor and the wall
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#answers
      another tenant none of them
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#pages
      newest first with the instant and id of the last event
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#lets
      the application role insert and read an event (the premise)
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#refuses
      an UPDATE of an event by the application role, so a trail cannot be rewritten
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#refuses
      a DELETE of an event by the application role, so a trail cannot be erased
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js#still
      holds the event after both refusals
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/db/integration-audit-events.table.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# integration audit events table

## Verification Boundary

This database and service suite exercises integration audit events table. 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.