Plan — Second Renaissance explainer, narrative restart

Position

Sibling to the Thinking in Systems trilogy, in parallel with it rather than after it — carried over from #7, nothing here contradicts it. Deliberately unnumbered (explainers/second-renaissance/index.html), so nothing implies a required position in a sequence. Should read well either way round: someone who has read the trilogy arrives with context; someone handed only this link, cold, still gets a complete piece.

This plan replaces #7's narrative brief. #7's original job description was, in effect, "rewrite story/draft.md as scrollable — same material, better form." That premise is dropped (see Why this exists). #7's process, sourcing, and pipeline decisions still apply and are restated below rather than re-litigated.

Scope boundary. This plan covers one piece: the accessible on-ramp. The deeper question of how a group would actually define and debate progress — including the real June "define throughput" episode — is out of scope here, noted as a possible separate, later piece. Don't let this plan grow to cover two deliverables.

Why this exists

We don't have a convincing story for why the Logical Thinking Process / claim trees matter to Second Renaissance. This piece is that story.

The current built page (03-script-v2.md, shipped in #7) doesn't tell it. It's a condensed retelling of story/draft.md's "define throughput" episode — same quotes, same beats, tightened prose. That premise assumes a reader already immersed in the trees and the LTP jargon; for a cold SR reader it's a level down from where the piece needs to start, and "what is throughput, and why does that sound like a factory" is the reaction it gets before the actual argument can land.

The thesis: one question, two answers

Not two coequal motivations running in parallel — one thesis, answered two ways, interwoven rather than presented as separate sections.

Answer A — primary. A structured, evolving way of thinking helps Second Renaissance actually align as a project: refine and organize a rigorous theory of change that can evolve over time, integrate new people and new ideas, organize research and work around the theory of change, assess progress against it. Without something like this, the default outcome is fragmentation — everyone pursuing their own version of the work, with little shared sense of direction.

Answer B — secondary, complementary. The same structure lets ordinary forum discourse and sense-making accumulate instead of repeating itself — new people showing up, the same ground re-covered, nothing aggregating — via an AI bridge that nobody has to learn LTP to benefit from. Write this aspirationally: regardless of what's actually built and working today in any existing prototype, describe what becomes possible. This is the SR-scale instance of a general point already in motivation.md: "discussion scatters across forum posts and never compounds into shared understanding" / "cathedral building instead of scattered noise."

Opening

Leads on Answer B's on-ramp into Answer A, not on either in isolation: Second Renaissance is an ambitious, largely volunteer-run project with an evolving thesis — how do new people and new ideas actually join in and cohere with the existing work? That question opens naturally into the forum's actual texture (Answer B), which opens into why that requires structure and not just goodwill (Answer A).

Explicitly not the opening: "what does it mean to make progress on Second Renaissance" — this is itself a level down from the real question, not the top-level hook. And not the word "throughput," or the real June episode — both presuppose a reader already inside the trees.

Ending

No single CTA is locked in. The piece should land both:

1. I can see how to get involved and align myself with the project (Answer A).
2. I can see how my own sense-making and discourse contributes to refining the thesis (Answer B).

A concrete close such as "go look at the trees, find your view in them" is a candidate, not committed — may or may not converge into one beat once drafted.

Audience

Any Second Renaissance community member — forum participants generally, not just the core/research team. Has to work cold: no LTP background assumed, per #7's original brief on this point.

Reuse of the current draft

Deliberately deferred. Candidates worth reassessing once a new stage-1 script exists (not before): the onramp/bridge mechanism (Act VI/VII of story/draft.md, compressed in 03-script-v2.md), the refrain "no way to change our mind together," the individual-vs-group-learning distinction, and the real Robert/David quotes and episode (which, if used at all, belongs in the separate deeper piece noted above under Scope boundary, and still needs their sign-off per NEXT.md's existing open item).

What stays from #7

• Real SR trees (goal, current reality, conflict resolution, future reality, prerequisite — docs/ltp_trees/) as the diagram source; no invented illustrations.
• Process discipline: stage 1 (script) must survive an adversarial critique before stage 2 (visual script) or stage 3 (build) start.
• Model assignments: Opus for stages 1–2 (original writing and visual judgment, no test to verify against), Sonnet for stage 3 (build, checked against an approved visual script).
• Stage files in explainers/_process/second-renaissance/, following skills/scrollable-explainer/SKILL.md.
• Title. "Whose Map Is It" was built for the throughput-episode narrative and may not fit the new one — retitling is open, not decided here.

Open questions

• Retitle, once a script exists to name.
• Whether the real throughput episode becomes its own later piece, and if so, when — not scheduled by this plan.
• The fate of story/draft.md, carried over from #6/#7, still undecided.
• Robert/David sign-off on any real quotes, whenever and wherever they're used — carried over from NEXT.md, unresolved by this plan.

Appendix — brainstorming FAQ

Distilled from the questions asked while shaping this plan, in the order asked.

What in the current draft is worth keeping? Unknown yet — don't decide before the new brief is settled. Assess reuse once a new stage-1 script exists, not now.

Who is this piece for? Any SR community member, not just the core/research team. Has to work cold.

Is this two motivations, or one thesis with two answers? One thesis — "why does LTP matter to Second Renaissance" — answered two ways. Answer A (structured alignment / evolving theory of change / organizing work) is primary. Answer B (forum discourse accumulating instead of repeating) is secondary and complementary, interwoven rather than a separate section.

Where does the existing point about people not self-adopting annotation live? It's a general point, not SR-specific, already in motivation.md: "discussion scatters across forum posts and never compounds into shared understanding." claim-tree-annotation.md / the annotation demo are the related process material, not the source of this specific point.

Should the AI forum-bridge be written as existing or aspirational? Aspirational, regardless of what's actually built and working today.

Should the real "define throughput" episode (Robert/David, June) be used? Not as this piece's spine, and not in the cold open — it already presumes the reader is deep in LTP jargon and trees. If used at all, it belongs much later, heavily reframed in plain language, or better, in a separate deeper piece — out of scope for this plan.

How should the piece open? Not "what does progress mean" — that's itself a level down from the real question. The real top-level hook, chosen from several candidates named (refining a rigorous evolving thesis; new people/ideas joining in; SR as sense-making in service of coherence): how do new people and new ideas actually join in and cohere with the existing work.

What should the ending ask of the reader? Depends on how the piece evolves — don't force one CTA. But land both answers: I can see how to get involved/align myself with the project, and I can see how my sense-making/discourse contributes to refining the thesis.

Does this plan cover the deeper progress/throughput material too, or just the intro? Just the intro piece. The deeper material is a separate, later, out-of-scope piece.