Script

Second Renaissance first. The room's own loss, then the idea, then the conflict in the way, then the room tries it, then the ask. One question runs through the whole thing: where does the thinking go?

Core is about 45 minutes. Section 5, where the room contributes, is elastic: budget 12 minutes if the room is quiet, up to 25 or more if it is not. Plan for 45 to 75 in total.

Two layers below. First a skeleton: what each beat has to land, with timings. Then the full script: what to actually say, in prose where the wording matters and bullets where it is staging. Demos are marked as blocks, with the intended behaviour in italic.


Skeleton

0 · Cold open: where does the thinking go? (3 min)

  • A sense-making session a few months ago ended on a question: what is the goal of Second Renaissance, and how would we know we were moving toward it? Good question. Good hour.
  • A week later it was nowhere. No note, no thread carrying it. The thinking stayed in the room, and people leave rooms.
  • That is close to the normal outcome here. So: where does the thinking go? That question turned into a project.

1 · The problem: thinking that doesn't accumulate (8 min)

  • The movement has a real thesis that is meant to keep improving as more people work on it. That only works if the improving adds up.
  • It mostly doesn't. One shape of it: a research circle reaches the same conclusion twice in three years. Both times the room agrees. Both times, weeks later, the agreement has nobody's name on it and nothing has changed.
  • Individual understanding compounds. The group's version doesn't. Agreement that survives only in the people who were present is a rumour.
  • Not a shortage of intelligence, or goodwill, or ideas. A shortage of somewhere to put them.
  • Writing it up doesn't fix it: six or seven white papers, 200,000 words. A claim in the middle of a paragraph has no address. You can't point at it, so you can't argue with it, so nothing builds against it. The precise disagreement a newcomer brings is the thing a long document is least able to receive.
  • Scope note: there are two halves, cohering our thinking and coordinating our action. Today is the first. The second is a talk of its own.

2 · The idea, and a look at it (10 min, Demo A)

  • What if what we hold in common is not a stack of documents but a structure. A top claim, broken into the sub-claims it depends on, all the way down. Every claim sits at an address. The links are claims too: this one is necessary for that one.
  • Demo A: the real 2R tree of change on screen. Click a leaf, its path to the goal lights up. Click a link, see the claim it carries.
  • So the tree is two things at once: a thesis about what has to be true, and an object you can improve one claim at a time. Whole and part stay connected.
  • One-sentence aside on lineage: 40 years old, from operations research, called the Logical Thinking Process. Nothing here depends on it.

3 · The conflict, and the turn (6 min)

  • Why don't we already work this way? A real conflict. People want the conversation to stay quick and human; nobody wants to fill in a form. Accumulation wants structure. Looks like you have to choose.
  • One assumption makes it look like a choice: that the structure has to be added by the contributor, at the moment of contributing.
  • That assumption is not true. That is more or less the whole talk.

