writing-beats

The user has passed (or will pass) a markdown file of raw material.

The user has passed (or will pass) a markdown file of raw material.

If the user hasn't said where the article is saved, ask once and remember the path.

If the user did not say where to save the article, ask once and remember the path.

Then run a beat-by-beat journey once:

Then run a beat-by-beat journey:

1. Write 2-3 candidates from the raw materialstarting beats. Each is a different entry point into the article. Show the beats to the user before writing to the article file. The user picks one. Preview which beats it might lead to once written — like the user looking a short way down the trail.

   Write 2–3 candidate starting beats, drawn from the raw material. Each is a different entry point into the article. Show the user the beats before writing it to the article file. The user picks one. Preview what beats that might lead to once written - as if the user is seeing a little way down the path.

2. After the user picks the starting beat,only that beatwrite to the article file. A beat can be one sentence or several paragraphs — whatever is the natural length for that beat. Stop there.

   Once the user picks a starting beat, write only that beat to the article file. A beat may be one sentence or several paragraphs — whatever that beat naturally is. Stop there.

3. Re-read the article file from disk. Then offer 2-3 candidates for thenext beat — the different directions the journey can turn from the article's current state.

   Re-read the article file from disk. Then offer 2–3 candidate next beats — different directions the journey could pivot to from where the article now stands.

4. Loop steps 2-4 until the article ends naturally.

   Loop steps 2–4 until the article reaches a natural end.

What is a beat (What is a beat)

A beat is one action in the journey. It does one thing — sets a scene, lands a point, poses a question, inserts an aside, twists the angle. Then it stops, leaving the reader where the next beat can turn.

A beat is one move in the journey. It does one thing — sets a scene, lands a point, asks a question, drops an aside, twists the angle. Then it stops, leaving the reader at a place where the next beat can pivot.

The size of a beat is determined by need:

A beat is sized by what it needs:

• If the action needs only one sentence ("Then nothing happened for three weeks."), one sentence.

  A single sentence if that's all the move is ("And then nothing happened for three weeks.").

• If the action needs setup, a short paragraph.

  A short paragraph if the move needs setup.

• If the beat is a self-contained vignette, argument, or example, several paragraphs.

  Multiple paragraphs if the beat is a self-contained vignette, argument, or example.

If a "beat" needs five paragraphs and three subheadings, it isn't one beat — it's two beats stuck together. Split it.

If a "beat" needs five paragraphs and three subheadings, it's not a beat — it's two beats glued together. Split it.

Writing one beat (Writing one beat)

Once the beat is chosen, write only _that beat_ to the article file. Don't write the next beat.

Once a beat is picked, write that beat only to the article file. Do not write the next beat.

Pull material from the raw material pile to fill the beat. You can paraphrase, split, reorganize, or quote. The material pile is a quarry.

Pull material from the raw pile to populate the beat. You can paraphrase, split, recombine, or quote. The pile is a quarry.

Ending the journey (Ending the journey)

The article ends when the journey is complete — not when the material pile is empty. Most material piles will have leftover fragments that go unused. That's fine; that's the point of having more raw material than you need.

The article ends when the journey is complete — not when the pile is empty. Most piles will have leftover fragments that don't make it in. That is fine; that is the point of having more raw material than you need.

Writing rhythm (Writing rhythm)

• Append one beat at a time. Never write ahead.

  Append one beat at a time. Never write ahead.

• Re-read the article file from disk before every write. Absolutely preserve user edits.

  Re-read the article file from disk before every write. Preserve user edits absolutely.

• If the user has heavily edited a previous beat, let it change what comes next.

  If the user edits a previous beat substantially, let it change what comes next.

• If the user says "rewrite that beat" or "go back and try a different beat 3," do it — edit in place, leave the rest untouched.

  If the user says "rewrite that beat" or "go back and try a different beat 3", do it — edit in place, leave the rest alone.