Rhythm 2.0 Specifications

Appearance

CAP-PFM-CSH-013Keep staff work and workspace work in distinct contexts

Markdown

CAP-PFM-CSH-013

Keep staff work and workspace work in distinct contexts

Markdown
  • DocumentDraft
  • Product intentProposed
  • ImplementationObserved

Planning

Feature
FEAT-PFM-CSH-03
Key concepts
CON-PFM-CSH-001, CON-PFM-CSH-002, CON-PFM-CSH-003
Actors
ACT-PFM-004, ACT-PFM-005, ACT-PFM-002
Journeys
JNY-PFM-CSH-001
Related
CAP-PFM-CSH-010, CAP-PFM-CSH-012, CAP-PFM-CSH-005, CAP-PFM-CSH-006
Proved by
ATS-PFM-CSH-013
Exercised by
JNY-PFM-CSH-003

KindCapabilityProduct areaPlatformModuleConsole Shell and NavigationRevision2

Read atreact-console baf6dae3services-platform ad3f6a65

Keep staff work and workspace work in distinct contexts ​

Purpose ​

Rhythm staff distinguish platform administration in HQ from customer work in a workspace.

How It Works ​

Staff choose between their own operational work and customer work. The address supplies the primary context signal. Workspace entry can establish a customer context without changing the purpose of HQ. Entering HQ clears the selected workspace while retaining useful bookmark memory. A refused staff workspace link returns to HQ with an explanation. The product should verify both contexts as one complete browser journey.

Relationships ​

  • Security owns staff authority and workspace grants.
  • Workspace entry handles bookmarks and staff refusals.

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes
HQ and customer navigation are selected independently.Cleared staff links enter their requested workspace directly.
Surfaces
console
Intent sources
react-console:docs/url-architecture.md#6. Tenant from the URL (decided by Andrew 2026-10-14; final acceptance 2026-10-15)react-console:docs/url-architecture.md#11. Decisions made during the build, item 24 (Andrew, 2026-10-15) (decided by Andrew 2026-10-14; final acceptance 2026-10-15)

Controls

25 controls apply, from the corpus control catalogue.

TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-001 TC-IAM-002 TC-IAM-003 TC-IAM-004 TC-IAM-005 TC-LOG-001 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

KeyChecked atScope
console.systemconsoletenant
hq.*apiglobal

Business Rules

7 rules, 5 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

IdRuleKindEnforced atProvenance
01must prove
Proposed
For staff, HQ addresses select HQ mode and console addresses select workspace mode, with other addresses following whether a workspace is selected; non-staff always use workspace mode.
origin: react-console:docs/url-architecture.md#6. Tenant from the URL (decided by Andrew 2026-10-14; final acceptance 2026-10-15)
no proof recorded yet
calculationconsoleobserved
react-console:components/console/use-shell-mode.ts:useShellMode
02must prove
Proposed
Main navigation selects HQ links in HQ mode and workspace links in workspace mode without combining them.
no proof recorded yet
invariantconsoleobserved
react-console:components/console/app-sidebar.tsx:MainNavigation
03
Proposed
The HQ menu contains Home, Customers, Staff, Workspaces, Jobs, Notifications, AI Usage and Custom Query Tables.
policyconsoleobserved
react-console:components/console/nav-config.ts:hqLinks
04
Proposed
HQ mode replaces the header workspace switcher with the Rhythm HQ label.
policyconsoleobserved
react-console:components/console/site-header.tsx:SiteHeader
05must prove
Proposed
Inside a workspace the staff account menu offers HQ, and only workspace mode offers settings and My Responsibilities.
no proof recorded yet
permissionconsoleobserved
react-console:components/console/app-sidebar.tsx:AppSidebar
06must prove
Proposed
A bare-address staff landing opens HQ without selecting the remembered workspace, while retaining that memory for later older links.
origin: react-console:docs/url-architecture.md#11. Decisions made during the build, item 24 (Andrew, 2026-10-15) (decided by Andrew 2026-10-14; final acceptance 2026-10-15)
no proof recorded yet
lifecycleconsoletest
react-console:e2e/mock/staff-landing.mock.spec.ts#a staff member with a remembered tenant and a standing grant lands on /hq in HQ context
07must prove
Proposed
A bookmark for a workspace covered by a staff grant opens its page and query directly after sign-in or from HQ.
origin: react-console:docs/url-architecture.md#11. Decisions made during the build, item 24 (Andrew, 2026-10-15) (decided by Andrew 2026-10-14; final acceptance 2026-10-15)
no proof recorded yet
policyconsoletest
react-console:e2e/mock/url-architecture.mock.spec.ts#a staff member's bookmark into a standing-grant tenant opens that page and query, from Rhythm HQ too

Scenarios

IdGivenWhenThenProvenance
01A staff user has a remembered workspace but opens the bare address.The console completes its landing.HQ opens while the remembered workspace remains available for older links.test
react-console:e2e/mock/staff-landing.mock.spec.ts#a staff member with a remembered tenant and a standing grant lands on /hq in HQ context
02A standing staff grant covers the bookmarked workspace.The staff user follows the bookmark from HQ.The requested workspace page and query open directly.test
react-console:e2e/dev/url-architecture.dev.spec.ts#signed in on Rhythm HQ: opening it goes straight into the tenant

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