---
id: TST-PFM-OPS-059
title: Audit events queries
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.queries.integration.spec.js
implements:
  - ATS-PFM-OPS-009-04
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.queries.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.queries.integration.spec.js#answers
    the event whole, every mapped field
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.queries.integration.spec.js#answers
    nothing for an id no event has
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.queries.integration.spec.js#answers
    nothing for an event of another tenant
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.queries.integration.spec.js#finds
    an event by the occurrence key its actor used
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.queries.integration.spec.js#does
    not find another actor’s event under the same key
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.queries.integration.spec.js#answers
    every event of the actor, newest first, with the tie broken by the id
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.queries.integration.spec.js#answers
    the last page with no cursor, so a client knows the history is exhausted
  - >-
    services-platform:modules/audit/tests/integration/services/persistence/audit-events.queries.integration.spec.js#answers
    every element of an event, mapped (the newest, which is one of the tie)
---

# Audit events queries

## 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 inspect stable event ordering and continuation across tied timestamps under actor and workspace filters. 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.