About.
I build AI platforms, agent toolchains, and spatial systems — end to end. Senior Consultant at Oteemo. Currently building the AI Dev Platform, its agent fleet, and a Quest 3 client that puts it all in space.
Senior Consultant at Oteemo by day. The rest of the year is the platform, the fleet, and the headset: an AI Dev Platform built end to end — orchestration services, sandboxed execution, agent catalogs, and the observability to keep it honest — plus a spatial client on Quest 3 to see the whole system in the room with you.
The decade before was the apprenticeship: SRE and MLOps at Launch Consulting (incident recovery, cloud re-architecture, standing up MLOps for the org), platform modernization at Kalkomey, an independent consulting practice at Sphinx Code, claims and refining systems at Optum and Marathon Petroleum — including an API pass that cut call times fivefold across 17 refineries — and CI/CD and test platforms at USAA, where the functional-testing framework cut end-to-end test time by half and the MISMO standards workgroup turned into two of them. US Army veteran.
| Name | Cory Policht |
| Role | Senior Software Engineer |
| Based | San Antonio, TX |
| Now | Building the AI Dev Platform |
| [email protected] | |
| Status | Booking selectively for Q4 2026. |
TIMELINE ―――――――――
- §01Ports, not platformsChoose seams over vendors. Domain logic that compiles and tests without its engine survives migrations — Unity to CI, Ruby to React, one cloud to the next. Multi-cloud at Sphinx Code and Launch; engine-free cores at home.
- §02Fail closedOn paths that touch hardware, secrets, or production, the default is no. SRE recovery inside 24 hours at Launch, production-support ownership at Kalkomey, and gated model loads at home all start from the same place: systems that can fail must fail safely.
- §03Evidence-anchored claimsA fact without a source is a rumor. Measure it — Gatling load tests at Optum, MISMO data-model discipline at USAA, provenance fields in the spatial platform — or cite it: path, line, commit, date.
- §04Prove it mechanicallyIf a boundary matters, the build enforces it. CI/CD pipelines at USAA that halved end-to-end test time, automated functional suites everywhere since, and CI that refuses to compile an engine into the core. Humans review; machines verify.