DiiT /dit/ · DIIT-SPEC-001 REV 2026.07.08 · STATUS: LIVE

DIIT-SPEC-001 · Define It In Text

REQ-0 — THE TEST

If you can't describe what you want in plain text, you're not ready to build it.

The same test runs a city, a security program, a small business, or your own life. Get the words right first — everything you build afterward is just downstream of the sentence.

Pronounced
/dit/
Type
verb
Definition
to define it in text before you spend a dollar building it.
§1The Idea04 CLAUSES

Why the words have to come first.

Writing is thinking made visible. It's the cheapest, fastest, most honest prototype you'll ever make — and the one most people skip.

1.1

Text is the cheapest prototype.

Words cost nothing to change. Concrete costs everything. If the sentence is muddy, the thing you build from it will be muddier still.

1.2

Plain language has nowhere to hide.

A diagram can fake coherence. A dashboard can bury a missing decision. A paragraph drags the hard question out into the open where you have to answer it.

1.3

If you can't write it, you can't hand it off.

A clear paragraph is a contract a person, a team, or a machine can act on. Vagueness doesn't delegate — it multiplies as it travels.

1.4

You can't measure what you never defined.

Winning is a sentence before it is ever a number. Write down what good looks like, or you'll spend years optimizing the wrong thing beautifully.

§2Examples04 SPECS

Four things worth defining before you build them.

Each one is a full system in text — a mission, the questions you ask on a cadence, what a good answer looks like, the action a bad one triggers, and the metrics, challenges, and projects that fall out.

Open full index →