Compliance analysts (primary) and compliance managers (oversight). Analysts do day-to-day case screening — reviewing OFAC candidates, scoring match candidates, recording findings, and making risk decisions. Managers review analyst decisions, audit trails, and risk labels. Both work primarily inside the 3-column case detail view. Speed, clarity, and auditability are paramount.
Precise. Accountable. Clear.
The tool sits at the intersection of legal obligation and investigative judgment. It should feel like a precision instrument — trustworthy, serious, never fussy. Approachable enough that analysts don't dread opening it; authoritative enough that compliance buyers trust it.
Utilitarian precision. Light mode as primary. Maximum information density with minimal chrome. Every pixel carries meaning; decorative elements earn their place by reinforcing data hierarchy.
Fonts already set the tone: Oxanium (geometric, slightly technical) for body/UI, JetBrains Mono for data values (scores, IDs, timestamps). Lean into this — monospace for machine-generated data, geometric sans for human-facing labels.
Risk signals must be unmistakable: HIGH = sharp red, MEDIUM = amber, LOW/NONE = muted gray-green. No ambiguity on risk level at a glance.
Anti-references: No glassmorphism, no gradient cards, no decorative shadows, no icon-above-heading template cards, no hero metric layout. Avoid anything that looks like a SaaS marketing dashboard.
References: Bloomberg Terminal (density, authority), financial reports (typographic hierarchy, monospace data), OSINT tools (structured evidence display).
- Data forward — reduce chrome to near-zero; information is the design
- Risk signals are unmistakable — color + typography reinforce severity instantly, every time
- Navigation reflects the actual workflow — Cases list → Case detail → Decisions; the shell should make this path obvious
- Density without overwhelm — pack information using typographic hierarchy, not more container nesting
- Persistent context — analyst always knows their case, their stage, and their navigation path
Current state: no persistent shell. Pages feel disconnected; no way back without browser history.
Required: A minimal persistent top nav bar with:
- Wordmark / product identity (top-left)
- "Cases" link (primary navigation destination)
- "New case" action (top-right)
- Breadcrumb trail when inside a case: Cases > [Subject Name]
The 3-column case detail workspace layout (280px left / fluid center / 320px right) is correct and should be preserved.