Intellidex · INTELLIGENCE PLATFORM · 2026

Missing persons intelligence & cold case investigative platform.

Unifying ten fragmented product squads around accessible foundations—and redesigning high-stakes compensation workflows for the people who rely on them.

Role

Lead Product Designer

& Systems Architect

Focus Domain

High-Density

Investigative Systems, Data Visualization, Case Review

Technologies

Figma, TypeScript, Tailwind CSS, IndexedDB, Playwright API

The Core Problem

Why cold cases stall:Where tools fall short

Traditional police software and basic spreadsheets make long-term missing persons work harder than it needs to. Investigators usually hit walls across four major areas:

01

Loose Timelines

Every investigation depends on locking down the exact time someone was last seen. But standard calendar tools treat all dates and times equally, making it hard to visually pin down confirmed facts against unverified rumors.

02

Impossible Sightings

Witness tips often put someone in two different cities within a two-hour window. Right now, those red flags stay buried in messy text notes instead of getting flagged automatically.

03

Privacy and Cloud Blocks

Sensitive files like unsealed records, dental charts, and family interviews can't just be tossed into standard cloud software without breaking strict privacy rules and chain-of-custody.

04

Manual Evidence Tracking

Cross-checking a random tip against old agency logs forces investigators to manually dig through hundreds of unorganized document scans, burning valuable time and energy.

Intellidex was built to fix this gap by combining private, local storage with clean layouts and smart tools, helping detectives and advocates cut through decades of noise.

Cold case files don't go quiet because people stop caring; they go quiet under the weight of fragmented evidence.

PRODUCT ARCHITECTURE & SYSTEMS STRATEGY

Designing the Investigative Engine from the Ground Up.

Standard law enforcement software works like a digital filing cabinet. It stores records for compliance, but it doesn't match how investigators actually piece things together. Finding connections across decades of files usually defaults back to physical paper, highlighters, and memory.

​

I designed Intellidex around how detectives actually think. Instead of treating records as static text fields, the system turns raw case notes into an interactive web where every insight links directly back to its original source.

Raw & Fragmented Inputs

  • Decades-old paper police logs and scanned intake forms
  • Unindexed community tip-line call sheets
  • NamUs records, physical trait markers, and dental data

Intellidex Core Mechanics

  • Two-way visual links connecting claims to original scans
  • Multi-track witness timelines that automatically catch schedule conflicts
  • NamUs records, physical trait markers, and dental data

High-Confidence Ground Truth

  • Timelines anchored by verified last-seen windows and search zones
  • Auto-flagged contradictions in witness statements
  • Source-traceable, audit-ready case files

Key Features & Design Decisions

Investigative friction in cold without missing persons inquiries.

Interviews and observational audits of cold case investigators and missing persons case auditors revealed four acute operational bottlenecks:

LKS DISORIENTATION

Over decades, the verified Last Known Seen timestamp becomes buried among hundreds of subsequent unverified sightings.

TIP-LINE SATURATION

High volumes of contradictory public sightings obscure the genuine departure window of the missing individual.

GEO-SPATIAL ISOLATION

Sighting addresses, transit corridors, and search grids exist in separate maps away from the written testimony.

UNVERIFIED EXTRACTIONS

Analysts distrust AI extraction summaries unless they can point directly to the physical line on the scanned agency filing.

Workspace Hub & Multi-Case Synthesis

Design Rationale

Investigative teams usually juggle multiple cases at once, and evidence rarely comes in neatly. Traditional folder structures make it hard to see what's actually moving forward, forcing analysts to manually click around just to figure out which cases have stalled or received fresh leads. The Workspace Hub acts like an operational radar, giving investigators a quick overview of case momentum and local vault status before they dive into an individual file.

Interaction Model

Cases are organized into simple triage states like Active, Review, and Cold using compact status cards. Investigators can instantly gauge progress through entity counts, file volumes, and recent updates. Top-level actions provide quick pathways to set up new dossiers or load local archives, while the persistent vault monitor ensures everything stays securely stored offline.

Real-Time Ingestion: Live Missing Alerts & Triage Feed

Design Rationale

When someone disappears, the first 72 hours determine whether critical leads are captured or lost forever. Investigators and search advocates usually have to monitor disconnected public bulletins, feeds, and regional agency alerts across multiple browser tabs. This fragmentation slows down early intake and creates friction when setting up a new file. I designed the Live Alerts feed as a centralized intelligence intake channel that pulls in real-time broadcasts and bridges the gap between public alerts and active local casework with one-click conversion.

Interaction Model

Streamlined Triage ErgonomicsEach alert card organizes vital details for rapid scanning, including the subject name, age, status pills (like Critical Missing, Active Search, or Endangered Runaway), verification badges, jurisdiction, and official case IDs.

Zero-Friction Workspace ConversionInstead of manually copying data into a new database entry, detectives can click "Open as case" to instantly create a dedicated local dossier. The system automatically fills in subject traits, contact info, and initial notes.

​

Offline-First Resilience & Cached SyncBuilt for secure environments and spotty connectivity, the engine keeps an encrypted local cache so investigators keep full access to recent alerts and records even when operating offline.

INTERACTION ARCHITECTURE & CORE WORKSPACES

Workspace Initialization: NamUs/Doe Network Ingestion & Active Case Instantiation

Starting a missing persons investigation used to mean re-typing data across agency databases, copying incident summaries, and standardizing physical traits by hand. This manual setup delays real casework and introduces human error right at the start.

​

I designed this ingestion view to turn raw clearinghouse data (like NamUs and AMBER bulletins) into an active, structured workspace with a single click.

Live Prototype: Phase 1 Deployed ↗

Note: This is an active web build validating core data extraction, local storage, and timeline rendering.

Automated Clearinghouse Ingestion

The engine pulls structured records directly from external clearinghouses, turning messy bulletin text into clean metadata like subject demographics, last-seen coordinates, agency contacts, and status tags (e.g., Endangered Missing).

One-Click Workspace Instantiation

Clicking an alert card moves investigators from the main monitoring feed into a dedicated workspace. The system automatically sets up the left navigation hierarchy with pre-configured schemas for intake, verification queues, location mapping, and timeline analysis.

Client-Side Air-Gapping & Local Vault

Ingested records and imported evidence are saved directly to the device's local vault. Cases stay persistent across browser sessions without sending unverified notes, family contact details, or sensitive files to external cloud servers.

Workspace 01: Interactive Verification & Extraction Engine

Standard forensic reviews force analysts to juggle between low-resolution PDF scans in one window and manual data entry in another. This back-and-forth introduces transcription errors and breaks the chain of custody. To fix this, I designed a side-by-side Verification Lab that connects a structured extraction queue directly to an interactive, coordinate-mapped document viewer.

Bi-Directional Coordinate Mapping

Every extracted card stays linked to its source document. Clicking an entity highlights the exact line in the original scan, and clicking the highlighted text instantly focuses its card in the queue.

