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.

Clarity through text — for any project, of any size.

Anyone leading something — or trying to — should be able to describe what they want to build, or how they'd change what they're taking over. That description is your ideal state, and you can't move toward a direction you can't name. If you can't put it in words, that's the tell that you don't know it yet — you're grasping, hoping the next project or vendor shows you a glimpse of what you should have been building.

Pronounced
/dit/
Type
verb
Definition
to write your ideal state in plain text before you spend a dollar building toward it.
§1The BaselineIDEAL STATE

The text is your ideal state. The number is how much of it you've built.

Whether it's a city, a company, a security program, or your own life, the move is the same: write the whole thing down, and that description becomes the standard. You don't jump from where you are to the ideal state — you climb toward it, level by level. From then on there's one real question: what percent of it are you running, and how well?

Ideal state — defined in text100%
Implemented — by people + agents14%

The other 86% isn't drift, and it isn't a program you're still hunting for. It's named, and just not built yet — too little staff, pre-AI, the agent you can't pay for yet, the project still in the queue.

1.1

You measure against the program, not your memory of it.

You're not drifting, not searching for the program, not letting it take shape in front of you. It's fixed, in text. The live question is only how much of it runs today — by people or by agents — and how well in each area.

1.2

Every proposal gets weighed, not guessed.

A vendor pitch, a resident's idea, a competitor's move — the question stops being "does that sound good?" It becomes: does this belong in the ideal state, are we already doing it, and is it better than what we run now? You have something to measure against.

1.3

A low number is a plan, not a failure.

Running 14% of a sharp, honest ideal state beats running 100% of a vague one nobody wrote down. The gap tells you exactly what to staff, fund, or hand to an agent next.

§2The 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.

2.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.

2.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.

2.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.

2.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.

§3Examples04 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 →