Anecdote
A-02A late-night build spawned a game whose only mechanic was “apologize to the scoreboard.” The AI judged every apology as “insufficiently sincere.”
ØVOID is a two-person experimental software lab building prototypes where unpredictability isn’t a bug—it’s the point. We don’t polish the future; we provoke it.
This is a marketing site. The experiments live elsewhere. If something feels unfinished, that’s the point—keep looking.
Mission, tone, and the one rule we keep breaking on purpose: control.
Games are created, played, and judged by AI. Weirdly rigorous. Surprisingly funny.
Experimentation over safe choices. Beautiful chaos as a design material.
Crumpled rules. Glitchy screenshots. A checklist that judges you back.
We build in public spirit—follow along on GitHub.
We are ØVOID, a two-person experimental software lab that treats software like weather: shaped by AI, full of surprise, rarely polite.
Our job isn’t to out-scale commodity software. It’s to spend our time on the parts that still feel strange: the edges where systems talk back, mutate, and teach us what we actually built.
Co-creation beats control. If a system can’t surprise us, we don’t trust it yet.
Translation: we prototype quickly, keep feedback loops short, and treat “unexpected output” as a material. We iterate until the behavior becomes legible—not tame.
beautiful-chaos-typography-collage,
two-desks-one-lamp
We’re building an AI-native gaming platform where games are created, played, and judged by AI. Not as a gimmick—more like an engine for strange, repeatable surprises.
Think: a loop that treats games as living drafts. The judge isn’t just a scorekeeper—it’s a collaborator that mutates the rules, finds edge cases, and turns “almost fun” into “why is this brilliant?”
We care about two things at once: (1) judgment that is consistent enough to learn from, and (2) misbehavior that’s beautiful enough to keep. The platform is a place for both.
AI makes software a commodity; we spend our time on the parts that still feel strange.
We choose experimentation over safe choices, even when the safe choice is wearing a nice sweater.
Beautiful chaos is a design material: stir, listen, iterate, don’t over-explain.
Co-creation beats control. If a system can’t surprise us, we don’t trust it yet.
The future is being written—sometimes in pencil, sometimes in fireworks.
Added chaos. Removed excuses. Kept the weird little sparkle that makes it feel alive.
A late-night build spawned a game whose only mechanic was “apologize to the scoreboard.” The AI judged every apology as “insufficiently sincere.”
Screenshot label from an old prototype folder: menu-final-FINAL-v3-actuallyfinal-chaos.png
Average time from idea to prototype: one strong coffee + one questionable decision.
20 minutes to make a feature delightful, or we delete it with ceremony and a sigh of relief. Number of features politely deleted this week: 5 (with gratitude).
These notes are intentionally “half-finished.” We keep the texture visible because it’s diagnostic: it shows where the system is still thinking, and where we’re still listening.
This site is the door sign. The lab is louder. Follow along here: GitHub.
We build prototypes where the system can surprise us—then we do the responsible thing: we write it down, and we iterate.