The manifesto Calm isn't a vibe. It's law.
Ten rules every ReDock screen obeys, written down so you can hold us to them. They are why the app feels the way it does, and why this site reads the way it does.
- 01
One green per screen.
There is one primary action on every screen, and it is the only thing that wears the accent. Status never competes with it; selection wears a soft tint, never the signal. If two things glow, neither is the thing to do.
- 02
A site is a noun with a state.
Six words, and nothing else: Running · Starting… · Stopped · Error · Attention · Checking…. The pill never claims what the process tree cannot prove. Running blooms, Starting breathes, Stopped is hollow. You can read the dock from across the room.
- 03
Receipts, not wire.
Every change the AI makes is named like work ("Changed the button label"), never like a tool call. It states its plan first, checks each step after it lands, and leaves a receipt you can reopen days later, with Undo on it.
- 04
Plain words.
No codenames without a sentence that explains them. A linked copy of your site on another branch is a universe, not a worktree. An error is a sentence with a fix, not a code.
- 05
Nothing happens silently.
Every change to your computer (the certificate authority, .test routing, the helper for ports 80 and 443) is a numbered manifest you read before it happens. Uninstall previews exactly what it removes. Error reports are disclosed on that same manifest, with the switch named.
- 06
Local first.
Your sites, databases, files and keys stay on your own computer. The internet comes to you only when you share, and only for as long as you say. A cloud model sees what you send it; a local model sees nothing leave.
- 07
Errors carry their fix.
A known failure arrives with what happened, why it tends to happen, and what to do next. Failures never fold away. Unknown errors stay raw and honest rather than dressed up.
- 08
The floor is 8 GB.
Every feature ships for every machine we support. Capacity scales: smaller models, sequential work on a small machine, parallel on a big one. Features never disappear behind a RAM check. Refusals happen only near an empty machine, and they are calm notes.
- 09
Everything is bounded.
No process runs forever. Every spawn has a timeout and a kill; every background loop pauses when you are not looking; nothing fans out. Calm is an engineering property before it is a visual one.
- 10
Honest state beats a good story.
The release log says Fixed when there was a bug. This site says "coming" when a thing is not shipped. A numbers strip shows numbers that are true. If we cannot verify a claim, we do not make it.
See the laws in a window.
Download ReDock and check every rule against the first screen you open.
Free · macOS and Windows · your sites stay on your machine