ØVOID
ØVOID two-person experimental software lab
software as a sandbox / not a monument

We build beautiful chaos
until the surprise feels inevitable.

ØVOID is a two-person experimental software lab that treats software like a sandbox, not a monument. We build in beautiful chaos—because AI makes software a commodity, and novelty is the only defensible edge.

Meet the current project
Poke around. If it wiggles, it’s intentional-ish.
Choose your route: read top-to-bottom like a normal site, or jump by “paths” like a book where the margins whisper back.

If AI can write the code, our job is to choose the surprises worth keeping.

Lab note, margin scribble

What we actually do

small lab / big prototypes

We prototype quickly, ship learnings faster, and keep the cursor blinking. Some drafts bite; we keep the ones with good teeth.

  • 01Rapid experiments with clear intent (even when the UI squeaks).
  • 02AI-native systems where behavior is a first-class material.
  • 03Tools and platforms designed for novelty, not sameness.

Current project: AI-native gaming platform

games made, played, and judged by AI

What “AI-native” means here

behavior is the interface

We’re building a platform where the loop isn’t just humans playing content— it’s AIs generating games, AIs playing them, and AIs judging them. The result is a living catalog of “first drafts” that argue back.

  • Create Games emerge from prompts, constraints, and evolving rulesets—less “final design,” more “replayable hypothesis.”
  • Play AI agents explore the game space, discover exploits, and surface weird edges that humans might miss.
  • Judge Scoring focuses on novelty, coherence, and “is this fun in a way we didn’t expect?”

Inspiration labels (not images): image://ai-judge-gavel-made-of-pixels, image://first-draft-game-screenshots-collage

Every game is a first draft. The fun part is watching the draft argue back.

AI-native gaming platform where games are created, played, and judged by AI playtest log

How to read our progress

prototypes > promises

We don’t claim certainty. We ship experiments and document what they teach us. If you want the most concrete trail, follow commits and notes.

Philosophy: experimentation over safe choices

“beautiful chaos” as a design principle

Manifesto (read like margin notes)

Page 1 — the premise
  • 1AI makes software a commodity; weirdness makes it memorable.
  • 2We choose experimentation over safe choices, even when it squeaks.
  • 3Beautiful chaos is not a phase—it’s a design principle.
Page 2 — how we work (and why it looks like this)
  • 4Prototypes are allowed to be loud, unfinished, and oddly charming.
  • 5If it behaves perfectly, we probably fixed the wrong thing.
  • 6The future is being written. We keep the cursor blinking.

Beautiful chaos: the moment a prototype stops obeying and starts collaborating.

Whiteboard, next to a doodled tornado

A practical promise

We won’t hide behind vagueness. Our work should be legible: what we’re exploring, what we learned, and what we’re trying next—without pretending the messy parts aren’t part of the craft.

“Safe choices are just defaults wearing nicer clothes.”

Lab notes (the margins are part of the page)

artifacts / anecdotes / metrics

Inventory: artifacts we actually trust

  • A laminated “Chaos Budget” card: 70% curiosity, 20% restraint, 10% snacks.
  • A tiny JSON file named ritual.json containing: {"breathe":2,"ship":1,"overthink":0}.
  • A desk bell labeled “Reroute the Plan.” It rings when something unexpected works.
  • A commit message fragment: “teach the system to misbehave politely.”
  • A coffee-stained map of features with a legend: “Here be delightful mistakes.”

Inspiration labels (not images): image://neon-lab-notebook-with-glitch-margins, image://chaos-spiral-diagram-on-whiteboard

Telemetry (measured in eyebrow raises)

Unpredictability Index
0.73
Prototype Half-Life
11 hours
Chaos-to-Clarity Ratio
3:2
Draft Density
9 first drafts / thought
AI Mischief Level
“cooperative troublemaker.”
Anecdotes (the kind that explain the UI without excusing it)
  • #We tested a color palette called “Slightly Haunted Neon.” It looked wrong in daylight and perfect at 2:13 AM. We kept it and named the bug “mood lighting.”
  • #A sticky note appeared on the monitor: “Stop polishing the chaos; let it glitter.” Neither of us claims authorship. We treat it as an office visitor.
  • #During a late-night build, we set a rule: every button must feel like it’s about to become a different button. The next morning, we couldn’t find the “Contact” link—turns out it had evolved into “Confess.”

Contact (we respond like humans)

Email: hello@ovoid.lab

If you’re exploring AI-native games, weird tooling, or novelty-driven systems—send a note. We’ll read it, not route it.

Note: This block has baseline styling if anything is injected here. It stays readable.