Skip to main content

One Text, Many Traditions

A SermonPrepDesk series that takes ONE passage and shows how it is heard across theological traditions — the lens, the emphasis, the characteristic application, the pastoral payoff. It is a living demo of the SermonWise lens engine (17 traditions + universal), disguised as genuinely useful craft content.

Why this (and why NOT "free AI sermons")​

The founder's original idea — publish AI-inspired full sermons and license them for reuse — was rejected because it contradicts the brand promise ("sermon prep help that keeps the sermon yours"), invites the "canned sermon / AI-plagiarism pulpit" stigma, and reads as a theological own-goal to a ministry audience. This series keeps the one part of that idea with real legs — the same text across traditions — and reframes it so it reinforces the promise instead of breaking it:

  • The hero is the preacher's discernment, not a finished manuscript. Viewers leave with insight for their own sermon, never a sermon to copy.
  • It shows the product's genuine moat — the lens engine — which no competitor can imitate, because it's backed by sai_theological_lenses + a real pastor curating.
  • It's descriptive/comparative, not "here's your sermon" — so it sidesteps the sermon-mill stigma entirely.

Tagline / CTA line: "Your sermon stays yours. SermonWise just shows you the whole room before you step into the pulpit."

The format​

Hub (8–12 min, chaptered) — "One Text, Three Traditions"​

One passage, three traditions that genuinely diverge on it. Per tradition (~2–3 min):

  1. The lens — what this tradition brings to the text (one sentence).
  2. The emphasis — what it foregrounds / what it guards against.
  3. A ~60–90s micro-movement preached in that tradition's voice — show, don't tell — always framed "here's how this tradition hears it," never "here's a sermon, take it."
  4. The pastoral payoff — what a congregation in that tradition needs from this text.

Close: "Your tradition is one of these. SermonWise gives you the others — so you preach yours with more depth, and you know how your people are hearing the text before you open your mouth." → sermonwise.ai.

Shorts (4–5 per hub) — extends the existing LensLine format​

  • "Same line, three lenses" — one sentence of the text, three traditions' takes, 30s. (Direct sibling of the LensLine short you already run.)
  • "Did you know a [tradition] hears this text completely differently?" — single-tradition hook.
  • "The one word [tradition A] and [tradition B] fight over in this verse." — the productive-tension hook.

Hard guardrails (non-negotiable — this series lives or dies on fairness)​

  1. Steelman every tradition. Represent each in its best, most charitable form. No caricature, no strawman, no "and here's the winner." Descriptive, not polemical.
  2. Founder transparency, not neutrality theater. John may name his own Reformed leaning openly — that's honest — but must treat the others with full respect and accuracy.
  3. Verify, never invent. Every tradition's distinctives checked against real sources + the product's lens data, NOT from memory. Reuse the kit rule: "Never invent doctrine or attribute positions to denominations." When uncertain, say so and invite correction in comments (engagement + humility).
  4. Honest about the AI. Disclose that SermonWise generates the lens framings and John curates/preaches them. Never imply "the AI wrote a sermon" or that the AI does the spiritual work — that breaks the [[ai-bridge-principle]]. The tool surfaces range; the pastor discerns and preaches.
  5. Existing channel rules apply (no fabricated claims, claims verified against the product before scripting, no negative call-outs).

Text selection​

Pick passages where traditions genuinely diverge in emphasis AND there's a pastoral payoff — not doctrinal combat for its own sake. Open with rich-but-warm texts to establish the charitable tone before the hot-button ones.

Candidate map (confirm divergences against lens data before scripting):

  • Luke 15 — the Prodigal — grace / repentance / covenant-belonging across Reformed · Wesleyan · Catholic. (Doubles as the already-planned "How to Preach Luke 15" evergreen — kill two birds.)
  • James 2 — faith & works — Reformed · Wesleyan · Catholic. The justification classic.
  • John 6 — bread of life — Reformed (memorial/spiritual) · Lutheran · Catholic. Sacramental spectrum.
  • Romans 8–9 — assurance & sovereignty — Reformed · Arminian/Wesleyan · Orthodox. (Hot — schedule after tone is established.)
  • Matthew 13 — the parables — ties to the Ep 1–4 hubs already live; kingdom/eschatology divergence.

Funnel​

"Same line, three lenses" Short (LensLine sibling)
  └─ related-video link → the "One Text, Three Traditions" hub
        └─ verbal + description CTA: "Preach yours with the whole room in view — free prep pack at SermonWise.ai"
              └─ sermonwise.ai (lens feature + Tuesday Prep Pack email capture)

Primary conversion metric: prep-pack signups + sermonwise.ai sessions attributed to the series (per strategy.md §8). Qualitative gold: pastors commenting "do [my tradition] on [text]" — passage/tradition requests are the strongest signal and the content engine for the next episode.

Why it's defensible​

  • Uncopyable: a live demo of the actual lens engine + a real engineer-pastor's discernment. Vendors can't fake the traditions; fail-content channels can't fake the pastoral credibility.
  • Inherently shareable: "how would a [tradition] preach this?" is catnip in pastor circles and seminary groups.
  • On-channel: it serves preparers (SermonPrepDesk's audience), so it doesn't fragment distribution the way full sermons or agent-demo content would.
  • Product demo disguised as craft help — the highest-trust kind of marketing.

Risks & mitigations​

RiskMitigation
A tradition feels caricatured → backlashSteelman rule; verify against sources; invite correction in comments
Drifts into "watch the AI preach"Founder is always the preacher/curator; AI = prep, disclosed
Too academic / long → low watch-throughPastoral payoff stays central; tight per-tradition segments; lead with the hook
Hot-button texts spark flame warsSequence them after tone is set; moderate; frame as understanding, not debate

Production​

Reuses the SermonPrepDesk machine wholesale — production-process.md (OBS/Descript), tools/render-episode.mjs (hub), tools/render-shorts.mjs (shorts). Marginal cost = scripting + a recording day.

Tooling note (2026-06-17): when invoking the headless-Chrome badge/overlay step from the Bash tool on Windows, pass a real C:/... path (not MSYS /c/...) or Chrome screenshots its own error page → opaque overlay → frozen video. See memory/feedback_chrome_headless_needs_windows_path_from_bash.

Open decisions for the founder​

  1. Display name — One Text, Three Traditions (clear, searchable) · Through the Lens · The Whole Room · One Passage, Many Pulpits. (Recommend: One Text, Three Traditions.)
  2. 3 traditions/episode (digestible) vs. occasional 4–5 deep-dive.
  3. Pilot text — recommend Luke 15 (folds in the planned evergreen; warm before the hot texts).
  4. Reuse license — if offered at all, license illustrations/outlines/angles, never a turnkey "preach as your own" manuscript.
  5. Sequencing vs. the date-pegged hubs — slot as evergreen between lectionary episodes, never displacing a dated hub's publish window.