Haunted Game Studio is where the work ships. MACK is the control plane I'm building to make a growing team of specialist agents repeatable, reviewable, and safe to direct.
The headliners
Haunted Game Studio
I use a working game studio as the proving ground for agentic delivery: design, engineering, builds, testing, launch operations, audio, art, and the systems connecting them.
Shipped
Mushrooms vs Skulls is live on Android.
Released under Haunted Game Studio, with iOS work still ahead. A product people can install is a stronger claim than a polished agent demo.
MACK / in development
MACK is the studio control plane I'm designing: one place to direct specialist agents, expose the state of a game, enforce handoffs, and keep the human Director in control.
This is the system being built, not a fake operations dashboard. The studio's current agents and tools exist; MACK is the layer intended to coordinate them.
Operating practice
Agents work concurrently in separate worktrees. Their branches return one at a time for deliberate review and merge.
Credentials, production accounts, live domains, and real spend stop with me. That boundary is part of the architecture.
A passing-looking result is not enough. I read the diff, run the checks, inspect the output, and keep failed gates visible.
Pressure test
A game built against 356 frozen design contracts. When a value was missing, the agents had to expose the gap instead of filling it with something plausible. Twenty-six sprints, a Windows build, an Android APK, and two registers of what the contracts got wrong.
Inspect the engineering record1,569 tests
CI runs the same suite on Linux, Windows, and macOS. It is a baseline for the next build, not a claim that the next build is done.
2 / 18 gates
The remaining release gates stay visible instead of being deferred out of sight to make the project look further along.
Evidence, now
These panels fetch this repository's public GitHub activity and CI runs at page-view time. They are live data, not captured screenshots.
The archive
An earlier operating-layer concept that clarified durable workflows, explicit authority, checkpoints, and provider boundaries.
Open the old workshopThe governance experiment that taught me enforcement belongs in task shape and validated state, not reassuring prompt language.
Browse the design recordThe operator behind it
My track record is walking into organizations with no durable engineering practice and installing one that lasts. Adopting agentic AI well is the same kind of organizational problem.
6 months
Ad hoc delivery to predictable Scrum
Two teams inside a 20-person cross-functional organization, moved from non-trackable work to a steady cadence.
14 / ~50
Direct reports at peak / managed overall
Across two international teams; personally hired 20+ engineers and owned the full employee lifecycle.
~$1M
Recurring annual licensing eliminated
Architected and built an enterprise HL7 integration platform that replaced CorePoint across all clients.
Senior Development Manager / Dental Intelligence
2024 - 2026Software Engineer II / Melaleuca
2023 - 2024Software Development Manager / Martin Garage Door
2022 - 2023Software Development Manager / ChartLogic / Medsphere
2015 - 2022Senior Software Engineer / Echopass / Genesys
2014 - 2015What comes next