Skip to content
Back to Projects
InternalPrivate implementation details removed.

Policy Anomaly Detection Workflow

A workflow-oriented system for surfacing policy anomalies, tracking remediation states, and making operational actions clearer.

Role: Software EngineerDuration: 2025
ReactTypeScriptWorkflow DesignState Machines

Context

Enterprise systems need to identify unusual policy states and guide teams through investigation and remediation.

Problem

Policy issues existed as disconnected manual checks rather than trackable workflow states.

Ownership

  • Anomaly list and severity/status UI
  • Remediation workflow with state transitions
  • Async state feedback patterns
  • Audit history integration

Architecture

Anomalies flow through Detected → Investigating → RemediationQueued → Remediated/Failed → Closed states with UI feedback at each transition.

stateDiagram-v2
  [*] --> Detected
  Detected --> Investigating
  Investigating --> RemediationQueued
  RemediationQueued --> Remediated
  RemediationQueued --> Failed
  Failed --> Investigating
  Remediated --> Closed

Key Technical Decisions

DecisionWhyTrade-offResult
State-based remediation modelConvert manual checks into trackable workflowRequires backend state alignmentImproved operational clarity
Severity labels with color systemOperators need quick triage signalsAccessibility requires careful contrastFaster prioritization of anomalies
Retry with idempotency awarenessAsync remediation can fail and need retryMore complex error handlingSafer operational recovery

Implementation

  • Built anomaly list with filterable severity and status
  • Created state transition UI with loading and failure feedback
  • Integrated audit trail for remediation history
  • Designed retry patterns with clear user messaging

Results

  • Improved operational clarity through state-based remediation
  • Converted policy issues from manual checks to trackable workflows

Reflection

  • Event-driven thinking changed how I designed the UI — states came first.
  • Async UI feedback is as important as the workflow logic itself.