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.