Critique of What Counts, script v1

Read as a non-fiction editor with no stake in the Second Renaissance and no memory of the trilogy. Adversarial by design.

What is working — protect these

The reversal in the cold open is real. "It should have taken an afternoon / they still have not answered it / that is the most useful thing all year" is a genuine turn, not a slow headline. Sentence four is flat and the fifth pays it off. Keep the shape exactly.
"Progress on what?" is the best moment in the script. Robert's twenty years of students are conceded fully before the distinction lands, so the distinction feels earned rather than scored. The line "Individual learning compounds. Group knowing, without something to hold it in, does not" is the thesis of the whole piece in eleven words.
Robert is a real objector, not a foil. His position is quoted at length, is coherent, and is never defeated — it is absorbed. For a piece handed to people inside the initiative, that is the single most important thing the script gets right. Do not let revision tidy him.
"The tree failed in public" is the argument for the whole method, made in four words, without teaching anything. This is the piece's proof and it is placed correctly.
The ending refuses the flourish. "It is dull work. Nobody here was ever short of ideas." Flat, forward-looking, aimed at SR rather than at the series.

Problems, worst first

1 · It is a third too long, and the overrun is all in the second half

The body runs ~1,850 words against a form baseline of 1,100–1,400. The header claims ~1,450, which is wrong; that error matters because it means the length was never actually checked.

The overrun is not evenly spread. Everything through "the trees' first real product" is economical. From "Consider what touching the trees actually required" onward the script starts covering topics rather than telling the story: the dancefloor, the cloud, the onramp, the prerequisites, the levels, the close. Six beats where there is appetite for three.

In this form, length is not a word count — it is screens. Every 16 words is a drawing that somebody has to make. At 1,850 words this piece needs roughly 115 text blocks and a comparable number of distinct visual states. Nobody is going to draw that, so what will actually happen is that the back half gets built as text on a background, and the piece stops being an explainer halfway through.

Cut to ~1,300. The cut has to come out of the back half.

2 · The back half enumerates instead of arguing

Symptom of the same disease. Four consecutive sections each introduce a new artifact:

the cost stack ("read five diagrams, learn a grammar, locate your point, defend it")
the conflict cloud (spontaneity vs structure)
the onramp (conversation / listener / merging circle)
the obstacle list (four obstacles, four fixes, delivered as a run of four)

The obstacle paragraph is the worst offender: four items in a row is a list, and it reads as a list even set as prose. It also arrives after the reader has already been shown the conflict being dissolved, so it adds no tension — it is a status report.

Cut the obstacle paragraph entirely, or reduce it to the one obstacle that carries the theme (one person can still quietly decide what the map says → an update protocol), which is also the only one that is a callback rather than a new idea.

3 · The levels section is a different piece

"The trees have levels… the map for everyone stops being something to declare and becomes something to arrive at" is genuinely the most exciting idea in the material. It is also the first appearance, at 85% depth, of an entirely new scale — individual, group, everyone — introduced in three sentences and then abandoned for the close.

A reader either bounces off it or wants the piece to be about it. Neither is what you want sixty seconds from the end.

Two options. Cut it, and let the piece end on the protocol. Or promote it into the close so that the ending is about the demotion — the Second Renaissance trees are one group's trees — which is a stronger and more modest note to leave an SR reader on than "it is dull work." Recommendation: cut. It is the seed of the next piece, not the end of this one.

4 · The opening disagreement is the wrong disagreement

The brief is that an SR reader recognises their own situation in the first minute. The script opens on movement-vs-monastery, taken from the conflict resolution documents. That conflict is real and it is in the trees.

But it is not the conflict the story is about, and the piece never returns to it. Sixty seconds later the actual disagreement arrives — is this a school or is it transformation-adoption — and the reader has to drop the frame they were just handed.

Worse, movement-vs-monastery is abstract. Two positions, no people, no quotes. Robert exists; the monastery advocate does not. The reader meets an argument before they meet anybody having it.

Fix: open on the disagreement the piece actually walks — Robert's, in his own words, against the definition already on the page. Two named people who both want the same thing and cannot both be right about what to do next. Then the "no procedure for choosing" line lands on a specific case instead of a hypothetical one, and the trilogy pointer sits exactly where a reader first feels the need.

