cognitive-rhythm-writing

A Japanese writing norm for producing cognitive rhythm

Dense prose becomes boring not because there is too much information, but because the entire text is written in the same cognitive mode. This norm deliberately switches the reader's cognitive mode (observing, wavering, becoming certain, re-confirming) and constantly maintains a "reason to keep reading," thereby creating the driving force to read on.

Norms used together

Before starting work, read ../japanese-tech-writing/SKILL.md .

Basic principles

Pacing is designed not as an increase or decrease in the amount of information, but as switching between cognitive modes. The round trip of observation → hesitation → assertion → re-observation is one unit.
The text always keeps at least oneunresolved tension(an unanswered question, an unverified conviction, an answer promised to be returned to later) open. The moment all tension closes, the reader can stop reading.
Write not in the voice of someone explaining a completed conclusion, but in the voice of a participant thinking as they go. Reenacting the process by which the writer reaches an answer becomes the reader's reenactment of thought.
Constraints on the generation side: When writing new sentences by applying this norm, the material for beat, tension, and looseness must be taken only from the situation side (events, data, and utterances in the target world, and the narrator's state of judgment). Where no material can be found in the situation, add nothing and leave it flat. Creating rhythm with sentences that take the text itself as their topic ("I will not enumerate ~," "the question is only ~") is a violation of the norm, not an application of it. Newly created or reshaped sentences are, at the moment they are written, subjected to the judgment in "How to distinguish looseness from dead writing."
Devices are to be realized, not declared: Do not write the names, procedures, or example sentences of the devices described in this norm ("half an answer," "tension," "payoff," "return the question in halves," etc.) directly into the text. "Return the question in halves" is realized by writing the first half of the answer as content. Sentences that declare an operation to be performed from now on, such as "First I will place only half the answer" or "At the end I will draw the line just once more," are themselves dead writing. If a device functions correctly, the reader does not notice the device's existence.
Situation in expository writing without scenes: In explanatory or descriptive writing that has no narrative scene, the counterpart to the situation side is the nature of the subject itself (data, calculations, trade-offs, naive expectations being broken by facts), along with the reader's inferences and counterquestions. Tension is created from the nature of the subject ("Why do fluency and correctness not coincide?" is about the subject, so it is acceptable). Just because there is no scene, do not substitute talk about the progression of the text for tension.
Prohibition of shortening bias: Do not cut sentences in order to create beats. Cutting the context sharing needed in the introduction (scope, viewpoint, axes of comparison, undecided matters) to make it shorter is not modulation but omission. Editing that raises density should be done only on top of already shared context.

Sentence beats

Strike a foothold with short sentences, flow with longer sentences, and stop with a short sentence. Make "set up -> flow -> stop" the basic beat of a paragraph.
Do not push through with assertions alone. Place assertions and hesitation alternately.
- Assertion: "It was ~," "It is ~," "So that is how it is."
- Hesitation: "It must be ~" (a belief that will later be betrayed), "I think ~. However..." "Could it be ~?"
Hesitation is not weakness but a device. "A conviction that will later be betrayed by facts" becomes a setup that leads the reader's prediction and then collapses it.
- Example: "It must be going well." -> (in the next paragraph) "Yet later, when I looked at the records, it was not so."
At a turning point, the beat of "concession -> turn -> short pause" can be used ("It will probably be ~. It will probably continue to be ~. But what I deal with here is ~. What I want to think about is that."). The short directive sentence after the turn fixes the reader's gaze.

Density waveform of paragraphs

If two or three dense paragraphs continue, place one sparse paragraph. The function of the sparse paragraph is limited to one of the following: fixing a settled matter in one line, presenting the next object of judgment, or switching the distance of viewpoint.
Do not fix the distance of viewpoint. Alternately place paragraphs that lean toward the concrete (records, numbers, statements, code) and paragraphs that step back through signification.
Bullet points can be used not only to compress information but also as a "pause" that stops the breathing of the main text. The sentence that steps back after an enumeration ("In short, ~") works because of this pause.

Design of the opening

The job of the opening is to create one uncollected tension in the first few sentences.The form does not matter. Examples of usable forms:
- From a rephrasing of the reader's felt sense ("You may sometimes feel ~") to a hypothesis ("Perhaps ~ is different")
- A direct question to the reader. However, do not leave it abandoned; immediately return your own answer
- A general proposition carrying conviction. The main text that follows tests that conviction
- A scene in which the narrator's assumption is written out affirmatively and then broken by facts
- A rephrasing, in the words of the person concerned, of the question left by the previous chapter or section
Forecasting and summarizing are not forbidden. If they are one or two sentences carrying an attitude ("When thinking about ~, there can be no more appropriate angle than this," "In other words, it is a story of ~"), then they themselves create tension. What should be forbidden is only an agenda list without attitude ("This chapter deals with A, B, and C").
The resistance the reader will likely feel (old, contrived, impractical, irrelevant to me) should be stated first in the reader's own words, handled briefly, and only then should the main topic begin.

How to Enter a Section

Do not declare "This section deals with ~" at the beginning of a section. Instead, enter with one of the following.
- Restate the discomfort left by the immediately preceding section as the question of the person concerned
- Write the counter-question the reader would naturally have just as it is ("Then, should I have done ~ first?"). Do not answer the counter-question immediately; first receive it with "I do think I wanted to," and then break it down
- Enter from the writer's confession ("To confess, there was also a plan to ~"). The confession is not for self-criticism, but is used as a foothold for the argument immediately after ("This plan is only half right")
Introduce theory, concepts, and quotations after creating a "nameless discomfort" in the reader. Introduce theory not as an answer but as a naming. The order of presenting theory first and confirming it with examples robs the reader of discovery.
Place the bridge between sections not at the end of the previous section but at the beginning of the next section. Adding a forecast of the "next, we will look at ~" type to the end of the previous section is play-by-play commentary and poor writing. If the beginning of the next section opens with a counter-question, discomfort, or confession, the reader will keep reading even without a forecast.

Landing of Enumerations

Once you have enumerated qualities or classifications, do not leave the enumeration as is. Land each item one by one in the concrete scene immediately before ("The first is the true nature of the ~ we just saw," "I can recall the second as well").
Do not make the style of landing uniform. Vary it: pointing out the true nature, recalling it, linking it to a specific fact, abandoning the future.

Collection of Questions and Conclusion

Do not leave questions raised along the way unattended; collect them explicitly. Returning the question half at a time ("Half of the answer is this," "The other half lies in ~") becomes the driving force for the second half.
For the conclusion, land the accumulated abstraction onto something concrete the reader already has (the opening scene, the reader's own experience, the question from the early part) before closing. Do not end while still in abstract discussion or general principles.
Choose to close the tension. You may leave just one thing open at the end. Modesty or leaving it to the reader ("I want the reader to fill in what is missing") functions as room for the reader's participation.
Second-person address, requests to the reader ("Please read with the understanding that ~"), and the writer's modesty or excuses function as looseness only at boundaries such as the beginning or end of a chapter. Do not mix them into the argument in the middle.

How to Distinguish Looseness from Poor Writing

There is only one axis for judgment. Does that sentence update the "situation" or the "document"?

A sentence that updates the situation: it newly conveys events, data, or statements by people in the target world, or the state of the narrator's judgment (assumption, suspension, regret, concession, confession). → It may be left as slack.
A sentence that updates the document: it conveys only how this chapter, this section, this explanation, or the story so far "looks" or "what to write next." → As a rule, delete it.

Typical bad writing (in every case the topic is the text itself, and the information about the situation is zero):

"Up to here, it probably looks like an explanation of a concept. So I'll return to examples right away." (How the explanation looks and the writing plan)
"In short, the theme of this chapter is not ~ but ~." (Only a restatement characterizing the chapter, with no new information about the subject)
"I don't want you to misunderstand, but I'm not trying to deny ~." (A defense that does not specify the misreading being dismissed. If it takes the form of exception 1 below, it can be kept)
"I will not list techniques." "This is not a story about ~. The question is only ~." (A declaration of the nature or scope of the text. Even if negative or short, if the topic is the text itself, it is bad writing)
"First I'll put down half the answer." "At the end I'll draw the line just one more time." (A live commentary on the devices of this norm. Devices are realized through content, not by declaring operations)
"By now ~ has become visible. The next question is ~." "Next we'll look at ~." (A progress preview at the end of a section. The driving force between sections is created by the counterquestion or sense of incongruity placed at the beginning of the next section. Do not preview at the end of the previous section)

Bad writing appears not only in the form of long explanatory sentences but also in the form of short assertions. If, instead of deleting a document-updating sentence, you reshape it into a short assertive tone, it looks like a punchy decisive line and tends to remain. This is the greatest route by which bad writing gets mixed in. Being short and rhythmically good is not a reason to keep it. Whether the rhythm is good or bad is evaluated only for sentences that have passed the topic test.

Typical good slack (in every case it updates the situation or the narrator's state of judgment):

"It must be going well." (An assumption. A setup to be undermined later)
"Well, it's not yet at the point where I need to act immediately, but at some point it will need to be sorted out." (An update of the state of suspended judgment)
"If I had known from the beginning, I would have done so—that is what I regret." (An emotion that makes the error in judgment visible)
"I do think I wanted to do that." (A concession to the counterquestion. A foothold for the turn immediately after)

Even for sentences that speak about the document, only the following four forms may be kept.

Handling objections: Write out the reader's misreading or objection concretely in quotation marks and dismiss it ("If the story so far is read as the claim 'do ~,' that is wrong"). The condition is that the object being dismissed is concretely quoted. A sentence that merely vaguely says "I don't want you to misunderstand" is bad writing.
Setting up and resolving questions: Place at the boundary "In this chapter we consider ~" (only after creating tension), "half of that answer is this." What can remain is only the question sentence itself and the payoff sentence. Declarations of what the main text is not or what it does not do ("I will not enumerate ~," "this is not a discussion of ~") are not the establishment of a question. Delete them unless they take the form of Exception 1 and dismiss a specific misreading.
Requests to and disclaimers toward the reader: Place at the boundary "Please do read it on the understanding that ~."
Opening and closing the frame of an example: Sentences that open the frame of a fictional example or scene ("Let us suppose ~") and sentences that close it ("Let me give the opening example a punchline"). They have the function of reminding the reader that the example is fictional and returning from abstract discussion to the scene. Place them at the boundary (the head of a section). Even if the topic appears to be the main text itself, if it is operating the frame of an example, it is not dead text.

Procedure for deletion and rewriting:

When you find a sentence that merely updates the document, first delete it and read what precedes and follows; if it connects, that is the end of it.
If deletion makes the logic jump, rewrite the content that sentence was trying to point to into a sentence on the side of the situation ("Up to here it looks like an explanation of a concept" -> "These three properties are all present in the opening failure").
If the resulting rewritten sentence still has the main text itself as its topic (merely shortened, merely rephrased), that rewrite is a failure. Unless it fits one of the forms of Exceptions 1-3, delete the sentence entirely and bridge the preceding and following text anew.

Post-writing inspection procedure

Once you have finished a draft, inspect it mechanically in the following order.

Topic test: Pick up every sentence at the head of a paragraph and every independent short sentence, and judge whether it updates the situation or updates the document. For those on the document side, delete or rewrite unless they fall under the form of Exception 3. Sentences newly written or re-split into shorter ones during revision are routes by which dead text enters, so subject them to this test immediately after writing them as well.
Leakage test: Search whether the vocabulary and example sentences of this norm ("half of the answer," "tension," "payoff," "draw a line," "return the question ~," etc.) appear as they are in the main text. If they do, it is evidence that you have declared the device, so delete that sentence and realize the device anew on the side of content. At the same time, check at the end of every section whether there is a "next, ~" type progress preview.
Tension ledger: Enumerate the questions, assumptions, and promises raised in the main text (such as "I will return the answer in halves"), and point to the location of each payoff by line. For those you cannot point to, either add the payoff or cut the question entirely.
Checking the beat: Find places where three or more long declarative sentences continue in a row, and insert a short foothold, a pause, or a hesitation.
Checking the boundary: Check whether second-person addresses, requests, or self-deprecation appear in the middle of the main text. If they do, move them to the boundary or cut them.

How to use the correction instructions

When diagnosing flat prose, pull the prescription from the symptom.

Every paragraph has the same tone and feels tiring: There is no beat in the sentences. Apply inspection procedure 3.
It is correct, yet you feel no urge to keep reading: There is no uncollected tension. Insert one of the patterns that creates tension at the beginning, and use the tension ledger to confirm that at least one remains open from then on.
The temperature suddenly drops in the theory section: The theory appears before the sense of unease. Place a counter-question or confession before the theory, and land each enumerated item in a scene one at a time.
There are loose sentences, yet it still looks slack: The looseness has become document updates (progress narration). Put it through the topic test and rewrite it into sentences on the situation side (subtle emotional differences, suspended judgment, assumptions).
The end of the chapter sounds preachy: It closes while remaining abstract. Place first a sentence that lands on something concrete the reader already has, and end by leaving one unresolved question.
The opening is businesslike: It has become an agenda list with no attitude. Rather than cutting it, give the preview sentence an attitude, or place the processing of the reader's felt sense or resistance before the preview.