Structured Forensic Normalization & Entity Tagging

Raw text is turned into clean, structured data with tags like time and person, making messy field logs searchable while keeping their original narrative context.

Algorithmic Confidence & Fast-Key Adjudication

Each extracted lead shows a match confidence score. Detectives can quickly confirm, edit, or reject items with simple inline actions, ensuring nothing unvetted reaches the active timeline.

RAW POLICE LOG

(PAGE 14)

"...at approximately 21:15 hours, subject was observed entering a blue sedan bearing Montana plates heading westbound toward Route 2..."

[ACTIVE CANVAS SYNC]

EXTRACTION VERIFICATION QUEUE

[!] SIGHTING: 1984 Blue Sedan

Timestamp: Oct 24, 1984 · 21:15 MDT

Source: Page 14, Line 18 

Confidence: 94% · Needs Detective Review  

[Confirm Value]   [Correct]   [Reject] 

Workspace 02: Chronology & Sighting Swimlanes

Traditional timelines flatten everything into a single linear feed, treating an unconfirmed tip with the exact same weight as physical video evidence. When dozens of tips flood in, dates overlap, create visual noise, and hide the crucial window of disappearance. I designed the Chronology Engine to clear up this confusion by organizing timelines into separate visual lanes, cleaning up crowded views, and locking down verified facts.

LKS (Last Known Seen) Permanent Anchor

Establishes a locked, persistent milestone across all views for the verified date, time, and coordinates of disappearance. It acts as a clear benchmark, separating confirmed pre-disappearance movements from later tips and rumors.

Four-Tier Operational Swimlanes

Breaks down messy chronological feeds into separate, parallel tracks so investigators can spot patterns instantly:

  • Track 01: Subject Activity (Pre-Disappearance)
  • Track 02: Witness Sightings & Tip-Line Reports
  • Track 03: Persons of Interest & Associate Movements
  • Track 04: Official Law Enforcement & Search Grid Operations

Dynamic Badge Collision Resolution

When busy time segments bunch up into unreadable clusters, a smart vertical offset automatically staggers the badges based on your zoom level, keeping everything legible without cutting off details.

Spatio-Temporal Contradiction Alerts

he engine automatically checks sighting locations against realistic travel times. If conflicting reports show someone in two different counties just 45 minutes apart, it flags the contradiction so investigators can test competing theories instead of assuming it is continuous travel.

Workspace 03: Transit Corridors & Media Vault

Investigative leads are rarely just text in a spreadsheet; they are grounded in time, geography, and physical items. When location tools live separately from media files, investigators lose the context needed to check if a sighting makes sense. This workspace connects geographic analysis with a secure, local media vault so visual assets and location data stay tied directly to the main timeline.

Chrono-Spatial Mapping

Maps location markers chronologically instead of as a static scatter plot, showing potential travel paths moving outward from the Last Known Seen anchor. This helps search teams figure out realistic travel times and spot unsearched coverage gaps.

Evidentiary Coordinate Overlays

Selecting a pinned node opens a detailed sidebar showing exact coordinates, source history (like NamUs or live alerts), verification status, and a quick link right back to the main chronology.

Air-Gapped Secondary Intelligence

Provides a secure, on-device vault for extra files like surveillance stills, ATM footage, missing posters, and search logs. This keeps the chain of custody intact without uploading sensitive files to third-party cloud servers.

Contextual Media Pinning

Lets detectives attach incoming photos, links, or age-progression sketches directly to specific map locations or persons of interest, ensuring every piece of media stays tied to a verified case event.

How it was made

Systems Architecture & Technical Execution

To test complex date logic, dense layouts, and offline data storage, I moved beyond static Figma components and built Intellidex as a fully functional web app. Combining product design principles with an AI-assisted frontend workflow allowed me to turn complex investigative models into an interactive, working environment in days instead of months.

USER WORKSPACE & PRESENTATION

Missing Case Intake | Document | Extraction Lab | LKS Chronology | Person Dossier | Spatial Map

DESIGN SYSTEM & UI FOUNDATION

Semantic Design Tokens  •  High-Density Component Kits  •  Accessible Color Systems

AI EXTRACTION PIPELINE

Multimodal Document Parsing

Confidence & Provenance Anchoring

Forensic Schema Normalization

DATA & VAULT GOVERNANCE

Local-First Data Persistence

Zero-Cloud Evidentiary Privacy

Deterministic Local Cache

USABILITY INTEGRITY

Strict Audit Trail Logging

Cross-Surface State Guard

Human-in-the-Loop Review

Critical Challenges Solved

Design & System Challenge

Evidentiary Ingestion Failures (Document Rendering Crashes)

Usability & System Root Cause

Decoded archival scans and degraded PDF case files contained irregular character encodings, causing document viewports to crash during initial upload.

Product Design & AI Resolution

Engineered a robust document-parsing fallback pipeline that sanitizes legacy file structures, ensuring seamless document viewing without data corruption or loss of visual fidelity.

Product Design & AI Resolution

Architected an AI-assisted structured extraction pipeline that transforms raw unstructured page captures into normalized, schema-aligned case profiles ready for review.

Design & System Challenge

Dynamic Data Ingestion Gaps (Real-Time Feed Ingestion)

Usability & System Root Cause

Single-page clearinghouse portals (like NamUs) render data dynamically, causing standard ingestion pipelines to pull blank layouts rather than structured records.

Design & System Challenge

Evidentiary Cross-Contamination

(Ghost Bounding Boxes)

Usability & System Root Cause

Switching rapidly between case files caused coordinate highlights and document boundaries to persist across active views, projecting misleading bounding boxes over new files.

Product Design & AI Resolution

Implemented strict context isolation patterns across active document workspaces, ensuring visual coordinates reset completely between cases to preserve evidentiary integrity.

Design & System Challenge

Cognitive Timeline Occlusion (Visual Clumping)

Usability & System Root Cause

Multiple witness sightings submitted for identical timeframes stacked directly on top of each other, cluttering the timeline canvas and hiding critical evidence.

Product Design & AI Resolution

Designed a dynamic layout algorithm with adaptive vertical swimlanes that automatically offsets concurrent badge clusters based on zoom scale, keeping dense evidence legible.

UI PATTERN LIBRARY & DESIGN SPECIFICATIONS

Design Systems & Forensic Ergonomics

Reviewing decades of dense casework requires keeping focus under heavy mental loads. The design system balances information density with visual calm, using tokenized neutral surfaces for structure and reserving meaningful colors strictly for status updates.

Low-Fatigue Layered Canvas

Avoids pure stark-white backgrounds in favor of layered, low-glare stone and slate surfaces. This grounds data tables, reduces visual fatigue during long review sessions, and creates clear depth between persistent navigation and active case canvases.

Accessibility & Hit-Zone Standards:

