---
id: TST-PFM-OPS-062
title: Audit api mapper
kind: unit
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts
implements:
  - ATS-PFM-OPS-008-04
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: 'Process-local inputs, registries and test adapters.'
evidence:
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts 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/unit/aws/api/audit-api-mapper.spec.ts#accepts the record, the
    visit’s key and nothing else (the negative control)
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts#accepts the metadata keys
    the store allows
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts#leaves metadata out of
    the request when the client sent none, rather than inventing an empty map
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts#records no screen when
    the client sends a blank one, rather than refusing the report
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts#records no screen when
    the client sends null for it, which is what a blank one becomes
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts#trims a record id, so a
    copied-and-pasted id is the same id
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts#refuses a record id that
    is nothing but whitespace, naming the field
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-api-mapper.spec.ts#passes a record type
    through unjudged, because the registry judges it and names the ones there are
---

# Audit api mapper

## Verification Boundary

This suite exercises record activity through its declared function or structural boundary. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks exercise audit api mapper 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 production logic under assertion is real. Inputs, registries or source files supply the declared test data; no live service workflow runs.

## Must Not Be Doubled

The production function, registry or builder under assertion remains real.