---
id: TST-PFM-OPS-063
title: Audit evaluated keys
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-evaluated-keys.spec.ts
implements: []
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-evaluated-keys.spec.ts at
    ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: This existing engineering suite is registered without claiming a complete specification scenario.
assertion_sources:
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-evaluated-keys.spec.ts#serves the report
    route at all (premise)
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-evaluated-keys.spec.ts#is allowed by
    Platform’s own create key alone
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-evaluated-keys.spec.ts#resolves every
    viewable record type’s read permission into the slice
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-evaluated-keys.spec.ts#resolves the query
    permission of every viewable record type’s dataset into the slice
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-evaluated-keys.spec.ts#resolves the
    organizations dataset’s query key, the one the dev defect lacked
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-evaluated-keys.spec.ts#evaluates exactly the
    read and dataset keys of the registry, and nothing else of another application
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-evaluated-keys.spec.ts#names the record keys
    on the report route only, the history routes reading nothing of another application
  - >-
    services-platform:modules/audit/tests/unit/aws/api/audit-evaluated-keys.spec.ts#is accepted by the
    registry manifest generator, so the release that carries it can be published
---

# Audit evaluated keys

## 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 evaluated keys within the file’s declared setup and assertion boundary. The structured assertion anchors distinguish these checks from the surrounding feature flows. No complete specification scenario is attributed to this suite yet.

## 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.