All primary interactive controls maintain a minimum 48x48px hit area to prevent miss-clicks during rapid triage. Semantic badges and typography tokens strictly adhere to WCAG AA contrast thresholds (4.5:1 for body copy and 3:1 for non-text UI anchors), ensuring critical tags stay legible across monitors and low-light environments.

The Modern Product Design Stack

Tech & Architectural Role

Product Design & Engineering Impact

Figma

SYSTEM ARCHITECTURE & UI ATOMICS

Architected component atomics, nested auto-layout structures for high-density desktop views, interactive coordinate states, and tokenized slate/stone variables.

Claude (Anthropic)

Generative UI logic partner

Accelerated the transition from concept to code by co-authoring modular React state machines, complex extraction prompt schemas, and forensic sample fixtures.

Cursor IDE

AI-ASSISTED COMPONENT REFACTORING

Refactored multi-pane workspace layouts, prevented CSS layout reflow/thrashing, and enforced strict TypeScript interfaces across analytical models.

React 18 & Vite 

FRONTEND APPLICATION CORE

Unified client orchestrating high-density analytical views with sub-millisecond hot module replacement, strict keyed cache unmounting, and fluid 60fps canvas panning.

Tailwind CSS

SEMANTIC DESIGN TOKENS

Translated Figma variables into a tokenized CSS architecture calibrated for low visual fatigue, high-density data tables, and WCAG AA-compliant evidentiary status alerts.

IndexedDB

AIR-GAPPED CLIENT PERSISTENCE

Engineered a local-first, zero-cloud storage engine to safeguard chain of custody, enabling stream-safe binary PDF rendering with zero external leakage.

Playwright

UX WORKFLOW QA AUTOMATION

Authored end-to-end regression test suites simulating real investigator flows, verifying coordinate-sync reliability, intake edge cases, and persona switching.

NamUs / Jina Proxy

INTAKE & EXTRACTION PIPELINE

Designed a resilient three-tier ingestion pipeline integrating federal missing-person endpoints with markdown proxy fallbacks to bypass single-page application data loss.

Lucide React

TACTICAL ICONOGRAPHY SYSTEM

Curated and styled scalable vector glyphs optimized for rapid glanceability across chronological swimlanes, verification drawers, and map overlays.

Vercel

CONTINUOUS DEPLOYMENT PIPELINE

Deployed automated staging pipelines to deliver instantaneous branch previews, versioned test links, and live production application builds.

How it was made

Engineering and Prototyping Decisions

Local-First Zero-Cloud State Engi

Local-First State Architecture

Rather than relying on remote servers that violate evidentiary chain-of-custody protocols, Intellidex is architected as an air-gapped, client-side engine. Using a centralized React Context layer coupled with browser-native IndexedDB, all uploaded case PDFs, coordinate annotations, and investigator theories persist strictly on the local machine. This architectural choice lets stakeholders evaluate high-density workflows with zero network latency while demonstrating compliance with strict digital evidence custody standards.

Interactive Coordinate-Sync and Viewport Ergonomics

Bi-Directional Viewport Synchronization

To bridge the gap between static documents and structured data, the prototype synchronizes an interactive SVG coordinate overlay directly with dynamic extraction cards. Enforcing bi-directional bounding-box focus routines inside the browser allowed me to stress-test real-world investigator ergonomics: testing panning friction, scroll anchoring, and tooltip legibility across high-resolution, multi-page scanned police logs rather than idealized Figma frames.

Production-Fidelity State Simulation

Production-Fidelity State Simulation

To validate cognitive ergonomics under authentic case stress, the interface bypasses static placeholder text in favor of stateful, real-time feedback loops:

  • Cryptographic Provenance: Real-time client-side generation of SHA-256 evidence hashes, UTC capture stamps, and immutable audit logs.
  • Dynamic Density Handling: Layout algorithms that detect badge collisions and dynamically offset overlapping timestamps across dense chronology tracks.
  • Optimistic Evidentiary Triage: Interactive verification queues that instantaneously write confirmed entities to active timelines and update local storage quotas without UI freeze.

Next project

Playground: Sheldrick Wildlife

This speculative concept explores how to pair authentic conservation storytelling with an intuitive mobile booking and foster flow, turning a routine visit reservation into lifelong donor support.

Sheila Sczepanik

Senior Product Designer

Specializing in enterprise tools, multi-brand design systems, and complex data-dense workflows that scale effortlessly for engineering teams.

Sheila Sczepanik

Senior Product Designer

Specializing in enterprise tools, multi-brand design systems, and complex data-dense workflows that scale effortlessly for engineering teams.

Intellidex · INTELLIGENCE PLATFORM · 2026

Missing persons intelligence & cold case investigative platform.

Unifying ten fragmented product squads around accessible foundations—and redesigning high-stakes compensation workflows for the people who rely on them.

Role

Lead Product Designer & Systems Architect

Focus Domain

High-Density

Investigative Systems, Data Visualization, Case Review

Technologies

Figma, TypeScript, Tailwind CSS, IndexedDB, Playwright API

Intellidex

Designing for clarity in cold case research

The Core Problem

Why cold cases stall:Where tools fall short

Traditional police software and basic spreadsheets make long-term missing persons work harder than it needs to. Investigators usually hit walls across four major areas:

01

Loose Timelines

Every investigation depends on locking down the exact time someone was last seen. But standard calendar tools treat all dates and times equally, making it hard to visually pin down confirmed facts against unverified rumors.

02

Impossible Sightings

Witness tips often put someone in two different cities within a two-hour window. Right now, those red flags stay buried in messy text notes instead of getting flagged automatically.

03

Privacy and Cloud Blocks

Sensitive files like unsealed records, dental charts, and family interviews can't just be tossed into standard cloud software without breaking strict privacy rules and chain-of-custody.

04

Manual Evidence Tracking

Cross-checking a random tip against old agency logs forces investigators to manually dig through hundreds of unorganized document scans, burning valuable time and energy.

Intellidex was built to fix this gap by combining private, local storage with clean layouts and smart tools, helping detectives and advocates cut through decades of noise.

Cold case files don't go quiet because people stop caring; they go quiet under the weight of fragmented evidence.

PRODUCT ARCHITECTURE & SYSTEMS STRATEGY

Designing the Investigative Engine from the Ground Up.

Standard law enforcement software works like a digital filing cabinet. It stores records for compliance, but it doesn't match how investigators actually piece things together. Finding connections across decades of files usually defaults back to physical paper, highlighters, and memory.

​

I designed Intellidex around how detectives actually think. Instead of treating records as static text fields, the system turns raw case notes into an interactive web where every insight links directly back to its original source.

Raw & Fragmented Inputs

  • Decades-old paper police logs and scanned intake forms
  • Unindexed community tip-line call sheets
  • NamUs records, physical trait markers, and dental data

Intellidex Core Mechanics

  • Two-way visual links connecting claims to original scans
  • Multi-track witness timelines that automatically catch schedule conflicts
  • NamUs records, physical trait markers, and dental data

