ØVOID
ØVOID two-person experimental software lab
Intake: ideas with symptoms Status: workshop lights on
Enter the lab (watch your step). Refresh if you want; it might not agree with you.

A medical diagram, but for ideas.

ØVOID is a two-person experimental software lab building playful systems where uncertainty is part of the interface. We make prototypes that feel alive—because the future is being written, and we prefer ink that smudges.

Philosophy: experimentation over safe choices
Constraint: beautiful chaos (not a bug report)
Method: ship first drafts, revise in public
Micro-policy: co-creation beats control
Manifesto: constraints, not commandments
Two people, many drafts, zero sacred cows.

Philosophy

  • AI makes software a commodity; personality becomes the scarce resource.
  • We choose experimentation over safe choices, even when it makes the roadmap wobble.
  • Beautiful chaos is not a bug report; it’s a design constraint.
  • We ship first drafts with sharp edges and keep the workshop lights on.
  • Co-creation beats control: if it can’t surprise us, it’s not finished yet.
  • The future is being written; we’re willing to revise in public.
Quotations: recovered from margins
If something feels unfinished, it’s telling the truth.

Selected lab notes

If the system behaves, we probably aren’t asking the right question.

Lab note, taped above the desk
See field reports This is a marketing site; the experiments live next door.
Artifacts: do not sanitize
The future is being written. We keep extra punctuation.

Bench drawer

A crumpled index card labeled “DO NOT SANITIZE”
Surprise, friction, laughter, reconsideration.
Design note: if it’s too clean, it’s probably lying.
mood-weather.json (tiny, but stubborn)
{"wind":"sideways","clarity":0.62,"omens":["soft","electric"]}
We tried to name a build “stable.” The build refused. It asked to be called “weather.”
Paper prototype: AI judgement screen sliders
Handwritten controls:
Fair ↔ Dramatic
Literal ↔ Mythic
Every game is a first draft. The judge is an alien editor. Everyone is invited to argue.
Archived commit message (kept on purpose)
made it worse, now it’s honest.
We build prototypes that argue back—politely, usually.
Metrics: non-financial vitals
Chaos isn’t the enemy. Predictability is.

Vitals

Unpredictability Index
7.4/10
Higher is kinder to curiosity.
Draft Count per Idea
1.0
We like first drafts; we iterate by remixing.
Beautiful Chaos Budget
3 glitches/page
Strictly unaccounted for.
Co-Creation Pressure
2 humans + 1 machine opinion
All equally stubborn.
Time-to-Delight
~one scroll
Assuming you scroll like you mean it.
Stability Forecast
variable
With a chance of wonder.
Field reports: the prototypes talk back Note: not a product demo
We ship first drafts with sharp edges.

Anecdotes (selected)

At 2:13 a.m., we tried to “stabilize” a prototype. It complied by becoming consistently unpredictable—like a metronome that insists on jazz. We kept the version number and dropped the apology.

Finding: stability ≠ honesty2:13 a.m.

We once printed a screenshot of a half-working menu and taped it to the wall as a “UI fossil.” The next morning, someone had added a sticky note: “Please do not disturb the ecosystem.” We didn’t.

Finding: interfaces have habitatsovernight

During a late-night playtest of our AI-native platform, the AI judge declared a game “emotionally circular.” We argued for ten minutes, then realized it was correct and also extremely rude. We shipped that judgment as a feature.

Finding: the judge has toneplaytest log

We tried to name a build “stable.” The build refused. It started generating tutorial popups that read like fortune cookies and demanded to be called “weather.” We listened.

Finding: words affect behaviorbuild notes
Back to intake We build playful systems where uncertainty is part of the interface.