---
id: TST-PFM-OPS-060
title: Record view
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/record-views/record-view.integration.spec.js
implements:
  - ATS-PFM-OPS-008-01
  - ATS-PFM-OPS-008-02
  - ATS-PFM-OPS-008-03
  - ATS-PFM-OPS-008-05
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/record-views/record-view.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/record-views/record-view.integration.spec.js#attributes
    the view to the signed-in caller, who named nobody
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/record-view.integration.spec.js#records
    it in the tenant of the execution, which the body never carries
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/record-view.integration.spec.js#records
    the record the caller opened, under the registry’s canonical type
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/record-view.integration.spec.js#records
    the one event type the store holds
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/record-view.integration.spec.js#keeps
    the metadata the client sent
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/record-view.integration.spec.js#reports
    that this call recorded it rather than finding it
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/record-view.integration.spec.js#logs
    the view with the ids an operator needs and nothing about the record’s contents
  - >-
    services-platform:modules/audit/tests/integration/services/record-views/record-view.integration.spec.js#writes
    exactly one row
---

# Record view

## 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 resolve targets under caller authority, append visits, reject unsupported or unreadable targets and distinguish repeated delivery from conflicting visit identity. 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.