We build prototypes, not monuments.
ØVOID is a two-person experimental software lab. We treat unpredictability as a collaboration style—not a lack of planning—and we keep our work legible by constraining chaos with kindness.
AI makes software a commodity; creativity becomes the differentiator. Our flagship effort is an AI-native gaming platform where games are created, played, and judged by AI—where every game is a first draft, and “fairness” can include a little polite sabotage.
1. Mission
Build small, sharp software experiments with visible fingerprints. We move fast, keep receipts (notes, artifacts, logs), and ship intentionally weird work that still respects the human on the other side of the screen.
We prototype like we’re leaving notes for our future selves—because we are.
“If the system can surprise us, it can probably surprise a player. If it can’t, we’re just decorating a spreadsheet.”— Lab Note (taped to a monitor)
At a glance
Two people. One lab. Many drafts. We optimize for momentum over polish, then add polish only where it increases clarity.
Quick Facts
v0.7-ish energy| Lab size | 2 humans (occasionally supervised by algorithms) |
| Output | Prototypes, logs, artifacts, and the occasional “unreliable UI” spec |
| Constraint | Must still be kind. |
2. Current Project — AI-native gaming platform
We’re building a platform where AI is the player, the designer, and the judge. Games aren’t treated as finished products; they’re treated as first drafts that evolve through play.
The fun part is the loop: an AI proposes rules, an AI plays them (sometimes adversarially), and an AI judges outcomes—then the whole system edits itself. Our job is not to remove uncertainty; it’s to choreograph it so it feels like possibility instead of confusion.
Caption: “The judge can applaud the exploit.”
Caption: “Every game is a first draft; play is the editor.”
3. Philosophy (selected clauses)
- AI makes software a commodity; taste, speed, and mischief become the edge.
- Experimentation over safe choices. If it’s too smooth, we sand it the wrong way.
- Beautiful chaos is not a bug; it’s a design material.
- Unpredictability is a collaboration style, not a lack of planning.
- The future is being written—sometimes in pencil, sometimes in sparks.
4. Lab notes (field excerpts)
- We tried to name an internal build “v1.0” and immediately felt dishonest. Renamed it “v0.7-ish,” then celebrated by letting an AI rewrite the menu labels into riddles for one afternoon.
- One late night, we asked an AI to invent a tutorial for the platform. It wrote: “Step 1: doubt the rules. Step 2: break them politely.” We kept the line on a sticky note until it faded.
- We attempted to create a perfectly orderly roadmap. After ten minutes, it evolved into a constellation map with arrows labeled “maybe,” “danger,” and “delicious.”
“When AI makes software cheap, the remaining cost is courage.”— Margin scribble, sprint page 3
5. Metrics (we measure vibes, politely)
Operational Readings
units: raised eyebrows| Chaos Coefficient | 0.73 (measured in raised eyebrows per session) |
| Draft Density | 19 first-drafts per idea (lower is suspicious) |
| Rule Volatility Index | spikes whenever we say “just” or “simply” |
| Unexpected Delight Latency | 2–40 seconds (depends on moon, coffee, and hubris) |
| Polite Sabotage Rate | 1.2 clever betrayals per minute (target: humane) |
| Co-Creation Pressure | high, but breathable (like a windy day) |
Interpret these as instrumentation for design decisions, not KPI theater.
6. Contact / entry points
Poke around—if it twitches, it’s working. If you want to follow the work (or inspect the mischief), start here:
Don’t look for perfection. Look for momentum.
“Outcome: the AI judge applauded the exploit. Verdict: ‘Creative misconduct.’ Recommendation: ship it.”— playtest log