---
id: TST-PFM-SEC-195
title: Authorizer source unit checks
kind: unit
product_area: platform
module: security
revision: 2
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/security/tests/unit/authorizer/authorizer-source.spec.ts
implements:
  - ATS-PFM-SEC-015-02
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: The suite owns its input fixtures and installed doubles.
assertion_evidence:
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#the
      authorizer’s source
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#reads the
      whole slice, so the scan below means something
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#never
      mentions createJit: the authorizer creates nothing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#never
      mentions newRhythmUserId: the authorizer creates nothing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#never
      mentions mintUserId: the authorizer creates nothing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#never
      mentions jit_binding: the authorizer creates nothing
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#never
      inserts or updates anything in Postgres: every port it has is a read
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#writes to
      the registry table only from the registry’s own modules
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#logs
      through @rhythmsoftware/macroservice-logging and never console
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#reads the
      clock only through @rhythmsoftware/macroservice-time: no native Date anywhere in the slice
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#carries no
      Auth0 or legacy branch, no impersonation, and no passthrough or generated manifest
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#the ports
      the schema repositories provide
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#implement
      every port the authorizer contract names
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#implement
      every publish port, which needs the registry table to read a prepared catalog back
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#the
      authorizer’s configuration
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#builds from
      the four variables, defaulting the service and the TTL to caching off
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#takes the
      TTL and the service from the environment
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#takes the
      licence step’s mode from RHYTHM_LICENSING, and reads anything but the three modes as off
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#reads the
      peer APIs as apiId=service pairs, and refuses an entry that is not one
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#refuses a
      missing variable rather than defaulting it
  - provenance: test
    source: >-
      services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts#refuses a
      TTL that is not a whole number of seconds in range
dependency_evidence: >-
  The production function, schema or declaration runs over literal inputs. The source declares no
  substituted collaborator; this is an in-process decision or mapping check.
evidence:
  - 'services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts'
  - >-
    Static review at the recorded source revision; executable results remain not-run and conformance
    remains not-verified.
binding_note: >-
  Each binding names the scenario to which this file contributes assertions. A binding is not a
  recorded pass and does not extend the file’s dependency boundary.
examiner: codex
examined_at: '2026-10-23'
final_text: OpenAI
dependency_review:
  provenance: test
  source: 'services-platform:modules/security/tests/unit/authorizer/authorizer-source.spec.ts'
  explicit_no_doubles: true
  identified_double_boundaries: []
---
# Authorizer source unit checks

## Verification Boundary

The file evaluates production helpers with controlled inputs in-process. The assertion references identify the source checks for authorizer source.

## What This Suite Proves

The source assertions support the observations named in the bound scenarios. A scenario spanning multiple files must retain the other files’ contributions.

## What It Does Not Prove

This examination does not run the suite. Passing behavior, deployed conformance and the behavior of substituted dependencies require separate execution evidence.

## Real Dependencies and Test Doubles

The production function, schema or declaration runs over literal inputs. The source declares no substituted collaborator; this is an in-process decision or mapping check.

## Must Not Be Doubled

Keep the production helper, schema, matcher or declaration under examination real. Substituting the decision itself would remove the behavior the assertions exercise.