---
id: ADR-PFM-CSH-002
title: Security Context Gates Console Mounting
product_area: platform
module: console-shell
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Gate production console mounting on a usable Security context, with distinct
  failure states and preference fallback when strict workspace entry does not
  yield one.
constrains:
  - DOM-PFM-CSH-001
  - STATE-PFM-CSH-001
  - WF-PFM-CSH-001
  - SCR-PFM-CSH-002
  - SVC-PFM-CSH-console-shell
origin: >-
  services-platform:docs/security/console-authentication.md#Console
  initialisation (final acceptance 2026-10-10)
alternatives:
  - option: Render the frame at once and fill it as answers arrive
    why_not: Early frame mounting exposes navigation before authority is coherent.
  - option: 'Several smaller start-up calls (identity, workspaces, permissions)'
    why_not: >-
      Multiple start-up documents require client reconciliation and can describe
      different snapshots.
consequences:
  - Production page mounting waits for a context answer.
  - >-
    Mounted surfaces receive a coherent held context rather than resolving
    identity individually.
  - Security can perform bookkeeping while answering the read.
  - Unknown-version rejection remains a proposed correction.
supersedes: []
evidence:
  - >-
    react-console at baf6dae: lib/security-context/{provider.tsx,boot.ts};
    components/console/console-boot-screens.tsx;
    e2e/dev/initialisation.dev.spec.ts
  - >-
    services-platform at ad3f6a6: docs/security/console-authentication.md;
    modules/security/aws/api/access.routes.ts
---
# Security Context Gates Console Mounting

## Context

Pages require a coherent answer about identity and authority before they can read data or offer navigation.

## Decision

Use the security-context gate before mounting the frame or page. A normal successful boot uses one context read; strict-entry refusal or failure can lead to fallback reads. Sign-in, setup, no-access and request failures have distinct handling.

## Alternatives Considered

Incremental frame rendering would expose partially known navigation. Separate identity and permission reads would require the client to reconcile answers.

## Consequences

Context readiness becomes a prerequisite for page mounting. The reads can produce Security bookkeeping effects. Contract-version validation remains a proposed correction.