Tools
● what wood fired games runs on
Tools.
I build a lot of my own tools. These are the systems my internal games projects and my AI practice run on: the engine and its editor, the state and persistence layers beneath them, the coordination tooling that directs the agents, and the telemetry that watches all of it. Some are open-source, most are proprietary, and each one exists because the leverage is in owning the layer the work runs on.
AI
AI Orchestration and Oversight.
The layer that directs the agents and keeps a record of what they do. One piece is open-source; the rest is the proprietary knowledge and research stack around it.
MECS
MECS: My ECS-based Simulation Engine.
The engine, the compile-time toolkit that makes it AI-legible, the editor, and the systems built on top.
[MECSComponent] and [MECSSystem] pair with a Roslyn incremental generator that writes the boilerplate and validates access patterns through custom diagnostics. A malformed system fails at compile time, not in production.Platform
Cloud Gaming Platform.
The containerized backend the engine runs on. All C# / .NET — low-latency services over gRPC, web-facing ones over ASP.NET Core REST, backed by PostgreSQL and Redis.
Unity
Unity.
Plugins that bring the engine and its data into the Unity client, where the rendering and authoring live. One is published on the Asset Store; the rest are in-house.
Misc
Misc.
The knowledge and fleet tooling that keeps a 45-plus-repo portfolio legible and maintained.
next
Built to run the work.
I just love building tools. The practice page shows the tools in use; the engine has its own write-up. If you would be interested to learn more, shoot me an email.
Four ways in, from a one-week audit to a full build. Pick the rung that fits where your studio is on the curve — pricing’s on the page.
/services → The practiceHow the AI actually gets used here, what the numbers say, and how the output gets verified before it ships.
/practice → The writingI document the practice as I build it — what works, what breaks, and what I’d tell your team to do differently.
/writing →