DESIGN RULES / 04

Principles over
ornament.

A small set of constraints that guide what gets built, what gets simplified and what should be removed.

01

Prefer deletion over addition

Every feature creates a maintenance obligation. Remove unnecessary steps before introducing another layer.

02

Build for the moment you are not there

A tool should remain understandable and dependable without someone watching every operation.

03

If it needs constant attention, it is already broken

Automation should remove recurring work, not relocate it into a new dashboard or babysitting routine.

04

Tools should feel inevitable

The best interface makes the right action obvious and keeps the number of decisions low.

05

Interfaces exist to hide complexity, not expose it

Expose the information people need; keep incidental machinery out of the way.

06

Trust is a system property

Trust is earned through verifiable behavior, predictable failure handling and honest output.

07

Complexity is debt with interest

Every abstraction, dependency and special case has a future cost. Spend that complexity deliberately.

THE STANDARD

“If it needs constant attention, it is already broken.”Automation should remove work, not hide it.