Seeds of Renaissance — 2027 LTP

Logical Thinking Process (LTP) run from 2026-11-19 with the reasoncommons ltp-v2 skill, from the near-term brief (the SCQ), with the pre-draft as a starting point and the top-level strategy as parent. Standing: in progress; accepted for now, not proof. Full state: sor-2027.ltp.yaml.

Stage: Goal [x] > Reality [x] > Conflicts [x] > Future [x] > Actions [x]

TL;DR

  • Goal (accepted): by December 2027, about 300 regulars (they keep coming back and call the story theirs), about 30 of them catalysts, with YouTube subscribers doubled to about 6,000. Numbers are placeholders until a December 2026 count.
  • Why this goal: success is the bottom of the first funnel (people who have the words and the belonging), not followers. Reach and depth together; a build year, not a learning year. The reasoning and the engagement ladder are in engagement-ladder.md.

How the goal was reached

  1. First draft (AI, from the SCQ): reach about 2x, plus learning which groups outside our circle the story lands with. Rufus: reach alone misses people going deeper (calls, courses, catalysts, local groups), and "an outside group takes up the core" meant nothing to him.
  2. Options: a learning year that grows the core; depth first; reach and depth together. Rufus: reach and depth together, not a learning year; first be clear what we want at the bottom of the first funnel.
  3. A subagent analysis (inputs/2026-11-funnel-success-definition.md) proposed the engagement ladder and anchoring on regulars. Rufus agreed the ladder and left the anchor (regulars or joined) to the AI; regulars chosen, with a pulse question so people who hold the story through the podcast or newsletter count too.

Comments in full: raw/2026-11-19-rufus-comments-2027-goal.md.

Goal tree (2026-11-19)

Reach is measured on YouTube, about 3,000 to about 6,000 subscribers (Rufus, 2026-11-20): one clear number, instead of an about-10,000 total across platforms that counted people twice. Other platforms are tracked monthly.

