Seeds of Renaissance — near-term strategy (2027)
Seeds of Renaissance — near-term strategy (2027)
Brief for the 2027 level of the SoR strategy. Sits under the top-level strategy; project record: planning 2649.
SCQ
Revised 2026-11-18 after Rufus's comments on the first draft. Next step: a full LTP on this SCQ (/ltp-v2), with 2027-strategy.md as the pre-draft.
Situation
- The top level is done (provisional; actions agreed lightly). Its 2027 moves: test a simple core with sensers outside the reflective milieu (the gate), set a pacing rhythm, and make a minimal way in. The distribution engine and catalysts come in 2028, after the gate.
- The story and its core lines already exist: the approved manifesto (2026-10-24) and the website ("A movement for civilizational rebirth, seeding what comes next"; "crisis carries within it the seed of rebirth").
- The path after discovery exists: the weekly call, courses, community (2R user flow, June 2026).
- Baseline: about 2,000 Instagram followers, 3,000 YouTube subscribers (Rufus, 2026-11-17); newsletter and podcast about 2,500 each (SoR draft, 2026-10-15).
Complication
- Too few people who would recognise the story as theirs ever find it. The top level names this as the core problem we control: no distribution engine. Rufus: being an order of magnitude bigger is the number one challenge.
- 2026 aimed for 10,000 on Instagram and 5,000 on YouTube and fell well short. The blocker was publishing and marketing finished material, not making more.
- We don't know who it lands with. The audience segments we have are too generic to act on; we need actual groups we could find now (e.g. effective altruists drawn to the broader questions).
- We don't know what growth is realistic, where a platform flywheel starts, which platforms matter (Instagram uncertain), or how much follower growth matters compared with active readers and listeners. The growth research says 10x is not realistic without a breakout, and there is no follower threshold: platforms judge each piece.
- Further down, how people self-organise. Real, but second.
Question How do we get the story in front of far more of the right people in 2027 (about 2x planned, more with a breakout), and learn which concrete groups it lands with, while keeping to the top level's order (test before scaling) and doing less, not more?
Criteria:
- By when: 2027 strategy agreed by end of December 2026.
- For whom: Rufus, Sylvie, Uriel; it is the brief for the content strategy (2603).
- Effort: not a constraint; AI does the drafting. Team hours are (publishing was the 2026 bottleneck).
- Off the table: re-opening the top level; brand and voice; the community self-organisation question; doing more things in parallel.
Issue tree
- How big a jump, on which measures, by when? decided (Rufus, 2026-11-18): about 2x planned, 5x stretch with a breakout, from the growth research
- Which platforms carry growth, at the level of priority? leaning: YouTube for growth, Substack for depth, Instagram for testing; channel detail is for 2603
- Which concrete groups do we test first, and what counts as fit? drafted in 2027-strategy.md
- Reach now, or test first (the top level's gate)? drafted: two-stage reach; to check in the LTP
- What do we stop, so the team can do this? open: needs the live projects named
- What does a newcomer do next? open (path exists; check the links work)
- What do we measure monthly? drafted
Output
sor/near-term/2027-strategy.md, one or two pages: the 2027 reach goal, audiences to test and what counts as fit, what we stop, monthly measures and 3–5 key results. It is also the brief for the content strategy (2603, Uriel), which works out channels, formats and cadence; don't do that here.
Inputs
- Top-level strategy
- 2R user flow, June 2026 and its materials entry
- Rufus's note, 2026-11-17
- Personas (May 2026):
staging/mediahouse-b9c7aa0/strategy/ - 2026 annual plan (tao): reach targets
Prompt
/ltp-v2 on life-itself/strategy/sor/near-term/README.md (the SCQ). Use sor/near-term/2027-strategy.md as a pre-draft and sor/long-term/top-level.md as the parent. Read the growth research in sor/near-term/inputs/ if it has landed. Output: sor/near-term/2027.ltp.yaml, then rewrite 2027-strategy.md from the result (one or two pages; no channels, formats or cadence).