High-Confidence Ground Truth

  • Timelines anchored by verified last-seen windows and search zones
  • Auto-flagged contradictions in witness statements
  • Source-traceable, audit-ready case files

Key Features & Design Decisions

Investigative friction in cold without missing persons inquiries.

Interviews and observational audits of cold case investigators and missing persons case auditors revealed four acute operational bottlenecks:

LKS DISORIENTATION

Over decades, the verified Last Known Seen timestamp becomes buried among hundreds of subsequent unverified sightings.

TIP-LINE SATURATION

High volumes of contradictory public sightings obscure the genuine departure window of the missing individual.

GEO-SPATIAL ISOLATION

Sighting addresses, transit corridors, and search grids exist in separate maps away from the written testimony.

UNVERIFIED EXTRACTIONS

Analysts distrust AI extraction summaries unless they can point directly to the physical line on the scanned agency filing.

Workspace Hub & Multi-Case Synthesis

Design Rationale

Investigative teams usually juggle multiple cases at once, and evidence rarely comes in neatly. Traditional folder structures make it hard to see what's actually moving forward, forcing analysts to manually click around just to figure out which cases have stalled or received fresh leads. The Workspace Hub acts like an operational radar, giving investigators a quick overview of case momentum and local vault status before they dive into an individual file.

Interaction Model

Cases are organized into simple triage states like Active, Review, and Cold using compact status cards. Investigators can instantly gauge progress through entity counts, file volumes, and recent updates. Top-level actions provide quick pathways to set up new dossiers or load local archives, while the persistent vault monitor ensures everything stays securely stored offline.

Real-Time Ingestion: Live Missing Alerts & Triage Feed

Design Rationale

When someone disappears, the first 72 hours determine whether critical leads are captured or lost forever. Investigators and search advocates usually have to monitor disconnected public bulletins, feeds, and regional agency alerts across multiple browser tabs. This fragmentation slows down early intake and creates friction when setting up a new file. I designed the Live Alerts feed as a centralized intelligence intake channel that pulls in real-time broadcasts and bridges the gap between public alerts and active local casework with one-click conversion.

Interaction Model

Streamlined Triage ErgonomicsEach alert card organizes vital details for rapid scanning, including the subject name, age, status pills (like Critical Missing, Active Search, or Endangered Runaway), verification badges, jurisdiction, and official case IDs.

Zero-Friction Workspace ConversionInstead of manually copying data into a new database entry, detectives can click "Open as case" to instantly create a dedicated local dossier. The system automatically fills in subject traits, contact info, and initial notes.

​

Offline-First Resilience & Cached SyncBuilt for secure environments and spotty connectivity, the engine keeps an encrypted local cache so investigators keep full access to recent alerts and records even when operating offline.

INTERACTION ARCHITECTURE & CORE WORKSPACES

Workspace Initialization: NamUs/Doe Network Ingestion & Active Case Instantiation

Starting a missing persons investigation used to mean re-typing data across agency databases, copying incident summaries, and standardizing physical traits by hand. This manual setup delays real casework and introduces human error right at the start.

​

I designed this ingestion view to turn raw clearinghouse data (like NamUs and AMBER bulletins) into an active, structured workspace with a single click.

Live Prototype: Phase 1 Deployed ↗

Note: This is an active web build validating core data extraction, local storage, and timeline rendering.

Automated Clearinghouse Ingestion

The engine pulls structured records directly from external clearinghouses, turning messy bulletin text into clean metadata like subject demographics, last-seen coordinates, agency contacts, and status tags (e.g., Endangered Missing).

One-Click Workspace Instantiation

Clicking an alert card moves investigators from the main monitoring feed into a dedicated workspace. The system automatically sets up the left navigation hierarchy with pre-configured schemas for intake, verification queues, location mapping, and timeline analysis.

Client-Side Air-Gapping & Local Vault

Ingested records and imported evidence are saved directly to the device's local vault. Cases stay persistent across browser sessions without sending unverified notes, family contact details, or sensitive files to external cloud servers.

Workspace 01: Interactive Verification & Extraction Engine

Standard forensic reviews force analysts to juggle between low-resolution PDF scans in one window and manual data entry in another. This back-and-forth introduces transcription errors and breaks the chain of custody. To fix this, I designed a side-by-side Verification Lab that connects a structured extraction queue directly to an interactive, coordinate-mapped document viewer.

Bi-Directional Coordinate Mapping

Every extracted card stays linked to its source document. Clicking an entity highlights the exact line in the original scan, and clicking the highlighted text instantly focuses its card in the queue.

Structured Forensic Normalization & Entity Tagging

Raw text is turned into clean, structured data with tags like time and person, making messy field logs searchable while keeping their original narrative context.

Algorithmic Confidence & Fast-Key Adjudication

Each extracted lead shows a match confidence score. Detectives can quickly confirm, edit, or reject items with simple inline actions, ensuring nothing unvetted reaches the active timeline.

RAW POLICE LOG (PAGE 14)

"...at approximately 21:15 hours, subject was observed entering a blue sedan bearing Montana plates heading westbound toward Route 2..."

[ACTIVE CANVAS SYNC]

EXTRACTION VERIFICATION QUEUE

[!] SIGHTING: 1984 Blue Sedan

Timestamp: Oct 24, 1984 · 21:15 MDT

Source: Page 14, Line 18 

Confidence: 94% · Needs Detective Review  

[Confirm Value]   [Correct]   [Reject] 

Workspace 02: Chronology & Sighting Swimlanes

Traditional timelines flatten everything into a single linear feed, treating an unconfirmed tip with the exact same weight as physical video evidence. When dozens of tips flood in, dates overlap, create visual noise, and hide the crucial window of disappearance. I designed the Chronology Engine to clear up this confusion by organizing timelines into separate visual lanes, cleaning up crowded views, and locking down verified facts.

LKS (Last Known Seen) Permanent Anchor

Establishes a locked, persistent milestone across all views for the verified date, time, and coordinates of disappearance. It acts as a clear benchmark, separating confirmed pre-disappearance movements from later tips and rumors.

Four-Tier Operational Swimlanes

Breaks down messy chronological feeds into separate, parallel tracks so investigators can spot patterns instantly:

  • Track 01: Subject Activity (Pre-Disappearance)
  • Track 02: Witness Sightings & Tip-Line Reports
  • Track 03: Persons of Interest & Associate Movements
  • Track 04: Official Law Enforcement & Search Grid Operations

Dynamic Badge Collision Resolution

When busy time segments bunch up into unreadable clusters, a smart vertical offset automatically staggers the badges based on your zoom level, keeping everything legible without cutting off details.

Spatio-Temporal Contradiction Alerts

he engine automatically checks sighting locations against realistic travel times. If conflicting reports show someone in two different counties just 45 minutes apart, it flags the contradiction so investigators can test competing theories instead of assuming it is continuous travel.

Workspace 03: Transit Corridors & Media Vault