This also saves ~120 words and removes one of the two abstract sections in the front half.

5 · Who is harmed, and by how much?

The stakes are institutional throughout: the group can't decide, the map can't update, the protocol is missing. There is no person in this piece who loses anything.

The material contains one, and the script walks past them. Someone posts a genuinely useful thought — the maps underweight place, we should be rooted in a watershed — in public, with no idea that a structure exists that could receive it. Nothing happens. They are not rebuffed; they are simply not heard, because hearing them required them to read five diagrams first.

That is the harm. It is small, ordinary, and repeats every week, which is exactly the kind that motivates. Half of the movement's own stated problem — many people resonate, few enter sustained practice — is that person, several thousand times.

Give them three sentences somewhere in the dancefloor section. They are the reason the onramp is worth building, and without them the onramp is a workflow diagram.

6 · The title is doing two jobs and committing to neither

What Counts means both "what should we measure" and "who gets a say." The pun is neat and that is the problem — it is neat, and it is inherited unexamined from the earlier draft.

Test it against the spine: the spine is that a group discovered it had no legitimate way to change its own mind. "What Counts" points at the throughput question, which the piece explicitly abandons in the last movement.

Candidates worth testing: The Map Nobody Could Redraw (matches the spine, slightly literary), Whose Map Is It (matches the spine and is a question the reader will want answered), Define Throughput (dry, specific, ironic once you have read it — the instruction the piece never manages to follow). Recommendation: Whose Map Is It.

7 · Signposting and telling the reader what to conclude

Four instances, each costing a screen:

"Start where the initiative actually is." — pure signpost, cut.
"Look at the shape of that." — instructs the reader to notice what the next sentence says anyway. Cut; the sentence after it does the work.
"It is worth being precise about what just happened, because it is the whole reason for doing any of this." — twenty-two words of throat-clearing before the best passage in the script. Cut to nothing and start at "A strategy document absorbs an objection silently."
"Which turns the original question inside out." — cut; the new definition arriving on its own line does this without narration.

Also "That is not a compromise between the two camps. It refuses the premise that they were opposed." The second sentence is the conclusion the reader just reached unaided. Keep the first, cut the second, or keep neither.

8 · The reader finishes with a feeling, not a word

The form's test: what noun does the reader walk away able to use?

The script names throughput and constraint, but both belong to the trilogy and both are deliberately soft-pedalled here. The concept this piece actually owns — a group's inability to legitimately revise its own shared map — is never named. It is described four separate times in four different phrasings.

Name it once, plainly, and reuse the name. The material already offers stewarded commons (from the conflict resolution document) for the solved state. For the broken state the piece needs its own short phrase. Even "no way to change our mind together" would do, if it is used consistently rather than re-described.

9 · Small things

"It survived two days" is a good line, but the piece never says what happened on day three in those terms — it just moves to Robert. Either make Robert day two explicitly, or drop the countdown.
"None of those are strategy. All of them are plumbing." Nice, but it is the third antithesis construction in four hundred words ("not a refusal, a rival definition"; "not a compromise, a refusal of the premise"). Ration to one.
The three trilogy pointers are correctly placed at points of genuine stumble, and each is genuinely optional. No change needed — but if the piece loses the movement/monastery opening, the Arrows Nobody Checks pointer needs to move to the "how does a group settle that" line, which is where it now belongs.
"This page is itself a first draft of a node. Object to it, and watch what happens." Keep. It is the only call to action in the piece and it is the right one.

Ranked fix list

Cut to ~1,300 words, all of it from the back half. (Problems 1, 2)
Re-open on Robert against the standing definition; cut movement-vs-monastery. (4)
Cut the levels section. (3)
Cut the four-obstacle list to one obstacle. (2)
Put a person in the dancefloor section — the unheard contributor. (5)
Retitle, recommendation Whose Map Is It. (6)
Cut the four signposts and the two told conclusions. (7)
Name the broken state once and reuse the name. (8)
Ration the antithesis construction to one use; fix the "two days" beat. (9)

Everything above the line in "what is working" survives all nine.