4 · The move, and watch it work (6 min, Demo B)

  • So don't add the structure at the moment of contributing. Let the conversation be a conversation. Afterwards, separately, a machine reads it against the tree.
  • Demo B: a real forum thread; the reader proposes placements (supports this, challenges that, doesn't fit yet), each linked back to the exact post.
  • A rotating handful of people decide what merges. Not one person, not the machine alone.
  • The cost of contributing falls back to one sentence, where you were already saying it. The filing is someone's job now, and it isn't the contributor's. AI is what makes that affordable.

5 · You try it (elastic, 12 to 25 min, Demo C)

  • Everyone writes ~1,000 characters: something 2R may be missing, underestimating, or getting wrong, or could act on.
  • Fair warning that this is a prototype: provisional trees, early reader, untested merge rules.
  • Take one or two live, through three questions: where does it fit; does it reveal a gap or a disagreement; so what, what would we do.
  • Then the reverse view: which of the eight conditions has the least behind it right now.
  • The point: a paragraph of ordinary thinking became a specific claim, at a place, with a path to an action.

6 · Close: back to the question (4 min)

  • Back to the goal question from the open. You can only ask it of something you can point at.
  • "Goal" and "progress" are loaded words here. Good. That disagreement should live at an address, with a name on it, not be had again next year.
  • The ask: today, write the thousand characters. After today, follow where it lands. If an action comes out of it, own it.
  • Where does the thinking go? Into the tree. At an address. With your name on it. Find the claim you disagree with, or the one nobody is standing under.

Full script

0 · Cold open

A few months ago, one of our sense-making sessions ended on a question. What is the goal of the Second Renaissance, and how would we actually know if we were moving toward it?

It was a good question. It got a full hour.

A week later it was largely forgotten1. Nothing changed in any of the white papers. The thinking stayed in the room.

I don't think this is unusual – either for us at Second Renaissance or in my experience across many other organizations and initiatives. I think it is close to the normal outcome. The community spends time discussing something, really good points are raised and a week later it is gone – and probably a month or two later we'll have the question will be debated again.

Could we do better? And how?

That is what talk is about. How can we provide structure and process to our discourse so that it accumulates? Put more simply: where does the thinking go?

We have been trying to answer that in a practical way, and it turned into a project: Reason Commons. It draws on ideas and patterns that are more than fifty years old – things like the Theory of Constraints by Eilyahu Goldratt, the Pyramid Principle of Barbara Minto and the Logical Thinking Process developed by Goldratt and colleagues.

Today, we want to share with you where we have got to and where we are going.

1 · The problem: thinking that doesn't accumulate

The Second Renaissance is a movement for civilizational renewal. It is largely volunteer. It has a real vision and a real theory of change, and both are meant to keep evolving as more people work on them. That only works if the contributions add up.

Mostly it doesn't.

Take the the research circle. It meets weekly. Several times in last couple of years it has worked its way to similar ideas. Each time, by a few weeks later they are lost and nothing has changed in the core theory of change. And a few months later the topic will start again from the beginning, because everything that produced it was stuck in a zoom call or an old thread on the forum.

The people in the room did learn something. To some extent, individual understanding compounds. Twenty years of someone's students will show you that. What does not compound is the group's share collective understanding. Agreement that survives only in the people who were present is close to rumour.

So this is not a shortage of intelligence, or goodwill, or ideas. It is a shortage of somewhere to put them.

And the obvious fixes do not work. Write it up properly and you get six or seven white papers, nearly a hundred thousand words. But a claim buried in the middle of a paragraph on page forty has no address. You cannot point at it. If you cannot point at it, you cannot disagree with it or improve. A vague disagreement with a long document is one nobody can act on, so in the end nobody makes it. The most valuable thing a new person brings, a specific suggestion or disagreement, is the thing we are least able to receive.

Note

One scope note before we go further. There are really two halves to all of this: cohering our thinking, and coordinating our action. What I have just described is the first half. The second, how work gets organised and tracked against all this, is a talk of its own. Today is about the thinking.

2 · The idea, and a look at it

So here is the idea. What if the thing we hold in common is not a set of documents or a bunch of forum posts but an underlying structure – a tree. A tree drawn from the former and supporting the latter.

TODO: simple right to left tree structure of thought. preferably animated so it grows in an organic way.

A tree helps you structure a thesis. Its root, its foundational node, is the the top claim. Then you break that down into the sub-claims it depends on. And so on: you keep break a claim into subclaims, as far down as is useful. Now every claim has a clear location in the tree. And we can also see exactly how a given claim depends on or supports other claims (we can even see circular reasoning if we spot loops!). What is on the screen is now not just conclusions but the structure of the the reasoning behind them.

Let me show you a real one. This is the Second Renaissance tree of change. It is generated from the actual written corpus.

DEMO A: see the tree On screen: the real 2R tree of change. The goal at the top ("co-initiate a Second Renaissance: a conscious transformation of foundational views, values, practices and institutions toward a wiser, weller, regenerative civilization"), the eight critical success factors below it, sub-claims under those. Do two things and stop. (1) Click one leaf, three levels down, under a condition like "pockets of coherent new culture." Its path up to the goal lights; everything else dims. Say: this claim is not floating in a document, it is at an address, and the address tells you what it is holding up. (2) Click one line between two claims. A one-line gloss appears: "this one is necessary for that one." Say: the links are claims too, so you can disagree with a link without touching the boxes. Ninety seconds. Do not tour the whole tree.

Two things about that tree at the same time. It is a thesis: a claim that these eight conditions, in this arrangement, are what it takes. And it is an object you can work on, one claim at a time, without rewriting the whole thing. The whole and the parts stay connected, so any leaf, however far down, traces back to the goal.

One aside on where the shape comes from, because it matters and then it doesn't. It is about forty years old, it came out of operations research, and it is called the Logical Thinking Process. There is a separate talk that does it justice. Nothing here depends on knowing any of it.

3 · The complication

So why don't we already work like this?

Because there is a real problem: structure takes effort and gets in the way of free flowing discourse. Put simply: structure supports cumulation but it creates friction, especially for new contributors – people you may most want to encourage to join in. It is even more work if you want the structure to enrich the existing discourse – and not just draw from it (e.g. you want the forum posts to be annotated with pointers to the tree of change).

Every group that tries to give itself structure hits it. On one side, people want the conversation to be as accessible, easy and joyful as possible: quick, exploratory, human. Nobody joined a movement for civilizational renewal to fill in a form or through some cumbersome analysis. People are right to be wary of anything that interrupts the flow of thought or dams up discourse. On the other side, accumulation needs structure. If everything stays loose, the good parts dissolve into the scroll and we are back to the same conversation two months later.

It looks like you have a dilemma: Keep it accessible or make it structured so it cumulates.

But fortunately there is one dissolvable assumption underneath that is forcing this choice. The assumption is that the structure has to be put there by a person – even perhaps the person contributing, at the moment they contribute.

That assumption is no longer true in the age of AI. That is what makes a reason commons possible.

4 · The possibility, and how it works

The key point is that structure does not have to be added by a person at the moment of contributing.

We can let the conversation be a conversation. You post your paragraph on the forum the way you were going to anyway.

Afterwards, separately, a machine reads the thread against the tree and proposes where the parts of it belong.

DEMO B: watch it read a thread TODO(@David): pick the specific forum thread — real, public, four to six posts, ideally one that supports a condition, one that challenges a link, and one the tree can't place yet. On screen: a real Second Renaissance forum thread, four to six posts, the kind of exchange that normally just scrolls away. Trigger the reader. Three or four cards appear next to the tree: "this paragraph supports condition 4, pockets"; "this sentence challenges the link between sangha and movement coherence"; "this is a claim the tree has nowhere to put yet." Each card links back to the exact post it came from. Say: nobody in that thread did anything differently. The structure was recovered afterwards, by something whose whole job is to do the filing. Pre-bake it so it lands in about a minute; narrate what it is doing while it runs.

Then a person or group of people (with AI assistance if necessary) decide what actually merges into the tree. It's pull requests for discourse 🙂

And look at what happened to the cost of contributing. It remains simply the effort of writing on the forum. The filing still gets done. But by AI. And it is AI that makes that affordable.

Two years ago this same idea would have ended at "lovely, far too much hand work, nobody will keep it up."

5 · You try it

Now you.

DEMO C: the room contributes (elastic, 12 to 25 minutes) Staging: run it live if the room and the tech are cooperating. Keep a mock-up prepared in advance as the fallback — contributions already collected and already run through the three questions, plus the reverse view — and switch to that without ceremony if the live run stalls. Decide on the day; build the mock-up either way. Step 1. Everyone writes about a thousand characters, on a phone or laptop, into a shared form: something important the Second Renaissance may be missing, underestimating, or getting wrong, or something we could act on. Their words, not tidied. Give it three or four minutes of quiet. Step 2. Fair warning before anyone leans on this: what you are about to watch is a prototype. The trees are provisional and wrong in places, the reader is early, and the rules for what merges are about three sentences long and have never been tested by anyone genuinely annoyed. That is what today is for. Step 3. Pick one or two contributions, ideally one that reads as a gap and one that reads as a disagreement, and run each through three questions on screen. (1) Where does it fit? The tree proposes a location. This is the easy part. (2) Does it reveal a gap or a disagreement? Is it sitting under a condition nobody is currently holding, or is it in tension with a link? Now it is doing work on the group's reasoning. (3) So what? If the room broadly agrees, what is the next action, and who might own it? Step 4. Show the reverse view: the tree with the condition that currently has the least attached to it highlighted. Say: the same structure that tells one person where their idea goes tells everyone which part of the goal nobody is holding. If the placement is weak on a given contribution, say so, place it by hand, and move on. A wrong first guess that a person corrects in five seconds is still the system working.

What you just did, if it went well, is take a paragraph of ordinary thinking and turn it into a specific claim, at a specific place, with a path to an action. That is a lot better than "thanks for your suggestion" and then nothing happens.

It is also, more or less, that forty-year-old method mentioned earlier but powered by AI.

One more thing this buys you, and this part is not built yet. So far the forum has been telling the tree what's happening. It can go the other way: the tree can tell the forum what already happened. A new post that touches a claim could get a quiet tag – "related, see the 2023 and 2026 threads on this" – so the next person reading it knows the ground has been covered before they write the same thing again. The research circle wouldn't have needed a third pass.

6 · Close

Go back to the question the sense-making session ended on. How would we know if we were moving toward what we are trying to do?

You can only ask that about something you can point at. A tree of change, you can point at. One hundred thousand words, you can't.

"Goal" and "progress" and "moving toward" may be loaded words in this room, and that some of you think a renewal is something that emerges not something you can plan towards.

We would agree.

But skilful gardeners and perma-culturists do planning and use reason to improve what they are doing. That is what we are doing here. We are cultivating a commons for reason and a place for better sensemaking to emerge.

Where does the thinking go? Anywhere! What is connected to and supported by? The tree! And a trees has leaves and branches that we can reference and contribute to.

Footnotes

  1. the one thing that came out of it was this work on reason commons ironically – so not a direct update but an attempt to make the theory of change clearer and addressable.

Built with LogoFlowershow