Stella Ops Console (UI)

Verified against commit 942a18727c (2026-09-26, DOC-2 of SPRINT_20260926_001). Re-verify by reading the evidence paths listed in the Evidence section of architecture.md.

Service wiring (image, database and role, compose profile, bundle presence) is generated in the service inventory; this dossier does not restate it.

The Console is the Angular single-page application operators use to drive Stella Ops: release control, security triage, evidence and compliance, integrations, and administration. This directory is the canonical dossier for it. The former web dossier now points here; see Companion documents.

• Source: src/Web/StellaOps.Web/
• Serving: the router gateway serves the built SPA from /app/wwwroot. In the dev compose estate the console-builder init container fills the console-dist volume; in the release bundle the dist is baked into the router-gateway image (architecture.md §8).
• Authority client: stella-ops-ui (Authorization Code + PKCE, DPoP-bound tokens).
• Runtime configuration: /platform/envsettings.json, served by Platform through the gateway.

Responsibilities

• Present backend state (releases, environments, findings, evidence, policy, integrations) without deriving evidence-grade results in the browser.
• Enforce scope-gated navigation that mirrors the Authority scope catalog.
• Run from one build in any deployment: all endpoints come from runtime configuration.
• Keep offline and air-gapped operation explicit (snapshot identity and staleness shown, never implied).

Key components

• Angular 21 workspace with standalone components and Signals; no NgRx.
• core/api/ typed clients and the single path-prefix registry (core/api/api-path-prefixes.ts).
• core/auth/ OIDC/PKCE/DPoP, route access model (route-access.ts), interceptors.
• core/navigation/navigation.config.ts sidebar groups: Home, Vulnerabilities, Deployment, Proof, Operate.

Integrations and dependencies

• Router gateway: static serving and same-origin API routing.
• Authority: sign-in, scopes, tenant and identity administration.
• Platform: runtime config, localization, preferences, context.
• Other backend services through their gateway routes (Release Orchestrator, Scanner, Findings, Vulnerabilities, Policy, Evidence Locker, OfflineKit, Integrations, Notify, Graph, AdvisoryAI, Attestor, Signer and others), each named by a key in the prefix registry.

Companion documents

• Architecture — canonical architecture (verified).
• Console feature contracts — per-surface contracts. Kept in docs/modules/web/ because Console source comments cite its section numbers.
• UX rules (binding) — UXR catalog, kept in docs/modules/web/ because the guard spec and src/Web/AGENTS.md cite that path.
• Information architecture — navigation, personas, action boundaries.

Related resources

Reference and operations

• Accessibility
• API client strategy
• Offline implementation
• Auth smoke tests
• Observability runbook and observability guide
• Setup wizard guide
• Compare workflow guide
• Smart-Diff UI architecture
• AI UX patterns
• Search chip context contract, search self-serve contract, zero-learning search entry
• Operator guide: ../../UI_GUIDE.md

Design references (not line-verified)

• EWS component docs, Provcache components
• Triage UX guide, triage reducer spec
• Lineage and Smart-Diff UI guide
• Micro-interactions map, micro-interaction theme, telemetry schema
• Proof visualization wireframes
• Persona workspace gap analysis (2026-05 point-in-time audit)
• UI v2 rewire (historical planning set)

Surface dossiers

• Assurance packs shell
• Attestor transparency controls
• Watchlist operations
• Reachability witnessing
• Platform-ops consolidation
• Offline operations
• Quota / health / AOC operations
• Execution operations
• Topology and trust administration
• Security operations leaves
• Platform-setup canonical route preservation
• Release-promotions cutover
• Evidence capsules canonical cutover
• Triage explainability workspace
• Unified audit surfaces
• Policy decisioning studio
• Workflow visualization and replay
• Contextual actions patterns

Historical planning material for this dossier (the 2026-03 component preservation map, restoration topic proposals, the orphan-revival batch, the superseded release-control IA rework, the Sprint 23 console architecture, and the 2025-12 triage design set) is frozen under docs-archive/modules/ui/ and docs-archive/modules/web/.