mochi
workflow

dust

A lightweight spec, review, and gate workflow for AI-assisted development. Small enough to stay local-first. Strict enough to make claims match reality.

spec → build → verify → done

Dust keeps work anchored to a change file, runs adversarial peer review between models, and makes verification explicit before anything gets called complete.

public name

`dust` on this site. `spec-of-dust` in the repo.

shape

Markdown specs, plain Git hooks, zero-dependency scripts, clean root.

why

To stop vague progress from sounding finished, especially when the live target never changed.

rule

If a live site update is desired, verification has to happen against the real target.

This page is the public-facing surface. The workflow itself still lives in the repo and is meant to travel between projects without bringing a toolchain with it.

528 Hz