Projects · lead & supporting

Three lead projects. Chosen, not listed.

The brief is "how I think," not "what I built." If a project can't carry the move paragraph, it isn't here.

01 · Lead
2026
AI-augmented operations

Same-Day Vendor Sweep

148 vendors became a segmented TheoPay rollout dataset in one workday, because the schema was written by the implementation lead, not for the implementation lead.

The move
Rows of vendor data converging through a terracotta diamond filter into segmented output groups — unsorted mass becoming a sequencing decision.
02 · Lead
2023 to 2026
Operations architecture

The Operations Backbone

SFT's state-government ESA platform runs on a Smartsheet substrate designed for 18 state customers before scale arrived.

The move
A layered schematic of the Smartsheet operations backbone: 5 workspaces, sheets, dashboards, and three-system ticket flows arranged as a substrate beneath 18 client slots, two of them activated.
03 · Lead
2024 to 2026
Capability building

User Enablement, 0 to 1

Founded SFT's User Enablement function from zero, designed to survive its author, hosted by the state on its .gov site.

The move
Platform guide catalog spanning four user audiences and two state programs, with WV State Treasurer's Office adoption marked as the external proof point.
04 · Lead
2026
AI-assisted software delivery

Sub-Creator Workbench

A 32,000+ LOC full-stack workbench, sole-authored in three months and run as a production service since June 2026, because AI-assisted delivery was directed like an implementation, not prompted like a demo.

The move
Five workspace panels arranged over a layered stack of frontend, API, search, and database strata, with a terracotta uptime line running unbroken beneath the whole schematic.
05 · Lead
2026
Document pipeline

Storekeeper

A 14,000+ LOC document-processing pipeline, sole-authored in six days at a testing discipline most month-long builds never reach: 93 commits, 42 test files.

The move
Stacks of mixed documents entering a staged sorting pipeline of parse and assembly steps, emerging as one bound output package, a terracotta test gauge marking every stage.