---
id: TST-PFM-OPS-058
title: Audit events
kind: integration
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js
implements:
  - ATS-PFM-OPS-008-06
  - ATS-PFM-OPS-008-07
  - ATS-PFM-OPS-010-08
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: >-
  The prepared local test database and suite-owned identifiers; existing hooks control rollback or
  cleanup.
evidence:
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js
    at ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: Bindings apply only to the listed specification scenarios.
assertion_sources:
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js#reports
    that this call is the one that recorded it
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js#answers
    the event whole, every mapped field as it was written
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js#takes
    the instant from the execution’s clock, never from the database’s own now()
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js#takes
    the tenant from the execution, which no caller of this service supplies
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js#writes
    exactly one row
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js#records
    the first delivery (the premise)
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js#reports
    that the second delivery recorded nothing
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.integration.spec.js#answers
    the first delivery’s event, not a new one
---

# Audit events

## Verification Boundary

This suite exercises record activity through production operations against the local database. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks exercise audit events within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. The scenario bindings name the attributed outcomes.

## What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database and production operations under test are real. The suite controls time where boundary checks require it.

## Must Not Be Doubled

The persistence operations, database constraints and reads under assertion remain real.