ØVOID builds in beautiful chaos—software as a living draft.
We are ØVOID, a two-person experimental software lab. We treat software as a living draft—especially inside our current project: an AI-native gaming platform where games are created, played, and judged by AI while the future is being written.
Some pages may feel like they’re thinking out loud. They are.
Signal: AI makes software a commodity; taste, weirdness, and velocity are the edge.
Method: experimentation over safe choices—ship the question, not the answer.
Operating system: beautiful chaos is not a bug; it’s preferred. (legible, not tame.)
Mission
ØVOID is a two-person experimental software lab building in beautiful chaos. We design systems that surprise us back—then we ship the surprise as a draft with better lighting.
We keep a tiny bell on the desk. When an experiment behaves exactly as expected, we ring it sadly and start over.
If the prototype feels finished, it’s probably hiding the interesting part.
Philosophy (beautiful chaos, made legible)
- Experimentation over safe choices — ship the question, not the answer. (Prefer a sharp maybe over a dull yes.)
- Beautiful chaos is not a bug; it’s our preferred operating system.
- Co-creation beats control: we build systems that surprise us back.
- Every release is a first draft with better lighting.
- The future is being written—sometimes in pencil, sometimes in glitter.
With two people, we optimize for clarity of intent and fast iteration—not committees. Small surface area, high weirdness density.
We build prototypes that don’t sit still. If it looks finished, it’s probably bait.
Current project: AI-native gaming platform
A platform where games are created, played, and judged by AI. Not as a gimmick—more like a new medium: rules and taste evolve in public.
When AI can generate infinite content, the differentiator becomes selection: what gets rewarded, what gets remixed, what gets a rematch with different physics.
ØVOID’s platform: where games are first drafts on purpose.
The loop: Create → Play → Judge
Prompting, tools, and constraints produce a game draft. The goal isn’t perfection— it’s to generate interesting failure modes you can iterate on.
AI plays. It explores edge cases like it’s bored on purpose. The fun is watching what the system decides to take seriously.
AI judges. Sometimes it invents categories. We don’t always remove them. We sometimes build a graph.
The output becomes input. The judge influences what gets created next. The platform is the feedback loop—not the final artifact.
The AI played the game, judged the game, and then asked for a rematch with different physics.
Artifacts (evidence of the draft)
- A torn sticky note labeled: “Make chaos legible (not tame).”
- A “Do Not Optimize Yet” card, laminated and ignored at least twice.
- A paperclip holding two contradictory diagrams, both marked “probably true.”
- A commit message excerpt: “teach the system to misbehave politely.”
- A tiny changelog entry: “Reduced certainty by 12%. Increased curiosity by 1 unit.”
- A short list titled “Things we refuse to pretend are stable.” (It contains one item: everything.)
image://neon-lab-notes-on-black-velvet · image://chaos-loop-diagram-create-play-judge-glitch-ink · image://pixel-confetti-over-terminal-text
Metrics (we measure the weirdness so it can’t lie)
We once tried to name a feature “Stability.” It immediately caused three unrelated systems to become extremely philosophical, so we renamed it “Wobble Mode” and everything calmed down.
Number of times we said “this is fine” while rewriting it: 2 (today).