Console start-up and working context

The Lifecycle

Transitions Explained

The production gate begins in loading and resolves session and context. Retry repeats that work while the failure screen stays visible. Address entry and programmatic switching can set a busy overlay on a ready context. Leaving for HQ follows a ready-to-ready path, clearing the workspace locally before its refresh completes.

What Cannot Happen

The gate does not mount content without a context. Older context-change answers cannot overwrite newer selections. A no-access start-up has no in-place retry control. The ready provider may retain the previous workspace during a refused entry, but the workspace gate withholds requested content until context matches.

Concurrency and Timing

A monotonically increasing ticket orders workspace changes. Tabs hold independent contexts and share browser preferences only where storage does so. Expiry parks live drafts; explicit sign-out forgets them and the remembered workspace.