AI Solutions Architect
Software engineer and team lead at IBM/Tivoli, Motive, Sun Microsystems, and BuildForge. Two decades running organizations with budget, staff, and executive accountability. Today I architect and deliver production AI systems — nine applications in five months, including a commercial game releasing on Steam and a real-time translation platform running two models on a single machine with no cloud at all.
This site is the long version. Everything below is running software, and every number on it came from the code.
Nine applications · ~90,000 lines of first-party code
A story-driven arcade game with 132 hand-built levels, four narrators, and an original 36-song score. Releasing on Steam September 1, 2026.
ShippingTypeScriptTauri / RustReal-time captioning and translation into ~200 languages, running entirely on one local machine. No cloud, no app, no audio leaving the building.
LivePythonCTranslate2Turns roughly ten form entries into a print-ready bulletin and an 80-slide deck. In continuous weekly production use since March 2026.
LiveReact 19FastAPIOffline-first ledger where two people on two machines converge without a server, a lock, or agreeing what time it is.
In developmentHybrid Logical Clock
A deployed inference engine that narrows ~990 entities to one in 25 questions or fewer, selecting each question by expected information gain.
LiveTypeScript
A 1992 machine simulated in a browser: BIOS, virtual filesystem, shell, a second bootable OS, and a working BASIC interpreter.
In developmentTypeScriptTauriA self-hosted replacement for a commercial speech vendor, including a multi-stage voice-training pipeline that runs as a monitored background job.
DeployedPyTorchLoRA
A desktop combat tracker shipped through 13 releases in four months, every one of them driven by a real user at a real table.
In useReact 19TauriDigital signage a volunteer can run from any browser on the network, serving images in place from wherever they already live.
In developmentFastAPIReactThe part that doesn't fit on a resume
I direct AI coding agents, and I own the architecture, the constraints, the verification, and the release gate. My engineering background is what lets me specify and review what the agents produce; the years I spent away from the keyboard running organizations are what let me give up authorship without feeling like I'd lost something. The judgment is the job. What to build, what it must satisfy, and what stops it from shipping broken.
That only works if verification is real. Every claim on this site is checkable, and most of them are checkable by a machine — because I built the machine that checks them.
FIRST LIGHT's 132 levels are each proven completable by a flood-fill algorithm that runs as a test on every edit. Most games in this genre ship unwinnable-board bugs. This one can't — the proof is a build obligation.
Two headless bots play every level 100 times to produce the difficulty curve. The game core is genuinely renderer-free, which is what makes that possible. Balance came from measurement, not from how it felt on a Tuesday.
Q&AI won't deploy below a 98% pass rate on a ~990-case regression harness. FIRST LIGHT runs two independent fail-closed checks that make shipping a debug-enabled binary structurally impossible rather than merely unlikely.
~1,700 lines · ~20 concurrent projects · evolved through a documented incident log
Running agents across twenty projects surfaced a problem the tools don't solve: instructions that live in a session don't survive the session. A core safety rule dropped out of context once during a compaction, and a faithful re-read couldn't recover it — because the rule wasn't written anywhere durable. So I built the thing that was missing.
commit ⊂ push ⊂ ship — commit freely, push on judgment, and ship only on an explicit human decision, every time. The gate is tied to irreversibility, not to command type. A prior yes never carries forward.
When I'm present: ask and wait. When I'm not: never block on a question — take the most reversible path and log loudly. The safety property you want changes with operator presence, and an agent frozen on an unanswered question is just a slower prompt.
Three consecutive near-misses taught me that when a safeguard fails you shouldn't sharpen it — you should change its kind. Vigilance becomes a fail-closed rule; a fail-closed rule becomes geometry. Nothing can stage a credential that was never in the directory.
Engineer, then executive, then both
I spent seven years as a software engineer and team lead — Tivoli Systems (IBM), where I was promoted to lead a team of eight; Interactive Intelligence, reporting to the company president; BroadJump/Motive, where I was primary architect of an automated build-verification system that was continuous integration in substance five years before the term became standard; Sun Microsystems; and BuildForge, a DevOps startup later acquired by IBM. I was also one of three founders of an early web company.
Then I left to become a pastor, and spent twenty-one years leading organizations — hiring and developing staff, owning operating budgets, directing a $500,000 capital project completed debt-free, and standing up every week to explain difficult things to people who did not come pre-equipped. I earned a doctorate in that last part.
The thread through all of it is the same one: find the work a person is doing by hand, and make it stop being necessary. That was process automation in 2001. It's AI-directed delivery now. The instrument changed; the job didn't.