Notes

Working notes, decisions, and parking lot. Keeps README.md tight and gives the script somewhere to defer detail to.

2026-09-04

  • How Does Our Thinking Grow (alt title)

The framing decision: 2R-first

Two talks were possible from the same material:

  • A — "What does 2R need?" Open on the movement's problem (thinking that doesn't accumulate; unclear how new people and ideas cohere), arrive at claim trees + the AI onramp as the answer. ~⅔ 2R, ⅓ Reason Commons.
  • B — "What is Reason Commons up to?" Tell the Reason Commons story on its own terms; land the 2R application and the origin story at the end. ~⅔ Reason Commons, ⅓ 2R.

Chosen: A. Reasons:

  • It is their room. Motivation before mechanism — start from the problem they feel, earn the tool.
  • The A arc is a clean top-down chain and it more or less wrote itself in the braindump. B's spine was never articulated — a tell about which is ready.
  • The origin story ("this grew out of our own sense-making question") is a hook near the top of A, establishing we're solving their problem, not importing one. Saved for the end of B it is wasted.
  • Nothing is lost: the Reason Commons vision and what-we-built becomes Act 3–5 of A. Same content, better order.
  • B is the right talk for a different audience — one already sold on the need, assessing the project on its merits. Not a first talk to this group.

B, parked as a one-paragraph alternative: Reason Commons is an effort to make collective reasoning accumulate — take a top-level claim, decompose it into a tree of sub-claims, and let discourse accumulate against that stable scaffold instead of scattering across threads. It started from a Second Renaissance conversation about how the movement knows it is making progress, and 2R is its first real application. Open on the general problem of groups being bad at accumulating reasoning, show the tool and the toy example, then turn to 2R at the end. Write this up properly only if a non-2R venue asks for it.

Audience sensitivities

  • "Goal" / "throughput" / "optimisation" may trigger. Part of this room is rightly wary of instrumentalising a movement for civilizational renewal. Do not lead with "how do we know we're moving toward the goal." Lead with "how do we know we're cohering our thinking" and treat progress-toward-an-aim as the second, gentler half. Name the discomfort out loud — it is a good discussion to have, not a thing to route around.
  • The 40-year factory pedigree (Theory of Constraints / LTP) reads as corporate. The explainer defuses it by making it a footnote: "the method behind this is forty years old and was invented for factories — a companion piece covers it properly, nothing here depends on it." Do the same live: present trees as an obvious idea first, reveal the lineage in one sentence, move on.
  • Assume the room knows 2R's framing and vocabulary cold. Do not re-explain the Second Renaissance thesis at length — one or two sentences, then move.

Two kinds of alignment

The braindump names two needs: cohering our thinking (better hypotheses about how renewal happens, sharper theses for why, researching detail, improving the theory of change) and coordinating our action (where to plug in, how initiatives move together, checking we are making progress).

This talk is about the first. The second — the "tree of action" — is a follow-up talk. Say so explicitly in Act 1. But note the 2R tree of change we show is itself partly a thesis about what to do and is something we can work on to improve, so the tree-of-action idea is present implicitly; we are just choosing to focus on the tree of change and the question of how it gets updated as people talk on the forum.

Naming: tree of change (the theory-of-change / thesis tree) and tree of action (the follow-up). Prefer these over "tree of thought" in the talk.

The evaluation point

"Once you have an actual, shared, living theory of change, you can start to ask whether the work is moving it" — this is real and worth a beat, but secondary for this audience. Put it in the close, framed as one thing this buys you, not as the point of the talk. In a business-oriented version it would be front-and-centre.

Demos

