Apply workspace availability consistently

Purpose

Lifecycle availability closes unfinished or disabled workspaces to ordinary customer requests while retaining authorized support access.

How It Works

Applications answer availability from the workspace’s lifecycle and business status. An ordinary caller reaches an active workspace unless it is disabled. Unfinished, failed and outgoing workspaces otherwise return a common unavailable response. Loading has a route exception for data-job work. Authorized staff on system routes retain access before that loading check applies. During destruction, staff can read through the gate but cannot write. Missing workspaces are unavailable to everyone. Each process caches the underlying facts for a short window, and the process making a lifecycle change invalidates its local entry. Background enumeration and derived-data processing have their own documented eligibility rules.

Relationships

• Preserve valid workspace lifecycle states: Lifecycle policy supplies the state and business-mode facts used by availability.
• Control the initial import and subsequent opening: Its loading period and activation decision control initial import availability.
• Schedule deliberate workspace deletion: The capabilities share the workspace’s recorded lifecycle decision.
• Revalidate the irreversible deletion decision: The capabilities share the workspace’s recorded lifecycle decision.