What Counts — script v1
What Counts — script v1
Stage 1 of 3. Pure narrative. No visual direction, no figure slots, no block numbers.
Working title: What Counts. Alternatives to test in critique: The Map Nobody Could Redraw, Whose Map Is It.
Inline pointers to the trilogy appear three times, each at the moment a cold reader would stumble, each optional. They are marked in the prose as italic asides.
~1,450 words.
In June, a group working on the Second Renaissance sat down to answer one question: how would we know if this is working?
They had plenty to answer it with. Years of white papers, a research circle that meets every week, a shared diagnosis of what has gone wrong with the modern world.
It should have taken an afternoon.
They still have not answered it.
That is the most useful thing that has happened to the initiative all year.
What Counts
The Second Renaissance is a project for civilizational renewal, gathered around the Life Itself collective. Its claim is that our crises are not separate cracks but symptoms of a paradigm in decline, and that a wiser one has to be consciously built rather than waited for.
In early June it did something unusual for its corner of the world. It translated its own written corpus into five linked diagrams — a goal, the obstacles, the tensions, the future, the sequence — so that every claim in its strategy would have an address you could find and argue with.
The very first thing the method asked for was a definition of throughput: name the thing the system exists to produce, so you can find what is limiting the producing of it.
That request has still not been met. In failing it, the group found something it had not been looking for — that the thing limiting the Second Renaissance is not its strategy. It is the way the group thinks together.
Start where the initiative actually is.
Ask five serious people what the Second Renaissance should be doing next, and you get five confident answers that do not fit together.
One says: act like a movement. Narrative, media, partnerships, public invitation. Without scale this stays a reading group with good taste, and the historical window is not waiting for us.
Another says: act like a monastery. Small dense pockets, deep practice, years of it. Scaling before the practice is real just reproduces the old paradigm in new language, and nobody needs another one of those.
Both of those people want the same thing. Both are describing a real risk. And they disagree about what to do on Monday.
So how does a group settle that?
Usually it doesn't. It has the conversation, warmly, for two hours. Somebody writes a document. The document reflects whoever held the pen, and the others go along with it, or quietly don't.
This is the subject of a companion piece — five people, five incompatible answers, and why arguing about them almost never resolves them. It is called The Arrows Nobody Checks.
The Second Renaissance tried a different thing. The trees.
A tree is not a strategy deck. It is a claim, broken into the claims it rests on, drawn so that the joints are visible.
Which means an objection has somewhere to go. Instead of "I'm not sure about the direction," you get: this arrow, here, does not hold.
The method is old — forty years old, invented for factories, and it is the subject of a third piece, Five Shapes. You do not need it to follow what happened next.
At the root of the new sequence sat one action, before anything else could begin.
Define throughput.
The first definition went up without ceremony, in early June.
The rate at which real transformation is durably adopted by people, groups, or institutions.
Reasonable. Uncontroversial. It survived two days.
Robert has spent his working life in education. He read down the new chain of dependencies, stopped at the first item, and wrote:
"The very first point — define throughput — is likely going to have a lot of people all tied up in knots. We're not exactly Adam Smith's pin factory. My take is we're basically in the education business. The throughput is raw information to workable ideas, along with a parallel throughput of people unfamiliar with any of it to advanced practitioners of all of it. We're a school. Without the stupid stuff, like grades and tuition."
Look at the shape of that. It is not a refusal. It is a rival definition, and a coherent one. If the Second Renaissance is a school, then throughput is information becoming workable ideas, and newcomers becoming practitioners — and the rest of the chain is educational administration, which is a solved problem.
The group now had two reasonable definitions of what counts, and no way to choose between them.
The tree had listed define throughput as a task. It was turning out to be a decision. And nobody had said whose.
David had built the trees. He started drafting a defence of his definition, then stopped and posted something else.
"If we were to start defining throughput and jumping into these tasks, we'd be implicitly affirming this tree's validity — and all of those that led up to it. But we don't really have a way of testing the trees' validity and updating them if we find flaws. Since I'm the trees' creator, should I get to decide? Should Rufus? If these trees organize our R&D, they will be very consequential. One or two points of failure wouldn't be in line with what we profess to believe in."
The author of the map had discovered that he had no legitimate way to change his own map.
That afternoon two new steps were spliced in above the root of the chain: decide how the trees get updated, and validate them enough for provisional use. Then, and only then, define throughput.
It is worth being precise about what just happened, because it is the whole reason for doing any of this.
A strategy document absorbs an objection silently. It gets softened in the next draft, and whoever holds the pen wins without anyone noticing there was a contest.
The tree failed in public. Everybody could see which link Robert's objection attacked, and exactly what got added in response.
The trees' first real product was the discovery that they could not yet be legitimately updated.
The next day Robert came back, and this time he attacked the premise.
The trees asserted that groups make real intellectual progress in conversation and then lose it. Robert wasn't sure that was true.
"The educational value gleaned from the group encounter persists in the participants, even if everyone goes separate ways and the group creates no artifacts. Most of the college classes I ever taught were like that. Following my students from as far back as twenty years, many have grown into very responsible positions."
David's answer is the sentence this whole thing balances on.
"The key question is: progress on what? Saying the progress is lost isn't saying that individuals don't develop. It's saying the conversation itself often doesn't."
Then the example. A group has a passionate discussion and minds change — we need to be politically active, it is agreed. Two weeks later nothing has changed. Months later the same discussion happens again, from the beginning, because the conditions that produced it haven't changed either.
Robert is right about people. Twenty years of his students prove it. Individual learning compounds.
Group knowing, without something to hold it in, does not.
Anyone who has been in this initiative for more than a year has had the same conversation three times.
Which turns the original question inside out.
The rate at which the group's shared map of its own thinking gets better.
If the trees organize the work, then improving the trees is the work. That is what the research circle produces. Someone notices the maps are neglecting something — bioregional practice, say — presents the case, and the maps are duly changed. That is a unit of output. It can be counted.
The idea underneath this — that a system's output is set by one limiting thing, and almost never the loud one — is the subject of the first piece, The Wrong Queue.
And it left an engineering problem. How do you aim the intelligence of an entire community at a set of diagrams?
Consider what touching the trees actually required that week.
Read five diagrams. Learn a grammar — sufficiency, necessity, the etiquette of a legitimate reservation. Locate your point among a hundred nodes. Then defend it to the people who wrote them.
Every one of those steps is reasonable. The stack of them is fatal.
Three weeks in, the picture was a structure everybody admired and nobody touched, with its author alone in the middle of it.
Underneath sits an older conflict, and every community that tries to give itself structure eventually meets it.
Some people love the trees — the focus, the clarity, the feeling of effort finally adding up. Others love the conversation exactly as it is: spontaneous, associative, alive. They are rightly suspicious of anything that interrupts it in order to file it.
Both wants serve real needs. Both needs serve the same goal.
The method's move here is not to pick a side. It is to ask what would have to be true for these two to be genuinely opposed — and then to write that assumption down and look at it.
Here it is: structure has to be added by the contributor, at the moment of contributing.
That is the only thing holding the conflict together. It is also not true.
So: let the conversation be a conversation. Nothing interrupts it.
Something else listens afterwards and proposes a place — this sentence supports that node, this one challenges another.
A small rotating circle decides what merges. That is the June lesson, encoded: no single point of failure, including the founder.
And the cost of contributing falls to one sentence, said in the place you were already saying it.
That is not a compromise between the two camps. It refuses the premise that they were opposed.
Then the group did the most characteristic thing in this story: it fed its new solution back into the machine that had just been so unkind to the last one.
What must be true for this to work? One person can still quietly decide what the map says — so there has to be an update protocol. Five diagrams read like a syllabus — so each has to be legible in one screen. A weak suggestion insults the person it invites — so the matching has to be good enough to surprise. Invisible contribution doesn't repeat — so contributors have to watch their sentence change the tree.
None of those are strategy. All of them are plumbing.
And then the demotion, which is the exciting part.
The trees have levels. A person could run them on a life. A group runs them on a mission. The Second Renaissance trees, which had quietly been treated as the top of the pyramid, are one group's trees.
Another circle, with an aligned but different vision, keeps its own. Between them, grafting becomes possible — shared branches, translated nodes, merged goals.
And the map for everyone — the one no committee could ever be trusted to write — stops being something to declare and becomes something to arrive at.
A month ago the question was: what is our throughput?
It is now: by what process does a group of people keep a shared map of its thinking true?
That is a smaller question and a harder one, and it is the one everything else in the initiative is waiting behind.
The next thing to build is not a strategy. It is a protocol. How a proposal enters the map, who hears the objections, who merges, and how the person who offered the sentence gets to watch it land.
It is dull work.
Nobody here was ever short of ideas.
Sources and method
Reconstructed from the Second Renaissance forum, 8–9 June, and research-circle messages, 30 June – 2 July, with the events of 12 July reported by a participant. Quotes are condensed for length; emphasis added. The five trees — goal, current reality, conflict resolution, future reality, prerequisite — exist as written documents and are the source of every diagram in this piece; nothing here is an invented illustration. The onramp and the conflict it dissolves are drawn from working documents, not finished systems: at the time of writing the matching is not good enough and the trees are not developed enough for either to be called working.
This page is itself a first draft of a node. Object to it, and watch what happens.