Investigative leads are rarely just text in a spreadsheet; they are grounded in time, geography, and physical items. When location tools live separately from media files, investigators lose the context needed to check if a sighting makes sense. This workspace connects geographic analysis with a secure, local media vault so visual assets and location data stay tied directly to the main timeline.

Chrono-Spatial Mapping

Maps location markers chronologically instead of as a static scatter plot, showing potential travel paths moving outward from the Last Known Seen anchor. This helps search teams figure out realistic travel times and spot unsearched coverage gaps.

Evidentiary Coordinate Overlays

Selecting a pinned node opens a detailed sidebar showing exact coordinates, source history (like NamUs or live alerts), verification status, and a quick link right back to the main chronology.

Air-Gapped Secondary Intelligence

Provides a secure, on-device vault for extra files like surveillance stills, ATM footage, missing posters, and search logs. This keeps the chain of custody intact without uploading sensitive files to third-party cloud servers.

Contextual Media Pinning

Lets detectives attach incoming photos, links, or age-progression sketches directly to specific map locations or persons of interest, ensuring every piece of media stays tied to a verified case event.

How it was made

Systems Architecture & Technical Execution

To test complex date logic, dense layouts, and offline data storage, I moved beyond static Figma components and built Intellidex as a fully functional web app. Combining product design principles with an AI-assisted frontend workflow allowed me to turn complex investigative models into an interactive, working environment in days instead of months.

USER WORKSPACE & PRESENTATION

Missing Case Intake | Document | Extraction Lab | LKS Chronology | Person Dossier | Spatial Map

DESIGN SYSTEM & UI FOUNDATION

Semantic Design Tokens  •  High-Density Component Kits  •  Accessible Color Systems

AI EXTRACTION PIPELINE

Multimodal Document Parsing

Confidence & Provenance Anchoring

Forensic Schema Normalization

DATA & VAULT GOVERNANCE

Local-First Data Persistence

Zero-Cloud Evidentiary Privacy

Deterministic Local Cache

USABILITY INTEGRITY

Strict Audit Trail Logging

Cross-Surface State Guard

Human-in-the-Loop Review

Critical Challenges Solved

Design & System Challenge

Usability & System Root Cause

Product Design & AI Resolution

Evidentiary Ingestion Failures

(Document Rendering Crashes)

Decoded archival scans and degraded PDF case files contained irregular character encodings, causing document viewports to crash during initial upload.

Engineered a robust document-parsing fallback pipeline that sanitizes legacy file structures, ensuring seamless document viewing without data corruption or loss of visual fidelity.

Single-page clearinghouse portals (like NamUs) render data dynamically, causing standard ingestion pipelines to pull blank layouts rather than structured records.

Architected an AI-assisted structured extraction pipeline that transforms raw unstructured page captures into normalized, schema-aligned case profiles ready for review.

Dynamic Data Ingestion Gaps

(Real-Time Feed Ingestion)

Evidentiary Cross-Contamination

(Ghost Bounding Boxes)

Switching rapidly between case files caused coordinate highlights and document boundaries to persist across active views, projecting misleading bounding boxes over new files.

Implemented strict context isolation patterns across active document workspaces, ensuring visual coordinates reset completely between cases to preserve evidentiary integrity.

Cognitive Timeline Occlusion

(Visual Clumping)

Multiple witness sightings submitted for identical timeframes stacked directly on top of each other, cluttering the timeline canvas and hiding critical evidence.

Designed a dynamic layout algorithm with adaptive vertical swimlanes that automatically offsets concurrent badge clusters based on zoom scale, keeping dense evidence legible.

UI PATTERN LIBRARY & DESIGN SPECIFICATIONS

Design Systems & Forensic Ergonomics

Reviewing decades of dense casework requires keeping focus under heavy mental loads. The design system balances information density with visual calm, using tokenized neutral surfaces for structure and reserving meaningful colors strictly for status updates.

Slate900

Global navigation, primary typography, and deep workspace chrome.

#0f172a

Slate800

Elevated headers, active list selections, and dark contrast borders.

#1E293B

Slate700

Subtle borders, secondary icons, and metadata dividers.

#334155

Amber

Unverified community leads, raw tip-line submissions, and pending intake status.

#f59e0b

Cyan

Verified subject movements and confirmed pre-disappearance timeline events.

#0284c7

Crimson

Active spatial conflicts, OCR confidence failures, and critical triage flags

#ef4444

Purple

Last Known Seen (LKS) baseline anchor and permanent benchmark milestone.

#a855f7

Low-Fatigue Layered Canvas

Avoids pure stark-white backgrounds in favor of layered, low-glare stone and slate surfaces. This grounds data tables, reduces visual fatigue during long review sessions, and creates clear depth between persistent navigation and active case canvases.

Accessibility & Hit-Zone Standards:

All primary interactive controls maintain a minimum 48x48px hit area to prevent miss-clicks during rapid triage. Semantic badges and typography tokens strictly adhere to WCAG AA contrast thresholds (4.5:1 for body copy and 3:1 for non-text UI anchors), ensuring critical tags stay legible across monitors and low-light environments.

The Modern Product Design Stack

Technology & Architectural Role

Product Design & Engineering Impact

Figma

SYSTEM ARCHITECTURE & UI ATOMICS

Architected component atomics, nested auto-layout structures for high-density desktop views, interactive coordinate states, and tokenized slate/stone variables.

Claude (Anthropic)

Generative UI logic partner

Accelerated the transition from concept to code by co-authoring modular React state machines, complex extraction prompt schemas, and forensic sample fixtures.

Cursor IDE

AI-ASSISTED COMPONENT REFACTORING

Refactored multi-pane workspace layouts, prevented CSS layout reflow/thrashing, and enforced strict TypeScript interfaces across analytical models.

React 18 & Vite 

FRONTEND APPLICATION CORE

Unified client orchestrating high-density analytical views with sub-millisecond hot module replacement, strict keyed cache unmounting, and fluid 60fps canvas panning.

Tailwind CSS

SEMANTIC DESIGN TOKENS

Translated Figma variables into a tokenized CSS architecture calibrated for low visual fatigue, high-density data tables, and WCAG AA-compliant evidentiary status alerts.

IndexedDB

AIR-GAPPED CLIENT PERSISTENCE

Engineered a local-first, zero-cloud storage engine to safeguard chain of custody, enabling stream-safe binary PDF rendering with zero external leakage.

Playwright

UX WORKFLOW QA AUTOMATION

Authored end-to-end regression test suites simulating real investigator flows, verifying coordinate-sync reliability, intake edge cases, and persona switching.

NamUs / Jina Proxy

INTAKE & EXTRACTION PIPELINE

Designed a resilient three-tier ingestion pipeline integrating federal missing-person endpoints with markdown proxy fallbacks to bypass single-page application data loss.

Lucide React

TACTICAL ICONOGRAPHY SYSTEM

Curated and styled scalable vector glyphs optimized for rapid glanceability across chronological swimlanes, verification drawers, and map overlays.

