BRICK & BRASS · MILL No. 6 · STEAM & SILENCE

enjoy-the-silence

It stands itself up on a machine that isn't yours: a rented VPS, a spare box, a throwaway container. Your laptop is only a window. State the work in one sentence, then watch the floor live or walk away. The run is the same either way.

Inside that box the crew runs at full power because the machine is built to be thrown away: work order → plan → red-teams → build → review → visual approval → delivery → run report.

CI status Coverage Tests Complexity Lint

⚙Watch it work

Three short clips, filmed against the real control room with mocked model calls (no tokens spent). Station behaviour mirrors real factory runs. CI re-records them on every relevant push — the latest filming is always in the Record demos workflow artifacts.

1 · Create a feature from one sentence

The owner states the work; a planner drafts the plan, two red-teams attack it, a builder implements it in an isolated worktree, two reviewers check the diff, and it lands.

2 · Model presets: who builds, who checks

Settings groups models into unlimited presets. With muse and agy installed, the factory suggests cross-family presets — Gemini writes the code, Muse checks it. Each group has switch rules: quota, failure rate, or provider errors.

3 · Quota failover: swap the whole preset

The builder's preset runs on the Antigravity subscription, whose quota is exhausted (429). The factory marks that provider spent, swaps the entire active preset to the muse preset, and the feature lands.

Full walkthrough

The longer tour of the control room: floor, work orders, station detail, governance stop-points, run report.

⚙How a feature flows

1 · State itOne sentence in the dashboard (or CLI). Triage estimates size and risk and picks the lane.
2 · Plan + red-teamsA planner drafts intent, approach and success criteria; two independent red-teams attack it. Minor points are deferred to a later related task instead of bouncing the plan.
3 · Build in isolationThe builder works in its own worktree — never in your checkout — under the preset you made active.
4 · Review + verifyTwo reviewers (subject-matter + coder) judge the diff against your patterns; the project's own verify command must pass.
5 · Visual approvalPages that changed are screenshot-diffed against the base commit; you approve or request changes from Before/After/Diff before anything lands.
6 · Land + retroThe branch merges, and a retrospective files what it learned as candidate tasks for you to accept or drop.

⚙Ways to run it — pick where the mill stands

The wizard only ever generates configuration; applying it and logging in stay yours. You don't need to own hardware.

A · Silent PC: a rented box on Hetzner (recommended)

Spin up a 32 GB RAM VPS (e.g. a Hetzner Cloud or dedicated AX box), point the wizard at the cloud target, and the factory lives there — your laptop stays off and silent while the work is done. 32 GB comfortably funds a dozen parallel tasks plus the OS reserve; reach the control room over your VPN/tailnet or an SSH tunnel, and turn the login key (model auth) once, by hand.

bun run wizard -- --target cloud --out ./my-env   # generates OpenTofu + factory config, never applies
# apply on the box, start the dashboard, state tasks from anywhere

B · A spare box at home

An old mini-PC or retired laptop on your LAN becomes the mill floor. Run the wizard on that machine so it can tailor the config to the box itself.

bun run wizard -- --target clean --out ./my-env

C · Throwaway evaluation on your current machine

An Incus container you can delete afterwards — the honest way to watch a full unattended run before committing to anything.

bun run wizard -- --target incus --out ./my-env
bun run demo        # offline rehearsal of the whole pipeline, planted fault included

D · You already run NixOS

Take the factory as a module into your existing configuration; rollback is your previous NixOS generation.

bun run wizard -- --target existing --out ./my-env

⚙Why a factory instead of just a coding agent

⚙Start yours

git clone https://github.com/Dmytroportianka/enjoy-the-silence
cd enjoy-the-silence
bun install
bun run wizard -- --target incus --brain muse --out ./my-env
bun run dashboard   # control room

Or paste the prompt in START_WITH_MUSE.md into a Muse session opened in the repo and let it commission the factory — it stops at every step that must stay human.