---
id: TST-PFM-TNL-091
title: Platform workspace access policy
kind: unit
product_area: platform
module: tenant-lifecycle
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/tenants/tests/unit/services/access/tenant-availability.spec.js
implements:
  - ATS-PFM-TNL-005-05
  - ATS-PFM-TNL-005-06
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Own in-process inputs and any installed dependency seams; restore process state after the file.
evidence:
  - 'services-platform:modules/tenants/tests/unit/services/access/tenant-availability.spec.js'
  - >-
    services-platform:modules/tenants/tests/unit/services/access/tenant-availability.spec.js imports
    ../../../../db/tenants.table
  - >-
    services-platform:modules/tenants/tests/unit/services/access/tenant-availability.spec.js imports
    ../../../../services/access/tenant-availability
binding_scope: >-
  Each implements link names a scenario whose retained cited checks all occur in this file. Partial assertions
  for other scenarios remain evidence only.
partial_scenario_evidence:
  - scenario: ATS-PFM-TNL-005-03
    references:
      - >-
        services-platform:modules/tenants/tests/unit/services/access/tenant-availability.spec.js#is reads only
        for staff once destruction has begun, so support can still inspect it
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
  - scenario: ATS-PFM-TNL-005-04
    references:
      - >-
        services-platform:modules/tenants/tests/unit/services/access/tenant-availability.spec.js#serves the
        upload protocol, which is what the load is made of
      - >-
        services-platform:modules/tenants/tests/unit/services/access/tenant-availability.spec.js#serves staff,
        who reach every tenant on a system route
    provenance: test
    scope: partial assertions; no complete scenario implementation claimed
---
# Platform workspace access policy

## Verification Boundary

The suite calls policy, mapping, manifest or dependency-injected code in process. Its assertions establish the named local behavior without a deployed API or a migrated cross-application workflow.

## What This Suite Proves

Workspace access policy is the inspected subject. The implements links identify scenarios whose cited checks occur in this file. The original test-title references delimit those checks; partial contributions to other combined scenarios remain evidence only.

## What It Does Not Prove

Source inspection supplies no passing run. The suite does not establish console behavior, deployment configuration, complete removal in every application or recovery from a provider failure beyond its declared seams. A local zero inventory covers declared and seeded resources only.

## Real Dependencies and Test Doubles

The source uses in-process policy and manifest inputs, and dependency seams where declared. Imported libraries are part of the exercised code; collaborator answers do not establish database enforcement or provider behavior.

## Must Not Be Doubled

Keep the policy, mapper, declaration or formatting function named by the source real; do not replace its return value with the expected answer. Any future database or API qualification must add the real boundary separately.