Vercel

CONTINUOUS DEPLOYMENT PIPELINE

Deployed automated staging pipelines to deliver instantaneous branch previews, versioned test links, and live production application builds.

How it was made

Engineering and Prototyping Decisions

Local-First Zero-Cloud State Engi

Local-First State Architecture

Rather than relying on remote servers that violate evidentiary chain-of-custody protocols, Intellidex is architected as an air-gapped, client-side engine. Using a centralized React Context layer coupled with browser-native IndexedDB, all uploaded case PDFs, coordinate annotations, and investigator theories persist strictly on the local machine. This architectural choice lets stakeholders evaluate high-density workflows with zero network latency while demonstrating compliance with strict digital evidence custody standards.

Interactive Coordinate-Sync and Viewport Ergonomics

Bi-Directional Viewport Synchronization

To bridge the gap between static documents and structured data, the prototype synchronizes an interactive SVG coordinate overlay directly with dynamic extraction cards. Enforcing bi-directional bounding-box focus routines inside the browser allowed me to stress-test real-world investigator ergonomics: testing panning friction, scroll anchoring, and tooltip legibility across high-resolution, multi-page scanned police logs rather than idealized Figma frames.

Production-Fidelity State Simulation

Production-Fidelity State Simulation

To validate cognitive ergonomics under authentic case stress, the interface bypasses static placeholder text in favor of stateful, real-time feedback loops:

  • Cryptographic Provenance: Real-time client-side generation of SHA-256 evidence hashes, UTC capture stamps, and immutable audit logs.
  • Dynamic Density Handling: Layout algorithms that detect badge collisions and dynamically offset overlapping timestamps across dense chronology tracks.
  • Optimistic Evidentiary Triage: Interactive verification queues that instantaneously write confirmed entities to active timelines and update local storage quotas without UI freeze.

Next project

Playground: Sheldrick Wildlife

This speculative concept explores how to pair authentic conservation storytelling with an intuitive mobile booking and foster flow, turning a routine visit reservation into lifelong donor support.

Sheila Sczepanik

Senior Product Designer

Specializing in enterprise tools, multi-brand design systems, and complex data-dense workflows that scale effortlessly for engineering teams.

Sheila Sczepanik

Senior Product Designer

Specializing in enterprise tools, multi-brand design systems, and complex data-dense workflows that scale effortlessly for engineering teams.

Intellidex · INTELLIGENCE PLATFORM · 2026

Missing persons intelligence & cold case investigative platform.

Unifying ten fragmented product squads around accessible foundations—and redesigning high-stakes compensation workflows for the people who rely on them.

Role

Lead Product Designer

& Systems Architect

Focus Domain

High-Density

Investigative Systems, Data Visualization, Case Review

Technologies

Figma, TypeScript, Tailwind CSS, IndexedDB, Playwright API

Intellidex

Designing for clarity in cold case research

The Core Problem

Why cold cases stall:Where tools fall short

Traditional police software and basic spreadsheets make long-term missing persons work harder than it needs to. Investigators usually hit walls across four major areas:

01

Loose Timelines

Every investigation depends on locking down the exact time someone was last seen. But standard calendar tools treat all dates and times equally, making it hard to visually pin down confirmed facts against unverified rumors.

02

Impossible Sightings

Witness tips often put someone in two different cities within a two-hour window. Right now, those red flags stay buried in messy text notes instead of getting flagged automatically.

03

Privacy and Cloud Blocks

Sensitive files like unsealed records, dental charts, and family interviews can't just be tossed into standard cloud software without breaking strict privacy rules and chain-of-custody.

04

Manual Evidence Tracking

Cross-checking a random tip against old agency logs forces investigators to manually dig through hundreds of unorganized document scans, burning valuable time and energy.

Intellidex was built to fix this gap by combining private, local storage with clean layouts and smart tools, helping detectives and advocates cut through decades of noise.

Cold case files don't go quiet because people stop caring; they go quiet under the weight of fragmented evidence.

PRODUCT ARCHITECTURE & SYSTEMS STRATEGY

Designing the Investigative Engine from the Ground Up.

Standard law enforcement software works like a digital filing cabinet. It stores records for compliance, but it doesn't match how investigators actually piece things together. Finding connections across decades of files usually defaults back to physical paper, highlighters, and memory.

​

I designed Intellidex around how detectives actually think. Instead of treating records as static text fields, the system turns raw case notes into an interactive web where every insight links directly back to its original source.

Raw & Fragmented Inputs

  • Decades-old paper police logs and scanned intake forms
  • Unindexed community tip-line call sheets
  • NamUs records, physical trait markers, and dental data

Intellidex Core Mechanics

  • Two-way visual links connecting claims to original scans
  • Multi-track witness timelines that automatically catch schedule conflicts
  • NamUs records, physical trait markers, and dental data

High-Confidence Ground Truth

  • Timelines anchored by verified last-seen windows and search zones
  • Auto-flagged contradictions in witness statements
  • Source-traceable, audit-ready case files

Key Features & Design Decisions

Investigative friction in cold without missing persons inquiries.

Interviews and observational audits of cold case investigators and missing persons case auditors revealed four acute operational bottlenecks:

LKS DISORIENTATION

Over decades, the verified Last Known Seen timestamp becomes buried among hundreds of subsequent unverified sightings.

TIP-LINE SATURATION

High volumes of contradictory public sightings obscure the genuine departure window of the missing individual.

GEO-SPATIAL ISOLATION

Sighting addresses, transit corridors, and search grids exist in separate maps away from the written testimony.

UNVERIFIED EXTRACTIONS

Analysts distrust AI extraction summaries unless they can point directly to the physical line on the scanned agency filing.

Workspace Hub & Multi-Case Synthesis

Design Rationale

Investigative teams usually juggle multiple cases at once, and evidence rarely comes in neatly. Traditional folder structures make it hard to see what's actually moving forward, forcing analysts to manually click around just to figure out which cases have stalled or received fresh leads. The Workspace Hub acts like an operational radar, giving investigators a quick overview of case momentum and local vault status before they dive into an individual file.

Interaction Model

Cases are organized into simple triage states like Active, Review, and Cold using compact status cards. Investigators can instantly gauge progress through entity counts, file volumes, and recent updates. Top-level actions provide quick pathways to set up new dossiers or load local archives, while the persistent vault monitor ensures everything stays securely stored offline.

Real-Time Ingestion: Live Missing Alerts & Triage Feed

Design Rationale

When someone disappears, the first 72 hours determine whether critical leads are captured or lost forever. Investigators and search advocates usually have to monitor disconnected public bulletins, feeds, and regional agency alerts across multiple browser tabs. This fragmentation slows down early intake and creates friction when setting up a new file. I designed the Live Alerts feed as a centralized intelligence intake channel that pulls in real-time broadcasts and bridges the gap between public alerts and active local casework with one-click conversion.

