Writing rules

Reference: Least first

The rule as we use it, word for word. Every piece on the site is edited against it.

Binding for every piece of prose written in this workspace, same scope as the short-words reference. Read it in full before writing or editing. Apply it top down: the whole piece, then paragraphs, then sentences, then words (short-words). For when each step happens (map, rough draft, final), see the writing-stages reference.


The rule

Start with the least that could work. Read it as the reader. Add only what answers a question the reader would have to ask. Stop when there is no such question.

The default answer to "does this need more?" is no. A layer has to earn its place with one of the reasons below.


Before you start: name the reader

"Does this need more?" has no answer until you know who is reading and what they will do next. Write it down in one line before the first draft:

Reader: . After reading, they will: .

Examples:

  • Reader: an agent loading this skill. After reading, it will pick which tool to call.
  • Reader: Ari, skimming. After reading, he will approve or ask a question.

If you can't fill in the second half, the piece may not need to exist.


The loop

  1. Layer 0: the thesis. Write the point of the whole piece in one sentence. If that line does the job, ship it.
  2. Layer 1: the outline. Write one topic sentence for each point the thesis needs to land. Read only these, in order. They should make the case on their own. Add a point only for a valid reason below.
  3. Layer 2 and on: support. Inside each paragraph, read as the reader and list the questions they would have to ask before they could act.
  4. Keep only the questions that match a valid reason below. Drop the rest.
  5. Add the least that answers each kept question. A sentence, a value, a step. Not a section.
  6. Read the whole piece, top to bottom, as the reader. Fix every seam before the next pass (see Flow).
  7. Go back to 3. Each pass should add less than the last.
  8. Stop when a pass keeps no questions and the read-through finds no seams.

If a pass wants to add more than the one before it, the earlier layer is wrong. Rewrite it. Don't stack on top.

Editing an existing draft works the same way. Cut each part down to its one-line point, then rebuild with the loop. Keep what the loop puts back. The rest goes.


Keep the essay shape

The loop decides how much goes in. It does not decide the shape. Any piece longer than one paragraph keeps these parts.

Opening. The thesis, in the first paragraph, in the first or second sentence.

Body. One paragraph per point, each opening with its topic sentence. Read in order, the topic sentences are a summary of the piece.

Links. Each paragraph's first sentence picks up from the one before and states its own point. See Flow.

Close. A last paragraph that says what follows: the so-what, the decision, the next step. A one-line callback to the thesis is fine if the close then adds something. A pure recap is not. If there is no so-what beyond the thesis, end on the last body paragraph.

Prose by default. Use a list only for parallel items the reader will scan or follow in order. Cutting must never turn a paragraph into fragments. Every cut leaves whole sentences.


Flow

A paragraph that works alone can still break the piece. Every local test in this file answers to the whole.

Work local, judge whole. After every pass, and after any delete, merge or move, read the piece top to bottom in one go. A local edit is not done until the read-through is clean.

A break in flow is a reader question. "Why are we here now?" "How does this follow?" "Which X?" These count as valid questions in the loop, same as a missing step.

Check every seam. Read the last sentence of each paragraph with the first sentence of the next. The second should pick up something from the first: a term, a claim, a result. If it doesn't, fix the order or the opening. A filler transition does not fix it.

Old before new. Start a sentence with what the reader already has. End it with what is new. The next sentence starts from that new thing. This carries flow with no link words at all.

Say the link. When the reader needs to know how two sentences relate (cause, contrast, sequence, example), say it with a short word: so, but, then, because, instead, also. These are not filler. Filler announces a turn without naming the relation.

Order is the main tool. If a seam needs a long bridge, the paragraphs are likely in the wrong order. Move them before you write the bridge.

Cuts leave gaps. When a paragraph or sentence goes, the two around it now touch. Re-read that seam.

Even depth. The loop can take one paragraph three layers deep while its neighbors stay at one. That reads lumpy. Either the deep one is two points and should split, or the others lack layers they also need, or the deep one has too many.

