Regulatory Compliance Cockpit

Compliance teams at financial institutions miss regulatory drift because disclosure templates, fee schedules, and customer notices change silently across CMS, e-signature, and email systems. A missed obligation can become a multi-million dollar enforcement action.

A regulatory compliance intelligence cockpit prototype: live risk banner, compliance events feed, obligation graph, monitoring feed, business unit risk scores, peer enforcement intelligence, fragility signals, exam simulation, and per-event response workspace. Six views, mock-data-driven, production UX.

Regulatory drift is when a legal disclosure template, fee schedule, or customer notice gets quietly edited in ways that violate CFPB, RESPA, TILA, ECOA, or CAN-SPAM obligations. These silent changes can expose a firm to multi-million dollar enforcement actions. This prototype answers one question: how do you detect the moment a compliance obligation is no longer satisfied, surface it to the right owner, and drive resolution before a regulator does? Built as a full-product SaaS prototype with 6+ views, mock enforcement scenarios, and production-quality UX on Next.js 16.

1. 1.
   Live Risk Cockpit: Surface the highest-severity open compliance event in real time with exposure estimate, SLA breach status, assigned owner, and evidence gaps in a single command view.
2. 2.
   Obligation Traceability Graph: Trace the chain Regulation to Obligation to Asset to Owner so compliance officers see exactly why a drift event is a violation, not just that something changed.
3. 3.
   Monitoring + Response Workspace: Real-time alert feed from scanning disclosure templates across source systems (CMS, e-signature, email platforms) with per-event remediation: assign owner, attach evidence, run checklist, track resolution.
4. 4.
   Exam Simulation + Market Intel: Simulate regulator audit readiness against current documentation. Surface peer enforcement actions for the same violation type currently open internally.

• ◆
  Workflow-First UI Design: Mapped compliance officer triage flow before building views: cockpit banner, expandable events feed, breakdown deep-dive, response workspace. Context-driven drawer system keeps officers in flow without page navigation.
• ◆
  Regulatory Citation Modelling: Modelled real regulatory citations with accurate obligation structures and enforcement scenarios in mock data. Fragility signals flag obligations that have failed multiple times as structural root causes.
• ◆
  Business Unit Risk Scoring: Per-business-unit risk scorecards with delta trending and top risk driver attribution so leadership sees concentration, not just individual events.
• ◆
  AI-Era Compliance Gap: Designed around the emerging obligation to keep AI model disclosures current with model versions as lenders deploy AI-driven credit decisions and adverse action notices.

A news aggregator tells you what happened. This cockpit tells you what to do about it: which obligation is violated, which asset drifted, who owns remediation, whether evidence exists, and whether peer firms were fined for the same issue. The product is the workflow from detection to resolution, not the feed of regulatory updates.

Every compliance event traces through Regulation to Obligation to Asset to Owner. When a disclosure template in Salesforce CMS drifts from its approved version, the system shows the specific regulatory citation, the obligation text, the template diff, and the responsible owner. Compliance officers do not hunt through documents. They act on structured violations with evidence packs attached.

I designed around the compliance officer's actual triage loop, not a developer console. The drawer-based deep-dive keeps officers in context. Exam simulation and peer enforcement intel answer the question every officer asks after a violation surfaces: how bad could this get?

Full-product RegTech prototype with 6+ views, obligation traceability graph, and live deployment on Vercel. Workflow patterns informed by Kinage bank compliance work (22%→50% precision, ~$600K annual savings at a top-10 U.S. bank), this repo is a standalone prototype, not the production Kinage system.