Talk — Reason Commons for the Second Renaissance Research Group

Blurb for talk

Title: Where Does the Thinking Go?

Subtitle: Trees of change, forum discussions, and getting Second Renaissance to constantly evolve its vision.

Abstract:

Any movement for civilizational renewal needs its discourse to compound: hypotheses about how renewal happens needs to evolve, questions and suggestions need to be captured and resolved. Right now it often doesn't. Discussions are scattered across the forum or WhatsApp and frequently repeats itself; offers of help struggle to find a place to land.

The proposal here is to develop a “reason commons”, a place where shared thinking anchors to a tree of change — rather than a stack of documents. This means that discourse has a foundation to build on and to contribute to. We show how to use AI to connect everyday conversation to that tree with little extra work.

What this is

A talk to the Second Renaissance Research Group that presents Reason Commons and the Logical Thinking Process through the question "what does Second Renaissance actually need?" — start from the movement's own problem, arrive at claim trees and the AI-assisted onramp as the answer. Second-Renaissance-first, Reason-Commons-second. Roughly two-thirds the 2R problem and the idea, one-third what we've built and what we're asking of the room.

It grew out of a real moment: a sense-making session a few months ago where someone asked what is the goal of Second Renaissance, and how would we know if we were moving toward it? Good question, good conversation — and then the conversation went nowhere in particular. That is the thing this talk is about.

The decision to lead with the 2R problem rather than the Reason Commons story, the alternative framing, and the reasoning behind both, are in notes.md. The raw dictation this was shaped from is kept in the repo at talk/_process/2026-09-01-braindump.md (process material, not published).

Audience

Members of the Second Renaissance Research Group — people actively working on the theory of change, not a cold public audience. Assume familiarity with 2R's framing and vocabulary; assume no familiarity with the Logical Thinking Process or Theory of Constraints. Some of the room is likely to bristle at goal/throughput/optimisation language — that is anticipated and handled in the framing (see notes.md).

Format and time

Core is about 45 minutes. Section 5, where the room contributes, is elastic: 12 minutes if the room is quiet, 25 or more if it is not. Plan for 45 to 75 in total. Three demos, placeheld in the script with the intended behaviour in italic: A (see the tree), B (watch it read a forum thread), C (the room contributes).

The arc

Act	Beat	~min
0	Cold open: where does the thinking go? — the sense-making question, and where it went	3
1	The problem: a movement whose thinking doesn't accumulate; the group's version is a rumour; prose has no addresses	8
2	The idea + Demo A: the tree of change on screen; every claim has an address; links are claims too	10
3	The conflict and the turn: spontaneity vs structure, and the one false assumption holding the dilemma together	6
4	The move + Demo B: contribute normally; a machine recovers the structure afterwards; AI makes it affordable	6
5	Demo C: the room writes; one or two taken through fit → gap/disagreement → so what; the reverse view	12–25 (elastic)
6	Close: back to the goal question; the ask; where the thinking goes	4

Not in this talk

Alignment on action / the tree of action. That is a follow-up talk. It is named here and deliberately set aside — though the 2R tree we show is itself partly a thesis about what to do, so the idea is present implicitly.
The full Logical Thinking Process / Theory of Constraints lineage. Defused to a sentence and a pointer to a companion piece. Nothing in the talk depends on it.
Evaluation / "are we moving toward the goal" as the central thread. Present but secondary for this audience. It would be front-and-centre in a business-oriented version.

Files

File	What it holds
`README.md`	this — purpose, audience, arc, scope
`notes.md`	decisions, audience sensitivities, demo plan, reuse from the old talk, sources, open questions
`script.md`	skeleton outline, then the spoken script under a heading per section; demos as italic blocks
`slides-brief.md`	slide-by-slide: on-slide text, builds, image asks. Feeds the deck build
(later) `index.html` or slides	the built deck

The orphan talk/index.html was written by someone else, is a different (method-first) cut, and is ignored for this work — see notes.md for the parts worth lifting.