Home

Start here

The course doctrine

Ten stable principles run through your writing work, from writing as a way of thinking to using AI to increase intellectual resistance.

3 min read

On this page 10 sections
  1. 1. Writing is a way of thinking, not merely a way of recording thought
  2. 2. Fluency is presentation, not proof
  3. 3. Private understanding and public communication are different tasks
  4. 4. A public piece needs one primary reader problem
  5. 5. Structure should create movement, not merely order
  6. 6. Concrete detail is evidence when it changes understanding
  7. 7. Voice is not a layer of polish
  8. 8. Revision must happen in the right order
  9. 9. Compression should remove waste, not thought
  10. 10. AI should increase intellectual resistance, not remove it

1. Writing is a way of thinking, not merely a way of recording thought

Putting an idea into sentences creates resistance. Vague connections have to become explicit. Contradictions become harder to ignore. An idea that felt complete in the head may turn out to have no mechanism, no boundary, or no evidence.

So the first draft is not simply a poorer version of the final draft. Often it is an instrument for discovering what the final draft could be about.

2. Fluency is presentation, not proof

A claim does not become more reliable because it is expressed cleanly. An elegant explanation can conceal missing evidence, false causality, imported assumptions, or a framework that merely renamed the problem.

The better the prose sounds, the more important it is to ask what supports it.

3. Private understanding and public communication are different tasks

Before asking how to make an idea valuable to a reader, establish whether the idea is true enough to deserve publication. Your private workflow therefore separates inquiry from reader strategy.

This prevents a common corruption: choosing the most publishable interpretation before knowing whether it is the most defensible one.

4. A public piece needs one primary reader problem

There is no generic reader. A founder, investor, operator, academic, customer, engineer, and future version of yourself notice different problems and accept different evidence.

A piece becomes easier to structure when it is built for one primary reader, one live question or doubt, one intended change, and one central claim.

5. Structure should create movement, not merely order

Chronology is order. A list of categories is order. Neither automatically creates a story or argument.

Strong nonfiction usually moves through a causal or intellectual sequence, such as these:

6. Concrete detail is evidence when it changes understanding

Dates, numbers, gestures, tools, rooms, decisions, errors, quotations, and sensory detail are not inherently vivid or useful. Their value comes from the work they do.

A detail can establish character, constraint, stakes, mechanism, contradiction, or causality. If it does none of those, it may be decoration.

7. Voice is not a layer of polish

Voice comes from what you notice, what you omit, what you doubt, how much certainty you claim, which examples you choose, and what you refuse to simplify.

Trying to "add voice" late often produces mannerisms. Preserving the author's actual judgments and language is more reliable.

8. Revision must happen in the right order

The governing sequence is:

truth → argument → reader value → structure → emphasis → evidence and source fidelity → prose

Editing sentences before the argument is stable wastes effort. It also creates attachment to material that may need to be removed.

9. Compression should remove waste, not thought

Cut repetition, throat-clearing, vague qualifiers, ornamental transitions, duplicated examples, and explanations the reader can infer. Do not delete a distinct condition, countercase, threshold, example, or uncertainty merely to make the piece shorter.

The target is density without loss of meaning.

10. AI should increase intellectual resistance, not remove it

The most useful roles for AI in your writing system are interviewer, critic, source mapper, counterargument generator, structural auditor, reader simulator, and local editor.

The most dangerous role is silent co-author of your final voice. It removes the very friction that helps an idea earn conviction.