Rhythm 2.0 Specifications

Appearance

FAS-PFM-TNL-02Workspace Readiness and Access acceptance

Markdown

FAS-PFM-TNL-02

Workspace Readiness and Access acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-TNL-02
Capabilities
CAP-PFM-TNL-005, CAP-PFM-TNL-006

Product areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-platform ad3f6a65services-crm a8d1364fservices-commerce c8b66a98services-committees 36129c24services-membership 5994c270services-submissions 64236c19services-websites 5fc6823cservices-marketing d071a159rhythm-v2-docs d318a948

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 ​

RevisionChangeScenarioWhy
1initialallDefine cumulative feature checks from the examined capability scenarios and known failure boundaries.

Scenarios

5 scenarios proving FEAT-PFM-TNL-02 as a whole.

01 Staff change business status while ordinary access follows lifecycle behaviour proposed
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.
Data
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.
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
02 Cancellation changes lifecycle without reopening disabled access interactionnegative proposed
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.
Data
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.
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
03 Construction, loading and activation preserve one set of system facts lifecycle proposed
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.
Data
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.
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
04 Destruction keeps gated staff reads but refuses their mutations permissionnegative proposed
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.
Data
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.
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
05 Cache expiry prevents stale status from becoming permanent availability regressionnegative proposed
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.
Data
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.
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

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software