DIGITAL PRODUCT LAB [ONLINE]

MZORK_LAB // v0.9.4

We build software
before it's obvious.

A small lab for prototypes, tools, and digital products that need to exist in the world before the slide deck does. Design-led. Code-first. Allergic to generic.

ACTIVE_RUNS 5
BUILD_MODE PROTOTYPE
LAB_STATUS ACTIVE
MISSION_BRIEF.txt

$ cat mission.txt

MZORK is not an agency waiting for a brief. We are a product lab — two builders who prototype software, ship what survives, and publish the rest as experiments worth stealing from.

We care about typography, independent tools, and interfaces that feel like they were discovered rather than committee-approved. If it needs a hundred meetings, it probably belongs somewhere else.

LAB_PILLARS

How we work when nobody is watching.

01

PROTOTYPE

Rough software in days, not quarters. We sketch in code — interfaces, APIs, and flows that can be touched, argued with, and thrown away without ceremony.

02

EXPERIMENT

Tools for odd problems. Typography playgrounds, typing machines, dashboards for signals nobody asked for yet. Most experiments stay small; a few become products.

03

SHIP

When something survives contact with reality, we polish and release. No pitch decks required — working software is the artifact that matters.

ACTIVE_EXPERIMENTS

Running builds, stable releases, and ideas still warm from the bench.

EXP-000 LIVE

ZURD+_IDE

MS-DOS styled IDE for the Zurd+ language — write, run, and debug fusion-syntax code in the browser with ZVM.

EXP-001 LIVE

TYPE_MACHINE

A keyboard that misbehaves on purpose. Letter swaps, idle whispers, type sounds — a sandbox for how text should feel.

EXP-007 STABLE

TEAM_MANIFEST

The humans behind the lab — designers, builders, and chronic overthinkers with blogs and Telegram channels.

EXP-014 BREWING

FONT_FORGE

Custom typefaces and glyph experiments. Letters treated as industrial objects — drawn, tested, and occasionally published.

BUILD_PIPELINE

Four commands. No ceremony.

  1. 01
    mzork scan

    Notice friction in real workflows — not roadmap theater.

  2. 02
    mzork build

    Ship an ugly version before the meeting about the pretty version.

  3. 03
    mzork stress

    Break it on bad networks, weird screens, and impatient humans.

  4. 04
    mzork decide

    Release, iterate, or archive with notes so the next experiment starts smarter.

$ where next?

No forms. No calendar links. Just software you can click.