Rhythm 2.0 Specifications

Appearance

SVC-PFM-CSH-console-shellConsole Shell

Markdown

SVC-PFM-CSH-console-shell

Console Shell

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleConsole Shell and NavigationRevision1

Read atreact-console baf6dae3services-platform ad3f6a65

Console Shell ​

What This Service Is For ​

The shell turns Platform answers into the shared console experience: start-up states, page space, navigation, context entry and application explanations. It is implemented in the console and serves no API of its own.

Boundary ​

The four owned objects describe client presentation. Security supplies identity and authority, Metadata supplies record placements, and Operations supplies application availability. Hosted search, attention, alerts, recent records, financial context and assistant behavior stay with their owning modules.

Operations in Words ​

The operations below describe consumption. Start-up asks for the security context, strictly when an address names a workspace and otherwise with a remembered preference. A strict refusal or failure can require fallback reads. Full refresh uses the current workspace context, while application refresh reads only applications and features into the client snapshot. Navigation reads placed record types, falling back to definition and custom-app lists. The administrator overview reads workspace availability. Each listed read is excluded from configurable intake with an explicit reason.

Events and Jobs ​

An in-browser application-refusal signal starts a refresh. It is not a published Platform event. The shell schedules no service jobs and performs no model inference. The remembered workspace and sidebar cookie are browser preferences.

Consistency Guarantees ​

Context-change tickets prevent old answers from replacing a newer workspace. This client ordering is not a database transaction. Application refresh checks both ticket and selected workspace, retaining the previous list on failure. Security reads can stamp authentication and settle expired grants; these effects remain Security responsibilities.

The recorded deployment enables licensing and application-access enforcement. The mode readers default to off when configuration is absent or unreadable, so that deployment assumption must be preserved by the owning services. The console still derives domain visibility from the returned application list.

Owns
DOM-PFM-CSH-001DOM-PFM-CSH-002DOM-PFM-CSH-003DOM-PFM-CSH-004
Repository
react-console

Controls

50 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-005 TC-CHG-006 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-IAM-001 TC-IAM-002 TC-IAM-003 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-002 TC-MON-003 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-PRV-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Does Not Own

  • Identity, sessions, reachable workspaces and staff clearance remain Security responsibilities.
  • Operations owns licensing records and application availability.
  • Metadata owns custom record definitions, apps and placements.
  • Hosted tools retain the ownership of their respective modules.

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