We ship into a live demo channel. Then hunt bugs in public.
Every playable build goes to game.hipdurian.com — a public, 18+-gated demo environment. Not a private staging server. Real players play the actual builds, and the team watches the bugs come in live. The feedback loop is measured in hours, not sprints.
Hold Yer Gold went live on the public demo environment on 17 September. Within seventy-two hours, David had spotted a reel-framing edge case (the engine renders a fixed ~700×500px reel regardless of container width between 900–1400px), Feli had a fix candidate, and the team was debating which fix approach preserved the mobile experience.
Reel is rendering at ~700×500 no matter what the container is. Between 900px and 1400px it looks the same, then it snaps. Container-relative sizing hack or engine fix?
Twenty-four hours from bug spot to fix candidate is not fast in the abstract. It's fast for a slot studio, where the traditional loop is: internal QA → build server → operator UAT → operator production → player report → dev cycle → next release. That's a four-to-six week loop. Ours is a day.
The loop closes because we own the whole stack
Marketing site, game demo environment, RGS, math bench, art pipeline, audio bus. Every layer is instrumented, every layer is deployable from git, every layer has a human on it who can fix or approve within the same hour. The AI toolchain compresses the work. The stack architecture compresses the ceremony.
Down tools on HYG now. Consider it ready.
Down tools is what "release candidate" looks like when a designer says it. The math is signed off. The art is signed off. The audio is signed off. The build is live on a real URL that real people can play. And the next game in the queue starts tomorrow.
We're an AI-native studio, not an AI-authored one. Our art pipeline uses public foundation models in a proprietary orchestration. Our math pipeline uses an entirely proprietary model on our own GPUs. Every game is written, reviewed, and shipped by humans.— The whole thesis, in three sentences
The workflow isn't a slide. It's a set of decisions we've made about which parts of slot production should be automated and which parts should stay stubbornly, insistently human. So far, six weeks and eight games in, the split is holding.