I build LLM platforms inside regulated cloud environments, and AI workflows that business teams use on their real work. When a result misses, I trace why and say so.
Employer and client code is private, so this page describes the work and draws how it fits together. Red notes mark the limits.
Stauder Technologies, 2026
/v1/messages route. I traced that and fixed it with a pre-call hook. I also designed and directed a FastAPI bridge (AI-assisted implementation) so Codex CLI traffic goes through the same gateway.LiteLLM, Amazon Bedrock, AWS GovCloud, FastAPI, CloudWatch, Athena
Stauder Technologies, 2026
There are no formal productivity metrics yet.
Bedrock Guardrails, FedRAMP High, Codex CLI, PowerShell, workshops
MarkSet (AI workflow consultancy), October 2026
The knowledge system is designed, not built.
Claude Enterprise, Claude skills, SharePoint, Outlook
MarkSet, 2026
Two jobs is a small sample, and I treat it as one.
Personal project, October 2026 to now
It is running a paper month before any real money, so there are no returns to report.
Python, scheduled runs, simulated exchange
Personal project, June 2026 to now
Claude Code, Codex, hooks, scheduled jobs
Smaller builds and measurements. I design, direct and test these, and AI coding agents write most of the code.
Research, 2026
I measured how much of Claude Code's context its built-in tool schemas use before any work starts: about 34,800 tokens, or 17.4% of a 200,000-token window.
Context Headroom is a method I designed and published as a LinkedIn post: compact early, at around 40% of the window, into a verified ledger, instead of waiting until the window is nearly full.
I haven't collected usage data on Context Headroom yet.
Personal project, July 2026
~16 tokens/sec, measured on the phone
llama.cpp serving Gemma 4 E2B on a Galaxy S25 Ultra through Termux, with phone tools through Termux:API. The shell is allowlisted, and any action with side effects waits for me to type "yes". I ran and debugged it on the device; Claude wrote the script.
Personal project
A standard-library Python agent with grammar-constrained decoding and a git-backed knowledge tree that records where each fact came from. 16 of 16 tests pass.
So far the tests run only against a stand-in model, not a real one.
Personal project, November 2026 to now
My daily market and tech brief. It collects from a public list of sources every four hours and posts a visual page each weekday morning, plus a Saturday wrap. It informs only and never makes trade calls. To earn its keep, it has to beat a plain prompt in a blind week-long head-to-head, on at least 4 of 5 days.
It went live November 14, 2026. The head-to-head week hasn't run yet.
Personal project
Functional parts I model as code, print and measure. Fit clearances come from a printed test coupon rather than guesses, and a part counts as done only when it has been measured against what it had to do.
On the side, I'm designing a mobile factory-automation puzzle game: one fair daily puzzle for everyone, plus a base that grows between dailies. Coding agents build it from my design.
St. Peters, MO. May 2024 to present.
St. Louis, MO. April 2026 to present.
Missouri University of Science and Technology, May 2024.