Goal and CSFs accepted 2026-11-19; necessary conditions proposed, revised after critique. Marks: ✓ in place, ~ partly, ✗ not yet (the AI's estimate).

G  By Dec 2027, about 300 regulars (they keep coming
   back and call the story theirs), about 30 of them
   catalysts who bring in or host others, with
   YouTube subscribers doubled to about 6,000.

CSF1 Far more of the right people find the story
     (reach about 2x)
 ~ Finished work is published steadily
 ✗ Finished work is marketed: each piece pushed to
   where people gather (the 2026 blocker)
 ~ Each piece suits how its platform recommends
 ✗ Pieces that travel get pushed further
 ~ We show up where the groups who feel the
   breakdown gather, beyond our usual circle

CSF2 People recognise the story as theirs: it gives
     them words for what they feel
 ~ One simple core line, recognisable in every
   framing
 ~ Each group hears the line in terms of its own
   route in

CSF3 Every piece offers one clear next step, and the
     way in works
 ✗ Every piece points to one clear next step that
   suits its audience
 ~ The way in works end to end, even under a spike

CSF4 Newcomers are welcomed and have reasons to come
     back
 ✗ Every first-timer gets a personal welcome and
   follow-up
 ✗ Named people, not only Rufus or Sylvie, do that
   each week
 ~ A regular rhythm worth returning to (2027 call
   series not yet set)
 ~ Active places to hang out between calls
   (Discord, the forum)

CSF5 Regulars get a role; some become catalysts who
     host and bring others
 ✗ Anyone who comes back is offered a role
 ~ A catalyst path runs through 2027
 ✗ Catalysts are equipped to start local and
   topical groups (hosting guide not drafted)
 ~ Catalysts are supported without everything
   going through Rufus or Sylvie

CSF6 We see each step of the ladder and act on it
 ✗ Baseline counted in December 2026
 ✗ Each step counted monthly, by person
 ✗ We ask people whether the story is theirs
 ✗ We can tell which reach turns into regulars
 ✗ What we see changes what we do

Changes after critique: needs not means (Acorn, one page and the monthly review move to actions; "come to the call" became "one clear next step"); publishing split from marketing; added who does the welcome, and the "is this story yours?" question; dropped a restatement of CSF4; "pieces show the vision lived" kept for future reality.

Current reality (draft 2026-11-19, revised with Rufus's read)

Gaps against the goal tree, and their causes. Two chains, reach (why so few people find us) and conversion (why few who find us become regulars), with one core driver under both, named by Rufus. His comments in full: raw notes, third round. Items marked (AI) are the AI's, to confirm.

CORE DRIVER
 R We don't apply ourselves strategically and
   systematically to building a following or
   a community
   because:
    K Founders' focus has been elsewhere (Sylvie's
      interest isn't here; Rufus more focused now)
    F Small team, little spare capacity
    H Story not sorted until recently (it is now)
    C Effort spread over ~18 live strands (AI)

REACH: why so few people find us
 B Core team doesn't focus on or optimise
   marketing and content production      <- R
  A We don't publish regularly ("a huge deal")
  G Many small things undone: titles and SEO,
    covers, hooks, clips; content not always
    right for the platform
  I No guests with big followings; guests not
    asked to share with their own following
  2 Finished work published but not marketed
    -> 1 Audience ~10,000 after a decade;
         2026 targets missed

CONVERSION: why few who find us become regulars
 D Community isn't run as a system; content and
   community worked on separately        <- R
  4 Path from a piece to the call exists but
    isn't clear; only recently consolidated
  5 People who come through aren't coordinated
    or supported well
  10 No standard, well-oiled way in to contribute
  11 We don't ask (financial support, resharing)
  12 We don't build community online (engaging
     with people, community-style posts)
  8 Welcome and hosting lean on Rufus and
    Sylvie (AI)                          <- F
  6 Catalyst path early (Acorn 2 being designed;
    no hosting guide)
    -> 3 Conversion OK (Rufus's sense) but
         unmeasured

BOTH
 E No habit of counting                  <- R
  -> 7 We can't see the ladder

Evidence that the small things matter: when a piece does travel it brings subscribers. The Ivan Illich piece (about 18k views) brought about 200; an SEO-led piece about 1.5 years ago brought about 1.5k. Rufus: "50 small things" done better add up to a massive change.

What this means: the problem is less a missing idea than a missing system. R is the core driver; K, F and H explain it, and H is now resolved. That points to the core conflict: where the founders' limited time goes.

Core conflict (accepted 2026-11-19)

Cloud 1, accepted by Rufus ("a really good tension to identify"), the conflict under core driver R. Drafted by the AI, then revised after critique: it is about Rufus's own week, because Sylvie's focus is elsewhere (a given here, not a choice); and the needs are results, not means.

A SoR grows into     B Our work is         D Rufus's hours go to
  a movement      <-   distinctive:   <-[!]  making and thinking
  (300 regulars,       original pieces,      (pieces, ideas,
  30 catalysts,        one clear story       the strands)
  YouTube 6,000)                                  ^
                                                  | CONFLICT:
                                                  | limited hours
                                                  v
                  <- C Enough of the    <-   D' Rufus's hours go to
                       right people find     running the system
                       us and come back      (rhythm, small things,
                                             asks, follow-up)

[!] weakest assumption
ArrowAssumptionHolds?
A ← BWithout depth we are another channel, not a movementYes
A ← CGood work doesn't spread on its own; a decade shows itYes
B ← DOnly Rufus can make the deep work, and it takes most of his timeWeakest. Publishing is irregular, so the time goes into many strands, not into making
C ← D'Only Rufus will run the system; no one else owns itTrue today; changeable
D ⟷ D'His hours are full and the system needs many of them each weekShaky. Each of the "50 small things" is cheap on its own

Injection (accepted), already under way:

  1. A team runs the system, not Rufus alone. Capacity has gone from about 0.5 FTE across comms and community to about 1.5 FTE on marketing and communications: Uriel as content lead, Amanda dedicated to the podcast, plus others. AI multiplies it. This breaks "only Rufus will run the system".
  2. Rufus helps Uriel run it for the first three months.
  3. AI and templates make the small things cheap (titles, SEO, covers, clips, posts); market finished work before making new.
  4. Write the routine down as it settles.

Still open: the new capacity is on marketing and comms. Who carries community (follow-up, the way in, online engagement)? Answered: about 0.8 FTE on community (Petronella and Fae); see cloud 2.

Conflicts 2–4 (accepted 2026-11-19)

New fact from Rufus: about 0.8 FTE on community (Petronella and Fae), not yet as well organised as we'd like; a community strategy is needed. So conflict 2 is no longer "marketing vs community capacity" but how the two work together. A critique found that 2 mostly dissolves, 3 is real only on frequency, and 4 largely repeats cloud 1.

Cloud 2: marketing and community, separate or one ladder

         B Each team focuses on     D Marketing and community
       / its own work      --[!]--  run separately, own goals
A New-                              and counts
  comers                                 ^ shared goals
  keep                                   v blur ownership?
  coming \ C The path from a piece  ---- D' Both run as one
  back     to regular works            ladder, shared goals
           end to end                  and handoffs

[!] marks the weakest assumption.

  • Weakest assumption: focus needs separate goals. Each team can own its rungs inside one shared ladder and stay just as focused. The conflict dissolves.
  • Injection: one shared ladder and one count. Marketing owns Reached to Joined, including every piece's next step. Community owns Joined to Catalyst, including a first welcome within a week. Uriel owns the joins, supported by Fae and/or Asdra (decided 2026-11-20). A short monthly joint review, once the December baseline exists. The community strategy Rufus asked for is written on this ladder.
  • Risk: 0.8 FTE, not yet organised, may not manage a welcome within a week, especially after a spike. Test it in the community strategy.

Cloud 3: deep pieces vs platform norms

         B Our work is distinctive  D Long, deep pieces in
       / (deep, original)  -------  our own form and pace
A Grow                                   ^ [!] depth vs fit
  into a                                 v     and frequency
  movement
       \ C The right people see ---- D' Pieces to platform norms
         our pieces                    (hooks, shorter, frequent,
                                       clickable titles)

[!] marks the weakest assumption.

  • Weakest assumption: packaging changes the substance. Our own evidence says no: the Illich piece was deep and travelled, and an SEO-led piece brought in about 1.5k subscribers. What's left is frequency: platforms reward a steady stream, and deep pieces are slow.
  • Injection: deep inside, platform-native outside. The long piece stays the source; the team packages and cuts it for each platform (titles, covers, hooks, clips, SEO) and tests the packaging piece by piece. Clips from long pieces close the frequency gap, but only partly.
  • Risk: clickbait titles and clips bring followers who never come back. Judge each test by next steps taken (follows, sign-ups, calls), not by views.

Cloud 4: keep every strand vs focus (folded into cloud 1)

         B Keep commitments,        D Keep all live strands
       / relationships and -------  running
A 300      long-term options
  regulars,                              ^ same people's
  30 catalysts                           v time
         \ C Enough focus for --[!]-- D' Time only for strands
           the ladder to work          that feed the ladder

[!] marks the weakest assumption.

The conflict is real for founders' time, which is cloud 1, so it's folded in there. The teams already point at the ladder.

  • Weakest assumption: the ladder is the only value. Some strands serve the long-term strategy.
  • Injection (keeps "no stop list"): a priority order where every strand is tagged by the rung it feeds, or by its long-term role. Bottom-tier strands get capped upkeep time, enough to keep commitments, not zero. Rufus sets the order; check it quarterly. First, list the strands (about 18 is the AI's estimate).

Future reality (summary, 2026-11-19)

The injections together, what they should produce, and the top risks. Short form; the full version is in the YAML.

INJECTIONS                              EFFECTS
1 A team runs the system (Uriel,     -> Steady, well-packaged
  Amanda; Petronella, Fae); Rufus       publishing; more pieces
  helps Uriel 3 months; AI; market      travel; audience ~2x
  finished work first                     (1, 2, A, G, I)
3 Deep inside, platform-native out-  ->
  side; judge by next steps; ask
  guests to share
4 Priority order, capped upkeep      ->
  for bottom-tier strands

2 One shared ladder; teams own       -> More people take one next
  rungs; one owner of the joins;        step, are welcomed, come
  monthly review; ask for support       back (3, 4, 5, 10, 11, 12)
  and resharing
5 Count the ladder: Dec 2026         -> We see each rung and act
  baseline, then monthly by person      on it (7)

6 Catalyst path: Acorn 2 and a       -> ~30 catalysts host or
  hosting guide                         bring others (6, 8)

7 AI as a multiplier across          -> Feeds 1 and 3: a small team
  producing, editing and publishing     publishes steadily; most of
  (Rufus)                               the frequency gap closes

                    => ~300 regulars, ~30 catalysts,
                       YouTube ~6,000 by Dec 2027

Numbers in brackets are the current-reality effects each injection removes. Injection 6 was added here: no cloud covered the early catalyst path (6).

Short-form conflicts settled by these injections: asking for support and resharing (5) sits in injection 2; guests (6) in injection 3; who welcomes (7) is the community team, with founders for key people.

Top risks:

  1. The new team isn't organised yet, so welcomes slip after a spike (watch: share of first-timers welcomed within a week).
  2. Packaging tests drift to clickbait and bring followers who never return (watch: next steps per 1,000 views).
  3. The strands and Rufus's own making pull time back from the system (watch: quarterly priority check).
  4. The December baseline comes in much lower than assumed; reset 300 and 30 then, not later.

Decided: Uriel owns the joins between marketing and community, supported by Fae and/or Asdra (Rufus, 2026-11-20).

Added by Rufus: injection 7, AI as a multiplier. It was implicit in 1 and 3; it is a key injection in its own right, because it changes what a small team can produce.

Actions (accepted 2026-11-20)

Here are the actions to take. Channels, formats and cadence stay with the content strategy (2603); these say what it must cover, not how.

#WhenActionOwner
1DecCount the ladder baseline, due 18 Dec: call attendees (12 weeks, and 3+), Discord and forum actives, course completions, catalysts, overlap by email.Petronella with Fae
2DecAdd 'how did you hear of us?' to every sign-up; design the 'is this story yours?' pulse.Fae
3DecPull six months of per-piece data, with the Illich and SEO pieces: what travelled, what brought next steps.Uriel
4DecList the live strands (AI drafts) and set the priority order, with capped upkeep for the bottom tier; check quarterly.Rufus
5DecDecide membership for 2027: implicit (showing up plus the pulse) or formal sign-up. AI recommends implicit for 2027.Rufus
6DecFinalise sor-2027-strategy.md, the brief for 2603.Rufus
7JanReset the 300 and 30 from the baseline.Rufus
8JanContent strategy (2603). It must cover: market finished work first; packaging tested by next steps per 1,000 views; guest asks; AI across producing, editing, publishing. Uriel picks the means.Uriel with Amanda
9Jan-MarRufus works with Uriel a fixed few hours a week; sets up the AI pipeline with him in January; by end of March the routine is written down and runs without Rufus.Rufus and Uriel
10JanCommunity strategy on the ladder: welcome within a week, a standard way in to contribute, online engagement, asks for support and resharing.Petronella with Fae
11JanRun the pulse in January, then each quarter; keep the monthly count by person.Fae
12FebThe joins: every piece has one next step; the handoff from Joined to a welcome is tested end to end.Uriel with Fae and/or Asdra
13FebOne ladder page and a monthly joint review of marketing and community.Uriel
14Q1-Q2Acorn 2 running in Q1; hosting guide for local and topical groups drafted with the first catalysts in Q2.Petronella

Order that matters: the baseline (1) before resetting the numbers (7); the community strategy (10) and content strategy (8) before the joins (12); the reset numbers (7) before the ladder page (13).

Key results for December 2027:

  1. About 300 regulars, most of whom say "the story is mine".
  2. About 30 catalysts, and at least 5 local or topical groups running.
  3. About 6,000 YouTube subscribers (from about 3,000).
  4. From Q2, at least 90% of first-timers welcomed within a week, including after spikes.
  5. Next steps per 1,000 views rising each quarter.

Changes after critique: an action for each injection (writing the routine down, running the pulse, AI with Rufus named); the 2603 action says what to cover, not the means; the hosting guide moved to Q2; the strand list moved to December to free Rufus's January; the baseline due 18 December; the joins moved to February; the membership decision and finalising the 2027 strategy added.

Main conflicts (list for choosing, 2026-11-19)

Which to work through in detail. Each is a pull between two things we need; "Explains" points to current reality.

#Conflict (one side vs the other)ExplainsReal?Recommendation
1Rufus's hours: making and thinking vs running the systemR, most of both chainsYesDone: accepted; team under way
2New capacity on marketing (reach) vs on community (conversion: follow-up, way in, online engagement)5, 10, 12, 8Likely: the new 1.5 FTE is marketing and comms; community has no named ownerDetail
3Distinctive, deep pieces vs pieces made for the platform (post more, hooks, clips, shorter)B, G, ALikely: depth sets us apart, the platforms reward the oppositeDetail
4Keep every strand vs focus on the ladderC, 2, 6Yes: about 18 strands, and no stop list by choiceDetail (or settle with the priority order already in the brief)
5Ask people (money, resharing, roles) vs don't ask (keep it a gift, avoid feeling salesy)11Plausible; worth namingShort form
6Guests chosen for reach (big followings) vs for depth and fitIPlausibleShort form
7Founders welcome people (quality, relationship) vs others do it (scale)5, 8PlausibleShort form
8Make new pieces vs market finished onesA, G, 2Largely settled by cloud 1's injection (market first)Drop

Open questions

  1. Baseline: how many regulars and catalysts are there today? Count in December 2026.
  2. Membership: formal sign-up as members or supporters, or implicit (showing up)?