---
id: FAS-PFM-TNL-02
title: Workspace Readiness and Access acceptance
feature: FEAT-PFM-TNL-02
product_area: platform
module: tenant-lifecycle
revision: 1
status: proposed
product_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  services-committees: 36129c24daeaadcdb339218c38cdeaff9861359d
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  services-submissions: 64236c19be89579ef5897aad7de3925ed3ce03bf
  services-websites: 5fc6823c69d5e6f208c21dba8c0eb3132f8bdc4c
  services-marketing: d071a159fe9782bb71ff246d5c67d5bbfe07fbfa
  rhythm-v2-docs: d318a948692343e2f0a7ecc2e11c50db179a8c95
capabilities:
  - CAP-PFM-TNL-005
  - CAP-PFM-TNL-006
scenarios:
  - id: FAS-PFM-TNL-02-01
    title: Staff change business status while ordinary access follows lifecycle
    kind: behaviour
    exercises:
      - CAP-PFM-TNL-005
      - CAP-PFM-TNL-006
    relies_on:
      - ATS-PFM-TNL-005-01
      - ATS-PFM-TNL-006-05
    preconditions: The workspace is active in implementation; authorized staff and a customer administrator are available.
    steps: 'Disable it as staff, read both status axes and try ordinary customer access after cache expiry.'
    expected: Lifecycle remains active while business status is disabled; ordinary access returns unavailable.
    negative: false
    data_needs: >-
      Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture
      records named by the relied-on capability scenarios. Use controlled clocks and faults only where the
      scenario requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
  - id: FAS-PFM-TNL-02-02
    title: Cancellation changes lifecycle without reopening disabled access
    kind: interaction
    exercises:
      - CAP-PFM-TNL-005
      - CAP-PFM-TNL-006
      - CAP-PFM-TNL-014
    relies_on:
      - ATS-PFM-TNL-005-01
      - ATS-PFM-TNL-006-04
      - ATS-PFM-TNL-014-05
    preconditions: A disabled workspace has a reversible deletion request.
    steps: 'Cancel deletion, read lifecycle and status, and check ordinary customer access with a fresh cache.'
    expected: The decision becomes cancelled and lifecycle active; disabled status keeps ordinary access closed.
    negative: true
    data_needs: >-
      Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture
      records named by the relied-on capability scenarios. Use controlled clocks and faults only where the
      scenario requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md;
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-014-hold-release-or-call-off-a-deletion-before-destruction.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-014-hold-release-or-call-off-a-deletion-before-destruction.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-014-hold-release-or-call-off-a-deletion-before-destruction.md
  - id: FAS-PFM-TNL-02-03
    title: 'Construction, loading and activation preserve one set of system facts'
    kind: lifecycle
    exercises:
      - CAP-PFM-TNL-005
      - CAP-PFM-TNL-006
      - CAP-PFM-TNL-011
    relies_on:
      - ATS-PFM-TNL-005-08
      - ATS-PFM-TNL-006-01
      - ATS-PFM-TNL-011-05
    preconditions: An implementation workspace can move from construction through its first initial load.
    steps: >-
      Finish construction, open loading, activate the load and attempt a client edit of lifecycle and first
      opening time.
    expected: >-
      Ordinary availability follows those periods; activation keeps load attribution and business status, and
      client input cannot replace system-owned lifecycle facts.
    negative: false
    data_needs: >-
      Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture
      records named by the relied-on capability scenarios. Use controlled clocks and faults only where the
      scenario requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md;
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md
  - id: FAS-PFM-TNL-02-04
    title: Destruction keeps gated staff reads but refuses their mutations
    kind: permission
    exercises:
      - CAP-PFM-TNL-005
      - CAP-PFM-TNL-006
    relies_on:
      - ATS-PFM-TNL-005-03
      - ATS-PFM-TNL-006-05
    preconditions: The target is disabled and deleting; a staff system caller and customer caller are prepared.
    steps: 'Read and mutate through workspace-gated routes with both callers, then compare state facts.'
    expected: >-
      Staff reads remain admitted, gated mutations refuse and customer calls remain unavailable; this does not
      assert a guard on every HQ administration route.
    negative: true
    data_needs: >-
      Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture
      records named by the relied-on capability scenarios. Use controlled clocks and faults only where the
      scenario requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
  - id: FAS-PFM-TNL-02-05
    title: Cache expiry prevents stale status from becoming permanent availability
    kind: regression
    exercises:
      - CAP-PFM-TNL-005
      - CAP-PFM-TNL-006
    relies_on:
      - ATS-PFM-TNL-005-06
      - ATS-PFM-TNL-006-05
    preconditions: A process cached active implementation standing before an authorized staff disable.
    steps: Check availability within the cached interval and again after its maximum lifetime.
    expected: >-
      The cache can retain the earlier answer during its bounded lifetime; expiry reads disabled status and
      refuses ordinary access.
    negative: true
    data_needs: >-
      Create run-owned target and comparison workspaces, distinct staff and customer callers, and the fixture
      records named by the relied-on capability scenarios. Use controlled clocks and faults only where the
      scenario requires them.
    bound_to: []
    provenance: proposed
    source: >-
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
      rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
    action_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
    assertion_evidence:
      provenance: proposed
      source: >-
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
        rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
evidence:
  - >-
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
  - >-
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md;
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-014-hold-release-or-call-off-a-deletion-before-destruction.md
  - >-
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md;
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-011-open-a-workspace-for-its-initial-import-and-let-its-people.md
  - >-
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
  - >-
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-005-keep-people-and-background-work-out-of-a-workspace-that-is.md;
    rhythm-v2-docs:specs/platform/tenant-lifecycle/planning/capabilities/CAP-PFM-TNL-006-keep-every-workspace-s-lifecycle-state-truthful.md
execution_gap: FND-PFM-TNL-086
---
# Workspace Readiness and Access: Feature Acceptance Suite

## What the Feature Must Do as a Whole

The workspace is active in implementation; authorized staff and a customer administrator are available. The behaviour case follows that staff outcome through the participating capabilities and compares their records at the end. Separate lifecycle, permission and regression cases test the consequences of interruption or refusal. These are proposed combined checks; inspected component tests supply their prerequisites but do not establish a passing feature run.

## Interactions Between Capabilities

Cancellation changes lifecycle without reopening disabled access. A disabled workspace has a reversible deletion request. The case changes the upstream condition and checks the downstream outcome described in its structured assertions. Where the chain crosses a feature boundary, the scenario names the other capability while the suite retains its own feature membership.

## Regression Record

| Revision | Change | Scenario | Why |
|---|---|---|---|
| 1 | initial | all | Define cumulative feature checks from the examined capability scenarios and known failure boundaries. |