---
id: TST-PFM-OPS-100
title: Licence overrides
kind: integration
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js
implements: []
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/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js
    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/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js#answers
    the override it wrote, with the caller as its author and version 1
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js#answers
    it as unrevoked, which is what every new override is
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js#keeps
    the window it was given, in the wire form every instant of this API has
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js#starts
    at the instant it was made when the caller named no start, so an override is never dormant
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js#trims
    the reason it was given, so no override is stored with padding around its explanation
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js#writes
    exactly one row, which is what the reads below are counting
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js#writes
    a withhold as readily as a grant, because refusing an application is a decision too
  - >-
    services-platform:modules/licensing/tests/integration/services/persistence/licence-overrides.integration.spec.js#refuses
    a grant on a customer tenant with no end date, naming the tenant and its type
---

# Licence overrides

## Verification Boundary

This suite exercises application licensing 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 validate and retain staff exceptions, record withdrawal attribution, reject repeated withdrawal and read decisions within the requested workspace. 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 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.