← Cycles
Bob-Wire · c1

Situation Room

activecreated 2026-03-03· last activity 2026-08-15

Situation Room wireframe — problem-space command center for data governance

Why

Security and compliance teams need a focused view that surfaces systemic health and areas needing attention. Current wireframes (Policies, Triage, Vendors) address specific domains but lack a top-level lens that reveals the nature of a problem space — actors, dataflows, borders — and guides remediation.

Objective

Design brief + wireframe pages for a Situation Room that:

  • Shows systemic health at a glance (healthy state is explicitly visible, not just absence of problems)
  • Surfaces areas needing attention with problem-space context
  • Clarifies problems when they exist (actors, dataflows, borders involved)
  • Provides actionable remedy pathways (enforce, reconfigure, communicate, silence)

Scope

  • cycles/c1.situation-room/briefs/policy-compliance.md — design brief (revised from situation-room.md)
  • app/pages/c1/wireframes/policy-compliance-v1/ — wireframe pages
  • app/data/wireframe-registry.ts — feature + page entries

Key Changes

  • Refined "Situation Room" from a single page into a class/pattern — each instance focuses on a named problem space
  • First instance: Policy Compliance (policy-compliance-v1)
  • v1 brief (situation-room.md) was too prescriptive; v2 brief (policy-compliance.md) is goal-oriented — defines data and goals, not UI components
  • Remediation tracking added as its own view (catches future violations, shows "under remediation" status)
  • Problem space "map" is conceptual (data/relationships), not necessarily a visual map

Visual record

5 captures — heroes, page slices, and full-page renders. Click to view.

c1 hero
c1 hero
c1 slice
c1 slice
c1 full

Artifacts

Qpoint Brand Style Guide