One name per thing. Use the same term for the same thing across the whole piece. A new word reads as a new thing.


Valid reasons to add a layer

These are the only ones.

They can't act yet. A step, value, name, path or place is missing.

They would read it wrong. A likely misread, a term with two meanings here, a case where the obvious reading is the wrong one.

They can't see how two points connect. A link word or clause that shows cause, contrast or sequence between paragraphs or sentences.

The why changes what they do. Give the reason only when knowing it changes the action. A reason that only justifies the rule is padding.

They would doubt it, and the doubt stops them. Give proof when the reader would not trust the claim enough to act.

An edge case will bite. Name the case that causes harm if missed. Not every case.

One example, when the rule is abstract. One. Add a second only if it shows something the first does not.


Not valid reasons

Reject all of these.

  • Completeness. Covering every case is not the job. Covering the ones that bite is.
  • Context for its own sake. Background that doesn't change the action.
  • Covering yourself. Hedges and caveats the reader won't act on.
  • Restating. "In other words", or a summary of what was just said. The close is the one place a short callback to the thesis is allowed, and only if the close adds something.
  • Signposting. "This section covers", "Below we look at". Headings do that job.
  • Filler transitions. "Moving on", "With that in mind", "Now let's turn to". They announce a turn without making one. Flow comes from order and from each paragraph picking up the last (see Flow).
  • It feels thin. Short is not a flaw. Missing is.
  • The reader is new / senior. Name the thing they lack, then add that. Not a general level of detail.

Paragraphs

One paragraph, one point.

  • First sentence is the point. A reader who stops there should have the gist. The rest of the paragraph is layers.
  • Delete test. Remove the paragraph. If the reader loses nothing they need, it stays gone. Then re-read the seam it leaves.
  • Merge test. Two paragraphs making the same point become one.
  • Order by need. What the reader needs first goes first. Background, if it survives, goes last.
  • Lists and tables are layers too. They pass the same test. A table with one useful row is a sentence. A list that carries an argument belongs in prose.

Sentences

One idea per sentence. Two facts joined by cause, contrast, condition or time (because, so, but, when, then) are one idea: the link is the point. Keep them in one sentence.

  • Delete test. Remove it. If nothing is lost, it's gone.
  • Cut throat-clearing. "It is worth noting that", "Note that", "It should be said". Start with the thing.
  • Cut the closing restate. The last sentence of a paragraph that repeats the first.
  • Hedges stay only if the sentence is false without them. "Usually" stays when the exceptions matter. Otherwise cut.
  • Subject and verb up front. Who does what, then the details.
  • Split chains. A sentence with three or more clauses strung on "which", "and" and "while" is two sentences.
  • Unpack long nouns into verbs. "Provide an explanation of" is "explain" (see short-words).

Traps

Answering questions nobody asked. The loop runs on the reader's questions, not on what you know.

Too terse. Cutting until the reader has to guess is a failure too. The loop catches it: a guess is a question they would have to ask.

Staccato. A run of short sentences of the same shape (subject, verb, stop) reads like a list read aloud. Join the ones that lean on each other, and save the short sentence for the point that should land.

Front-loaded context. A "Background" part before the point. Move the point up. Then run the delete test on the background.

Layer creep. Each pass adds a little "just in case". Hold every addition to the valid list.

Two readers. If a human and an agent both read it, name both. Add a layer only when the one who needs it would ask.


Self-check

Scan for these before you ship. Each is a near-certain cut.

it is important to note · it is worth noting · note that · in other words · as mentioned · as noted above · in summary · to summarize · this section · below we · let's · in this document · it should be noted · generally speaking · for context · moving on · with that in mind · now let's turn

Then two questions:

  1. Read only the first sentence of each paragraph. Do they make the case, in order, as a short essay?
  2. Does every layer trace back to a question on the valid list?
  3. Is it still prose? Whole sentences, linked paragraphs, a close that adds something.
  4. Read it top to bottom in one sitting. Did you stop anywhere to ask how you got there?

Back to how we use AI