Dry-run by default: why preview beats hope

Most content systems treat “publish” as the happy path and “preview” as an optional checkbox. We inverted that.

At MeltingFace, dry-run is the default. Local site builds, social queues, and campaign calendars are designed so nothing leaves the building until a human says so. Automation isn't evil. Accountability just doesn't fit inside a single model call.

What dry-run means here

  • Website: Markdown builds into `site-out/` you can open on a local preview server. Pages can carry an explicit dry-run badge.
  • Social: Adapters format posts for X and LinkedIn and park them in a queue. They do not call live publish APIs by default.
  • Config: `DRY_RUN=true` and `PUBLISH_MODE=dry_run` stay on until the Board unlocks a channel.

If a feature cannot run usefully in dry-run, we treat that as a design smell — not a reason to skip the guardrail.

Why teams skip preview

Preview feels slow when you are behind on a calendar. The cost shows up later:

  1. Wrong claim ships because nobody re-read the final HTML.
  2. Brand drift when each tool invents its own “close enough” voice.
  3. No audit trail between “draft in chat” and “live on the wire.”

A preview-first path is slower for the first hour and faster for the next six months.

How we keep it practical

  • Brand kit is machine-readable — palette, voice, legal boilerplate, forbidden claims. Agents read; they do not invent.
  • Status vocabulary is shared — front-matter, CRM, and SSG agree on what “approved” means.
  • Diff before approve — humans can see old → new without guessing.
  • Quality gates offline — brand validate, link checks, SEO/a11y baselines, golden HTML — no production deploy required.

What we do not claim

We do not claim autonomous publishing, auto-replies to social mentions, or real-money spend by agents. Those are out of scope for the current preview stack. When the Board unlocks a live channel, it is still one channel at a time, with humans on the critical path.

Bottom line

Dry-run is not a demo mode we are ashamed of. It is the operating mode that keeps people in charge of what represents the company.

Next: Agents can't govern AI — people do · Platform overview

MeltingFace