Proof Pages · All families

Portfolio

The work, in production

Data maps, the screens I shipped, and the tests behind them. No mockups staged for a portfolio, just what each build actually put into production.

A developer at a desk at night facing a monitor of code lit blue

Shipped UI

Devon × Tilt

The ops dashboard, running the floor.

Hands at a keyboard beside a large printed system architecture diagram under a monitor glow

Data Map

Devon × Ledger

Five sources to one typed sync.

Tilt Dispatch operations dashboard with on-the-road, needs-attention and on-time counts above an attention queue and an exceptions chart

Shipped UI

Devon × Tilt

The realtime ops dashboard.

A tablet showing a branching pipeline diagram in blue and green

Data Map

Devon × Tilt

Five tools to one source.

A printed code listing with coloured tabs under the blue glow of a monitor

Backend

Devon × Ledger

The rebuilt realtime sync.

A tabbed stack of annotated specification pages under a blue desk light

Research

Devon × Meridian

Chat logs tagged by decision.

Dual monitors of logs and charts on a desk lit blue, with a notebook and mug beside them

Internal Tool

Devon × Pulse

A safe, audited admin.

A developer working at night on a laptop showing a dark operations dashboard

Setup

Devon Park

Where the work ships from.

How To Read This Page

Every image is real, shipped work

Shipped, Not Staged

Screens and maps come from production builds, captioned with the client and the deliverable they came from.

Labeled By Role

Each artifact carries its role: research, data map, shipped UI, backend, or internal tool.

Claims Stay Home

A portfolio shows work, not results. Operational metrics live in each client's analytics, next to what was and was not measured.

The Stories Behind These

Every screen has a repository