The Second Renaissance · the deeper cut
A movement tried to define what counts. What it found was that it had no way to change its own mind.
A scrolling piece: the drawings build as you read. This is the more advanced telling and it assumes you already know what the trees are — The Forum Doesn't Remember, and Doesn't Cumulate is the way in.
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.
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 method is forty years old and was invented for factories. A companion piece, Five Shapes, covers it properly. 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. Name the thing this system exists to produce, so you can find what is limiting the production of it.
The first definition went up without ceremony.
Reasonable. Uncontroversial. It lasted 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.
That is not a refusal. It is a rival definition, and a coherent one.
If the Second Renaissance is a school, throughput is information becoming workable ideas and newcomers becoming practitioners — and the rest of the sequence is educational administration, which is a solved problem.
The group now had two reasonable definitions of what counts.
It had no way to choose between them.
Which is a familiar afternoon. The conversation is warm, both positions get stronger as they are stated, somebody writes a document, and the document reflects whoever held the pen.
Five intelligent people, five incompatible answers, and why arguing almost never settles it — that is the subject of The Arrows Nobody Checks.
The tree had listed define throughput as a task. It was turning out to be a decision.
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, 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 he had no legitimate way to change his own map.
That afternoon, two steps were spliced in above the root of the sequence. Decide how the trees get updated. Validate them enough for provisional use.
Then, and only then, define throughput.
A strategy document absorbs an objection silently. It gets softened in the next draft, and whoever holds the pen wins without anybody noticing there was a contest.
This failed in public. Everyone could see which link Robert's objection attacked, and exactly what got added in response.
The trees' first real product was the discovery that the group had no way to change its mind together.
The next day Robert came back at the premise itself.
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 the 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.
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 more than a year has had the same conversation three times.
So the question the group had failed to answer quietly changed into a different one.
The maps themselves became the thing to improve.
Someone notices the maps are neglecting something — bioregional practice, say — makes the case, and the maps change.
That is a unit of output. It can be counted.
Why 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.
What did touching the trees actually require 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 is fatal.
Somewhere out there is a person who posts, in public, that all this metacrisis talk floats free of any actual place — that the work should be rooted in a watershed.
Nobody rebuffs them. They are simply not heard, because being heard required reading five diagrams first.
It is a real objection to a specific claim in the current reality tree.
The movement's own list of symptoms has a line for this. Many people resonate with the ideas; few enter sustained practice. That is the same person, several thousand times.
Underneath sits an older conflict, and every community that gives itself structure meets it eventually.
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 and alive, and 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 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, and it is not true.
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, because one person quietly deciding what the map says is the thing that started all of this.
The cost of contributing falls to one sentence, said where you were already saying it.
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 everything else in the initiative is waiting behind it.
What comes next 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.
Reconstructed from the Second Renaissance forum, 8–9 June, and research-circle messages, 30 June – 2 July. 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 here; nothing on this page is an invented illustration. The conflict between spontaneous conversation and structure, and the assumption holding it together, are redrawn from the working conflict-resolution diagram. The symptom quoted near the end is UDE 1 of the current reality tree.
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. The watershed contributor is a composite, drawn from the kind of post the prototype was built to catch.
This page is itself a first draft of a node. Object to it, and watch what happens.