Skip to content
MAZAYA STUDIOS

SPEC-000 · YOURS

Start a project

Six questions, one at a time. Your answers assemble into a single sentence, the spec that lands in Ben’s inbox. It’s the same first artifact every project here starts from.

What do you want built?

spec · This answer becomes the spec's scope line.

Pick the closest one. It only shapes the first line of the spec.

Advisory work

What should it do, and for whom?

spec · This sentence is the spec's first line, quoted back verbatim.

One sentence is enough. This is the only writing you have to do.

When would you like it in your hands?

lanes · Timing sets how many lanes run, and in what order.

A rough answer is fine. Dates move; the shape of the plan does not.

What budget range are you working with?

lanes · Budget sets how many lanes get opened, not how good they are.

A range is enough. It shapes the spec, not the welcome.

Who is this from?

gates · Every gate ends with a human report; this is who gets yours.

Ben replies from his own inbox. Nothing else is sent to this address.

YOUR SPEC, v0.1

land · Read it back and submit: this is the artifact that lands.

With JavaScript off your answers are sent exactly as filled in above.

What you send is used to reply to you and nothing else. No newsletter, no list, no third-party analytics on this page.

Process

What happens to this

Every submitted spec moves through the same four stages every project here runs through.

  1. spec

    Written specs before code

    No component CSS and no architectural choice without a written spec and a numbered decision entry behind it.

  2. lanes

    Autonomous Claude Code lanes

    Work runs in isolated lanes on work branches. One human reviews reports and unblocks; the lanes do the building.

  3. gates

    Automated merge gates

    A rule is only as good as the gate that enforces it. Merging is a script that refuses to run on a red gate.

  4. land

    One human reviews, then it lands

    Every lane ends in a review gate. Findings become a fix spec, not a patch applied by the reviewer.

Demo

  • [demo] spec MAZ-000 · written, approved
  • [demo] lane lane/your-idea · opened
  • [demo] gates lint ✓ types ✓ tests 42/42 ✓
  • [demo] land merged · gate green (simulated)

A simulated lane, for illustration. Real lane events, sanitized from this studio’s own repositories, publish with the first verified case study.

Would rather just write a paragraph? The plain contact form is still here.