--- id: CON-PFM-OPS-004 name: Workspace Application feature: FEAT-PFM-OPS-04 product_area: platform module: operations revision: 1 status: draft product_intent: confirmed implementation_evidence: observed source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: >- A workspace application combines an application’s commercial standing, operational state and resolved availability for one workspace. owned_by: MOD-PFM-OPS synonyms: - application standing - application availability not_to_be_confused_with: - Commercial coverage alone - The person’s launcher choices - Console navigation organization facets: - name: Catalog entry meaning: 'The stable application identity, name, ordering and licensing mode.' used_for: Recognizing current and retired applications. - name: Operational state meaning: The workspace’s preparation or deliberate suspension standing. used_for: Managing readiness independently of commercial eligibility. - name: Participants meaning: The owning service work required to prepare the application. used_for: Executing setup and permitted recovery. - name: Availability and explanation meaning: The combined usable state and its governing refusal reason. used_for: Supplying security and both application views. relationships: - to: CON-PFM-OPS-003 statement: Application availability combines commercial standing with readiness and respects explicit withholds. provenance: documented source: 'services-platform:docs/licensing.md#1. The rule' - to: CON-PFM-SEC-002 statement: 'Each workspace has one state record per prepared application, removed during retirement.' provenance: observed source: 'services-platform:modules/licensing/services/maintenance/tenant-participant.ts' - to: CON-PFM-OPS-001 statement: Background workspace activation establishes core application operational rows. provenance: documented source: 'services-platform:docs/licensing.md#6. Where the rows come from' lifecycle: - state: never provisioned meaning: No operational preparation is recorded. how_it_changes: A first grant or core workspace activation establishes state. - state: provisioning meaning: Declared preparation work is underway. how_it_changes: Participants finish or establish a failed outcome. - state: provisioning failed meaning: Preparation ended without completing its participants. how_it_changes: An eligible staff retry attempts preparation again. - state: enabled meaning: Operational preparation is complete. how_it_changes: Staff may deliberately suspend operation. - state: suspended meaning: Rhythm has stopped operation while retaining information. how_it_changes: An eligible staff resumption restores enabled state. acted_on_by: - CAP-PFM-OPS-014 - CAP-PFM-OPS-015 - CAP-PFM-OPS-016 visible_to: - ACT-PFM-001 - ACT-PFM-002 - ACT-PFM-004 - ACT-PFM-005 evidence: - >- services-platform at ad3f6a6: docs/licensing.md §1, §2, §4, §6, §9; modules/licensing/catalog (applications, application keys, participants), services/availability, services/enablement, services/persistence/tenant-applications.ts, db/applications.table.ts, db/tenant-applications.table.ts; modules/tenants/aws/api/tenant-applications.routes.ts. - >- react-console at baf6dae: components/configuration/applications/*, lib/applications/*; e2e/mock/application-access.mock.spec.ts. supersedes: [] --- # Workspace Application ## What It Is A workspace application describes one application’s standing for one workspace. It brings together the commercial licence, operational preparation and resulting availability. An administrator can use that combined picture to understand whether an application is usable and which part of the decision currently prevents it. The application catalog provides the stable application identity and readable name. The workspace’s operational record describes preparation, successful readiness or deliberate suspension. Commercial coverage can change independently of that record. Availability is resolved from those inputs for the current execution context rather than maintained as another editable status. The capabilities define how the inputs combine and how staff move operational standing. ## What It Is Not This concept is broader than a licence and narrower than everything a person sees in the launcher. A licence supplies commercial eligibility; the launcher also depends on that person’s application access. Being operationally enabled therefore cannot promise that every person may perform every action. Console navigation areas are presentation choices around applications rather than new commercial identities. A suspension is an operational decision that retains prepared information. It should not be confused with deleting the application’s records or withdrawing every commercial term that might license it. ## How It Is Used Rhythm staff prepare applications and investigate failed setup through the workspace’s HQ panel. A preparation invokes the declared participants and records the resulting state. Staff can deliberately suspend an enabled application, resume a suspension or recover failed preparation through its permitted transition. Customer administrators inspect Applications in Configuration. The customer view explains standing while protecting internal override reasons and attribution. Staff receive more detail to support investigation. A licence and a successful setup can therefore be understood separately before looking at the final availability result. When setup fails, the commercial decision can remain saved and the operational explanation identifies the participant needing attention. ## Its Facets **Catalog entry.** The catalog identifies the application, its presentation order and its licensing mode. Retired identities remain recognizable without being offered as current applications. **Operational state.** Preparation, failed preparation, enabled operation and suspension describe the workspace’s readiness. Absence means there is no prepared operational record. State reasons explain intentional suspension and failed work without inventing a separate commercial refusal. **Participants.** These are the owners of the preparation work needed by the application. Their lifecycle behavior keeps application setup connected to the modules that actually own data and configuration. **Availability and explanation.** The combined decision supplies one reason when use is unavailable. An always-available application has an explicit readiness exception, while a withhold remains effective even there. The customer and staff views explain the same overall standing at different levels of detail. ## How It Relates Licences supply the commercial side and workspace lifecycle supplies preparation participants. Background workspace provisioning enables the core applications at activation. Release backfill adds missing core operational records without replacing established decisions. Security consumes availability and retains separate responsibility for personal authority. The workspace owns the lifetime of operational rows and licensing decisions that are removed during retirement. ## What It Could Become The product should strengthen concurrent transition handling so one action cannot overwrite a newer operational decision after checking an older state. Audit and invalidation failures also need a deliberate recovery contract. The accepted commercial initialization direction is only partially implemented: first overrides can prepare missing state, while contract synchronization cannot. Future design should preserve these separate commercial and operational meanings while making the transition between them reliable.