Joey Gartin

I design and build the parts of AI systems that have to be trusted: the control flow, the approval gates, the state model, the audit trail. My work tends to live where an autonomous process meets a real account, a real ledger, or a real customer record. That is the place where “mostly works” isn’t good enough.

I work with a small number of partners. They own sales and front-line support for their customers; I own the engineering. I build the product, ship the features, fix the bugs, and keep it running. The split is deliberate: it lets me stay close to a few systems instead of spread thin across many. I care about boring reliability, legible architecture, and systems whose behavior you can explain after the fact.

How I work

I keep business logic framework-free and push vendors behind seams I control, so the interesting decisions stay in one place and the replaceable ones stay replaceable. I write things down (design notes, decision records, evals) because the trail is often as valuable as the system. I prefer fewer moving parts, and I’ll argue for deleting a feature before adding one.

Partnerships

A partnership means I build and operate the system: orchestration cores, human-in-the-loop workflows, evaluation harnesses, and the data plumbing underneath. You bring the market and own the customer relationship; I stand behind the engineering for the long run. If that’s the shape of what you’re building, I’d like to hear about it.