Interaction Model

Streamlined Triage ErgonomicsEach alert card organizes vital details for rapid scanning, including the subject name, age, status pills (like Critical Missing, Active Search, or Endangered Runaway), verification badges, jurisdiction, and official case IDs.

Zero-Friction Workspace ConversionInstead of manually copying data into a new database entry, detectives can click "Open as case" to instantly create a dedicated local dossier. The system automatically fills in subject traits, contact info, and initial notes.

​

Offline-First Resilience & Cached SyncBuilt for secure environments and spotty connectivity, the engine keeps an encrypted local cache so investigators keep full access to recent alerts and records even when operating offline.

INTERACTION ARCHITECTURE & CORE WORKSPACES

Workspace Initialization: NamUs/Doe Network Ingestion & Active Case Instantiation

Starting a missing persons investigation used to mean re-typing data across agency databases, copying incident summaries, and standardizing physical traits by hand. This manual setup delays real casework and introduces human error right at the start.

​

I designed this ingestion view to turn raw clearinghouse data (like NamUs and AMBER bulletins) into an active, structured workspace with a single click.

Live Prototype: Phase 1 Deployed ↗

Note: This is an active web build validating core data extraction, local storage, and timeline rendering.

Automated Clearinghouse Ingestion

The engine pulls structured records directly from external clearinghouses, turning messy bulletin text into clean metadata like subject demographics, last-seen coordinates, agency contacts, and status tags (e.g., Endangered Missing).

One-Click Workspace Instantiation

Clicking an alert card moves investigators from the main monitoring feed into a dedicated workspace. The system automatically sets up the left navigation hierarchy with pre-configured schemas for intake, verification queues, location mapping, and timeline analysis.

Client-Side Air-Gapping & Local Vault

Ingested records and imported evidence are saved directly to the device's local vault. Cases stay persistent across browser sessions without sending unverified notes, family contact details, or sensitive files to external cloud servers.

Workspace 01: Interactive Verification & Extraction Engine

Standard forensic reviews force analysts to juggle between low-resolution PDF scans in one window and manual data entry in another. This back-and-forth introduces transcription errors and breaks the chain of custody. To fix this, I designed a side-by-side Verification Lab that connects a structured extraction queue directly to an interactive, coordinate-mapped document viewer.

Bi-Directional Coordinate Mapping

Every extracted card stays linked to its source document. Clicking an entity highlights the exact line in the original scan, and clicking the highlighted text instantly focuses its card in the queue.

Structured Forensic Normalization & Entity Tagging

Raw text is turned into clean, structured data with tags like time and person, making messy field logs searchable while keeping their original narrative context.

Algorithmic Confidence & Fast-Key Adjudication

Each extracted lead shows a match confidence score. Detectives can quickly confirm, edit, or reject items with simple inline actions, ensuring nothing unvetted reaches the active timeline.

RAW POLICE LOG (PAGE 14)

"...at approximately 21:15 hours, subject was observed entering a blue sedan bearing Montana plates heading westbound toward Route 2..."

[ACTIVE CANVAS SYNC]

EXTRACTION VERIFICATION QUEUE

[!] SIGHTING: 1984 Blue Sedan

Timestamp: Oct 24, 1984 · 21:15 MDT

Source: Page 14, Line 18 

Confidence: 94% · Needs Detective Review  

[Confirm Value]   [Correct]   [Reject] 

Workspace 02: Chronology & Sighting Swimlanes

Traditional timelines flatten everything into a single linear feed, treating an unconfirmed tip with the exact same weight as physical video evidence. When dozens of tips flood in, dates overlap, create visual noise, and hide the crucial window of disappearance. I designed the Chronology Engine to clear up this confusion by organizing timelines into separate visual lanes, cleaning up crowded views, and locking down verified facts.

LKS (Last Known Seen) Permanent Anchor

Establishes a locked, persistent milestone across all views for the verified date, time, and coordinates of disappearance. It acts as a clear benchmark, separating confirmed pre-disappearance movements from later tips and rumors.

Four-Tier Operational Swimlanes

Breaks down messy chronological feeds into separate, parallel tracks so investigators can spot patterns instantly:

  • Track 01: Subject Activity (Pre-Disappearance)
  • Track 02: Witness Sightings & Tip-Line Reports
  • Track 03: Persons of Interest & Associate Movements
  • Track 04: Official Law Enforcement & Search Grid Operations

Dynamic Badge Collision Resolution

When busy time segments bunch up into unreadable clusters, a smart vertical offset automatically staggers the badges based on your zoom level, keeping everything legible without cutting off details.

Spatio-Temporal Contradiction Alerts

he engine automatically checks sighting locations against realistic travel times. If conflicting reports show someone in two different counties just 45 minutes apart, it flags the contradiction so investigators can test competing theories instead of assuming it is continuous travel.

Workspace 03: Transit Corridors & Media Vault

Investigative leads are rarely just text in a spreadsheet; they are grounded in time, geography, and physical items. When location tools live separately from media files, investigators lose the context needed to check if a sighting makes sense. This workspace connects geographic analysis with a secure, local media vault so visual assets and location data stay tied directly to the main timeline.

Chrono-Spatial Mapping

Maps location markers chronologically instead of as a static scatter plot, showing potential travel paths moving outward from the Last Known Seen anchor. This helps search teams figure out realistic travel times and spot unsearched coverage gaps.

Evidentiary Coordinate Overlays

Selecting a pinned node opens a detailed sidebar showing exact coordinates, source history (like NamUs or live alerts), verification status, and a quick link right back to the main chronology.

Air-Gapped Secondary Intelligence

Provides a secure, on-device vault for extra files like surveillance stills, ATM footage, missing posters, and search logs. This keeps the chain of custody intact without uploading sensitive files to third-party cloud servers.

Contextual Media Pinning

Lets detectives attach incoming photos, links, or age-progression sketches directly to specific map locations or persons of interest, ensuring every piece of media stays tied to a verified case event.

How it was made

Systems Architecture & Technical Execution

To test complex date logic, dense layouts, and offline data storage, I moved beyond static Figma components and built Intellidex as a fully functional web app. Combining product design principles with an AI-assisted frontend workflow allowed me to turn complex investigative models into an interactive, working environment in days instead of months.

USER WORKSPACE & PRESENTATION

Missing Case Intake | Document | Extraction Lab | LKS Chronology | Person Dossier | Spatial Map

DESIGN SYSTEM & UI FOUNDATION

Semantic Design Tokens  •  High-Density Component Kits  •  Accessible Color Systems

AI EXTRACTION PIPELINE

Multimodal Document Parsing

Confidence & Provenance Anchoring

Forensic Schema Normalization

DATA & VAULT GOVERNANCE

Local-First Data Persistence

Zero-Cloud Evidentiary Privacy

Deterministic Local Cache

USABILITY INTEGRITY

Strict Audit Trail Logging

Cross-Surface State Guard

