How Monarch is made

Design

Paper and ink

Everything is paper; ink marks only what matters: text, outlines, the current choice. There is no colour — status is a shape and a word, and whatever thinks is made of pixels.

Motion has weight

Elements arrive and leave from a clear place, unfold and fold. No blinking, no constant glow.

Click — and interrupt it halfway

One animation owner

Any transition can be interrupted at any moment and never queues — the interface never makes you wait.

Motion is on right now. Turn on reduce motion in your system and the site will show final states straight away.

Respect for your settings

If “reduce motion” is on in your system, Monarch and this site show final states without animation.

Quality

Compiling isn’t fixing

A task is done when type checks, tests and a real scenario pass — not when the code builds.

Verify the result

In the product and in development alike: an action isn’t done until its effect is confirmed.

Truth in the copy

Every claim on this site is tied to code or a release. A test stops the site from promising “100%” or calling the installer signed while it isn’t.

Honest statuses

Beta, Preview and Alpha are marked right in the interface. Unfinished work is never passed off as finished.

Built with AI agents

Monarch is developed together with several AI agents. Each has its own role and admission under an open policy: Codex and Claude as lead developers, Grok admitted as a worker, unknown agents not admitted. Each task is bound to a code version, allowed paths and a deadline; accepting the result is never automatic.

Codexlead developer
Claudelead developer
Grokadmitted executor
Unknown agentsnot admitted

The mark

Two equal bands mirrored about the axis: a contour and glass laid over it. The mark comes together from two parts, the way Monarch brings a local model and your work into one. The primary version sits on a dark ground, the second on a light one.