Three, spread through the talk so the room sees the thing working before it hears the whole argument. Full intended behaviour is in script.md as italic blocks; summary here.

  • Demo A (Act 2) — see the tree. The real 2R tree of change on screen. Click one deep leaf: its path to the goal lights up. Click one link: the "necessary for" claim it carries shows. ~90 seconds, no full tour. Job: make "every claim has an address" physical.
  • Demo B (Act 4) — watch it read a thread. A real forum thread, 4–6 posts. Trigger the reader; 3–4 placement cards appear against the tree (supports this, challenges that, doesn't fit yet), each linked to the exact post. Pre-baked for a ~1-minute reveal, narrated live. Job: show the structure being recovered afterwards, with nobody in the thread doing anything differently.
  • Demo C (Act 5) — the room contributes. Everyone writes ~1,000 characters (something 2R may be missing, underestimating, getting wrong, or could act on). Take one or two through three questions, always in order: (1) where does it fit; (2) does it reveal a gap or a disagreement; (3) so what — next action, who owns it. Then the reverse view: which of the eight conditions has the least attached right now. Elastic 12–25 min. The prototype caveat is delivered here, as step 2, so the close doesn't end on disclaimers. Staging: attempt live; keep a pre-baked mock-up (contributions already collected and processed, plus the reverse view) as the fallback and switch to it without ceremony if the live run stalls. Build the mock-up regardless.

Logistics to sort before the talk: which forum thread (and whether its authors are okay being shown); is B/C running live or pre-baked with a live-looking reveal; who operates the screen while the speaker talks; fallback when the AI placement is weak (say so, place by hand, move on — that is still the system working).

Build tasks

  • @David — pick the Demo B forum thread. Real, public, 4–6 posts, the kind that scrolls away without connecting to anything. Ideal: one post supports one of the eight conditions, one challenges a link, one raises a claim the tree can't place — so the reader has something for each card type. (This is also flagged inline in the script's Demo B block.)
  • Reverse-view visual — the tree of change with the least-supported condition highlighted and an annotation count on each of the eight. Needed for the Demo A payoff and Demo C step 4.
  • Static fallback screenshots from the tool, captured in advance: full tree; one leaf-path highlighted; one link glossed; the chosen forum thread; the reader's placement cards; the reverse view.
  • Demo C kit — shared form for ~1,000-character contributions, QR code + short link, screen operator, 3–4 minutes of quiet write time.
  • Build the deck once slides-brief.md is signed off — frontend-slides skill, Life Itself warm-earth template (~/src/life-itself/design/presentations/life-itself-warm-earth-reference.html).
  • Image research pass against the "Assets to source" list in slides-brief.md. Not blocking; every slide works type-only.

Worth lifting from the orphan talk/index.html

Different cut (method-first, "a talk that performs the LTP"), but several lines and beats are strong and reusable:

  • The recognisable open: "a group has a thoughtful two-hour conversation. Three weeks later: where did that progress go?"
  • Two failure patterns: reasoning does not accumulate; willingness is not the scarce resource — somewhere for willingness to land is.
  • "Groups are surprisingly bad at accumulating reasoning — and at converting it into coordinated action."
  • The "imagine a conversation where…" list (insights accumulate, new contributions connect to what's been learned, disagreements become explicit rather than recurring, you can see what is currently blocking progress, offers of effort have somewhere to go, action stays traceable to the reasoning behind it).
  • The destination: "a group gets smarter over time, and its thinking increasingly results in action."
  • The hypothesis: "collective intelligence is not primarily about more intelligent people, or more conversation. It is about the process through which reasoning accumulates, bottlenecks become visible, and action follows."
  • The conflict as two columns: what people want (conversation stays natural and open) vs what accumulation needs (reasoning structured enough to build on).
  • The move: "what if people didn't have to think in trees? What if they could contribute normally, and the system revealed the structure underneath?" — and the disclaimer "not 'we built a graph interface.'"
  • The three demo questions above (fit / gap-or-disagreement / so what) come straight from it.
  • The close: "today, contribute something. After today, follow what happens to it. If there is an action you want to own, take it. Help us test whether this actually makes 2R better at thinking and doing."
  • "The test is not whether the software is clever. It is whether today's contributions improve 2R's reasoning, and cause useful things to happen."

Source material

  • explainers/_process/second-renaissance/07-script-v2.mdSomewhere to Put It, the narrative spine. The talk is essentially this argument delivered to this room.
  • explainers/_process/second-renaissance/08-visual-script.md — how it was visualised; useful for the later slide stage.
  • docs/plans/2026-08-16-second-renaissance-narrative.md — the "one thesis, two answers" framing and the choice of opening.
  • docs/ltp_trees/Goal Tree_ Second Renaissance.md — the goal and its 8 critical success factors. This is the tree of change we put on screen.
  • docs/ltp_trees/ also has current reality, conflict resolution, future reality, prerequisite trees — the five shapes named in the close.
  • motivation.md — the general version of the point ("discussion scatters across forum posts and never compounds… cathedral building instead of scattered noise").
  • claim-tree-annotation.md — the claim-tree + cumulative-annotation process spec and the remote-work toy example.

The 8 critical success factors (from the goal tree)

Goal: co-initiate a Second Renaissance — a conscious transformation of foundational views, values, practices, and institutions toward a wiser, weller, regenerative civilization.

  1. Shared diagnosis of civilizational crisis
  2. Compelling vision of the next paradigm
  3. Embodied practices and inner development
  4. Pockets of coherent new culture
  5. Sangha / wider community of practice
  6. Movement coherence and cultural transmission
  7. New institutions and regenerative social architecture
  8. Wise transition through collapse and renewal

Open questions

  • Which slot — 30, 60, or 75 minutes? Determines whether Act 4 is a full interactive block or a 3-minute walkthrough.
  • Live annotation on the day vs pre-baked reveal. Depends on prototype readiness.
  • Which real forum thread to use, and whether its authors are okay being discussed.
  • Does the evaluation/progress beat stay in the close or get cut entirely for time.
  • Title.
Built with LogoFlowershow