Human-in-the-Loop Review

Critical Challenges Solved

Design & System Challenge

Usability & System Root Cause

Product Design & AI Resolution

Evidentiary Ingestion Failures (Document Rendering Crashes)

Decoded archival scans and degraded PDF case files contained irregular character encodings, causing document viewports to crash during initial upload.

Engineered a robust document-parsing fallback pipeline that sanitizes legacy file structures, ensuring seamless document viewing without data corruption or loss of visual fidelity.

Dynamic Data Ingestion Gaps (Real-Time Feed Ingestion)

Single-page clearinghouse portals (like NamUs) render data dynamically, causing standard ingestion pipelines to pull blank layouts rather than structured records.

Architected an AI-assisted structured extraction pipeline that transforms raw unstructured page captures into normalized, schema-aligned case profiles ready for review.

Evidentiary Cross-Contamination

(Ghost Bounding Boxes)

Switching rapidly between case files caused coordinate highlights and document boundaries to persist across active views, projecting misleading bounding boxes over new files.

Implemented strict context isolation patterns across active document workspaces, ensuring visual coordinates reset completely between cases to preserve evidentiary integrity.

Cognitive Timeline Occlusion (Visual Clumping)

Multiple witness sightings submitted for identical timeframes stacked directly on top of each other, cluttering the timeline canvas and hiding critical evidence.

Designed a dynamic layout algorithm with adaptive vertical swimlanes that automatically offsets concurrent badge clusters based on zoom scale, keeping dense evidence legible.

UI PATTERN LIBRARY & DESIGN SPECIFICATIONS

Design Systems & Forensic Ergonomics

Reviewing decades of dense casework requires keeping focus under heavy mental loads. The design system balances information density with visual calm, using tokenized neutral surfaces for structure and reserving meaningful colors strictly for status updates.

Slate900

Global navigation, primary typography, and deep workspace chrome.

#0f172a

Slate800

Elevated headers, active list selections, and dark contrast borders.

#1E293B

Slate700

Subtle borders, secondary icons, and metadata dividers.

#334155

Amber

Unverified community leads, raw tip-line submissions, and pending intake status.

#f59e0b

Cyan

Verified subject movements and confirmed pre-disappearance timeline events.

#0284c7

Crimson

Active spatial conflicts, OCR confidence failures, and critical triage flags

#ef4444

Purple

Last Known Seen (LKS) baseline anchor and permanent benchmark milestone.

#a855f7

Low-Fatigue Layered Canvas

Avoids pure stark-white backgrounds in favor of layered, low-glare stone and slate surfaces. This grounds data tables, reduces visual fatigue during long review sessions, and creates clear depth between persistent navigation and active case canvases.

Accessibility & Hit-Zone Standards:

All primary interactive controls maintain a minimum 48x48px hit area to prevent miss-clicks during rapid triage. Semantic badges and typography tokens strictly adhere to WCAG AA contrast thresholds (4.5:1 for body copy and 3:1 for non-text UI anchors), ensuring critical tags stay legible across monitors and low-light environments.

The Modern Product Design Stack

Technology & Architectural Role

Product Design & Engineering Impact

Figma

SYSTEM ARCHITECTURE & UI ATOMICS

Architected component atomics, nested auto-layout structures for high-density desktop views, interactive coordinate states, and tokenized slate/stone variables.

Claude (Anthropic)

Generative UI logic partner

Accelerated the transition from concept to code by co-authoring modular React state machines, complex extraction prompt schemas, and forensic sample fixtures.

Cursor IDE

AI-ASSISTED COMPONENT REFACTORING

Refactored multi-pane workspace layouts, prevented CSS layout reflow/thrashing, and enforced strict TypeScript interfaces across analytical models.

React 18 & Vite 

FRONTEND APPLICATION CORE

Unified client orchestrating high-density analytical views with sub-millisecond hot module replacement, strict keyed cache unmounting, and fluid 60fps canvas panning.

Tailwind CSS

SEMANTIC DESIGN TOKENS

Translated Figma variables into a tokenized CSS architecture calibrated for low visual fatigue, high-density data tables, and WCAG AA-compliant evidentiary status alerts.

IndexedDB

AIR-GAPPED CLIENT PERSISTENCE

Engineered a local-first, zero-cloud storage engine to safeguard chain of custody, enabling stream-safe binary PDF rendering with zero external leakage.

Playwright

UX WORKFLOW QA AUTOMATION

Authored end-to-end regression test suites simulating real investigator flows, verifying coordinate-sync reliability, intake edge cases, and persona switching.

NamUs / Jina Proxy

INTAKE & EXTRACTION PIPELINE

Designed a resilient three-tier ingestion pipeline integrating federal missing-person endpoints with markdown proxy fallbacks to bypass single-page application data loss.

Lucide React

TACTICAL ICONOGRAPHY SYSTEM

Curated and styled scalable vector glyphs optimized for rapid glanceability across chronological swimlanes, verification drawers, and map overlays.

Vercel

CONTINUOUS DEPLOYMENT PIPELINE

Deployed automated staging pipelines to deliver instantaneous branch previews, versioned test links, and live production application builds.

How it was made

Engineering and Prototyping Decisions

Local-First Zero-Cloud State Engi

Local-First State Architecture

Rather than relying on remote servers that violate evidentiary chain-of-custody protocols, Intellidex is architected as an air-gapped, client-side engine. Using a centralized React Context layer coupled with browser-native IndexedDB, all uploaded case PDFs, coordinate annotations, and investigator theories persist strictly on the local machine. This architectural choice lets stakeholders evaluate high-density workflows with zero network latency while demonstrating compliance with strict digital evidence custody standards.

Interactive Coordinate-Sync and Viewport Ergonomics

Bi-Directional Viewport Synchronization

To bridge the gap between static documents and structured data, the prototype synchronizes an interactive SVG coordinate overlay directly with dynamic extraction cards. Enforcing bi-directional bounding-box focus routines inside the browser allowed me to stress-test real-world investigator ergonomics: testing panning friction, scroll anchoring, and tooltip legibility across high-resolution, multi-page scanned police logs rather than idealized Figma frames.

Production-Fidelity State Simulation

Production-Fidelity State Simulation

To validate cognitive ergonomics under authentic case stress, the interface bypasses static placeholder text in favor of stateful, real-time feedback loops:

  • Cryptographic Provenance: Real-time client-side generation of SHA-256 evidence hashes, UTC capture stamps, and immutable audit logs.
  • Dynamic Density Handling: Layout algorithms that detect badge collisions and dynamically offset overlapping timestamps across dense chronology tracks.
  • Optimistic Evidentiary Triage: Interactive verification queues that instantaneously write confirmed entities to active timelines and update local storage quotas without UI freeze.

Next project

Playground: Sheldrick Wildlife

This speculative concept explores how to pair authentic conservation storytelling with an intuitive mobile booking and foster flow, turning a routine visit reservation into lifelong donor support.