The Judgment Style Guide
How Editors Protect Clarity (Not Just Quality)
This guide exists to give editors authority—not polishers.
Editors are not here to:
- Make content nicer
- Reduce friction
- Smooth disagreement
They are here to protect judgment.
1. The Editor’s Primary Responsibility
An editor’s job is to answer one question:
“Does this page clearly tell the reader what to believe and do?”
If the answer is no, the page does not ship—regardless of effort.
2. What Editors Must Enforce (Non-Negotiable)
Every page must contain:
✅ A Clear Assertion
- Stated early
- Directional
- Removable only at the cost of meaning
If the page opens with background, definitions, or context, send it back.
✅ Named Tradeoffs
Editors should ask:
- What does this optimize for?
- What does it sacrifice?
If tradeoffs aren’t named, judgment is missing.
✅ A Resolution
Editors should be able to underline a sentence that answers:
“So what should the reader do now?”
If resolution is implied instead of stated, it’s not sufficient.
3. Language Editors Should Challenge
Editors must flag and remove:
- “It depends…”
- “There are many ways…”
- “In some cases…”
- “It’s important to consider…”
These phrases re-open uncertainty after the page should be closing it.
4. What Editors Should Protect
Editors should defend:
- Repetition of core ideas
- Consistent phrasing across pages
- Strong declarative statements
Internal boredom is not a valid reason to change language.
5. The Editor’s Kill Authority
Editors are explicitly empowered to:
- Block publication
- Request rewrites
- Recommend removal of ranking pages
If a page explains well but resolves nothing, it is not “almost there.” It is incomplete.
6. The Editor’s Litmus Test
Before approving, editors should ask:
“If this page were summarized by an AI, would our judgment survive intact?”
If not, the page is raw material—not an asset.
The Editor’s Creed
Clarity is not a tone. Judgment is not optional. Influence is not accidental.
Editors protect all three.