---
id: TST-ACC-BKS-194
title: Workspace Availability rule suite
kind: unit
product_area: accounting
module: books
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-accounting
files:
  - modules/maintenance/tests/unit/lifecycle/tenant-availability.spec.js
implements:
  - ATS-ACC-BKS-019-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: Each example owns its input values and configured doubles.
assertion_bindings:
  - scenario: ATS-ACC-BKS-019-06
    source: >-
      services-accounting:modules/maintenance/tests/unit/lifecycle/tenant-availability.spec.js#serves
      only an active tenant that is not disabled, and refuses every other
      combination
  - scenario: ATS-ACC-BKS-019-06
    source: >-
      services-accounting:modules/maintenance/tests/unit/lifecycle/tenant-availability.spec.js#serves
      a loading tenant whatever its status, and answers every other state as it
      does an ordinary route
  - scenario: ATS-ACC-BKS-019-06
    source: >-
      services-accounting:modules/maintenance/tests/unit/lifecycle/tenant-availability.spec.js#serves
      every state but the one being deleted, which it may only read
  - scenario: ATS-ACC-BKS-019-06
    source: >-
      services-accounting:modules/maintenance/tests/unit/lifecycle/tenant-availability.spec.js#reads
      it again once the thirty seconds are up
unmapped: false
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/maintenance/tests/unit/lifecycle/tenant-availability.spec.js
execution_notes: >-
  The file exists at the pinned revision; this registration records no execution
  result.
---

# Workspace Availability rule suite

## Verification Boundary

The suite evaluates workspace operations logic directly. Its boundary is the called functions and configured dependencies, rather than a running service.

## What This Suite Proves

The individual assertion references identify the acceptance outcomes this file exercises. When a scenario spans several suites, this file supplies only its listed assertions; qualification must include the other bindings and any recorded coverage finding.

## What It Does Not Prove

Direct function checks do not prove route enforcement, transaction behavior or deployed integration. No result is claimed for the pinned revision until the suite runs and its evidence is reviewed.

## Real Dependencies and Test Doubles

The called rule or mapping functions are real code. Test inputs and any dependency doubles remain confined to individual examples.

## Must Not Be Doubled

The production function or carried adapter named by the file remains the subject under test; a second implementation of its expected answer is not a substitute.