John Madrid · Reformed Life Liturgy

Reusable does not mean ungoverned.

A production web application for Reformed Life Community Church that compiles Scripture, fixed liturgical formulas, prayer, and song into a complete order of worship: an in-app Scripture browser, a whole-service compile view, and native Word export. Live and in weekly use.

The problem The standard The answer Governed reuse The honest ledger

Open the live app

30–60 minDown from 2–3 hours of weekly compilation, with Curator review authority preserved.

50Active users across weekly worship, including one Curator and four Compilers.

Jul 2026v1 shipped and verified live in production.

01 · The problem

The knowledge leaked because it had nowhere to live.

Every week, someone at Reformed Life Community Church had to turn Scripture, fixed liturgical formulas, prayer, and song into one coherent order of worship. The tooling was Docs, Sheets, and loose notes. That practice had three structural failures.

No unified view.

Nobody could see Call to Worship through Benediction as one continuous whole while writing it. Coherence had to be held in the crafter’s head.

Default to precedent, not intent.

With nothing surfacing what had already been used and why, the compiler reached for prior selections instead of choosing verses that built the day’s arc on purpose.

No record of how.

Even a well-chosen verse carried no record of how it was meant to be used: line divisions for responsive reading, adapted wording, the fixed formulas around it. The next person guessed at reasoning they were never there for.

02 · The standard

The tool had to beat the manual process before it counted.

Two decisions set the floor for everything that followed.

Equal or better, or it does not ship.

The standard, set in the project’s founding document: the tool must produce a result equal to or better than the current manual process, with full dialogical structure, fixed formulas, and adapted Scripture preserved exactly as required, before it counts as viable. Ease of use is a bonus on top of that floor, not a substitute for it.

Replace the pipeline; do not repair it.

The first export pipeline rendered PDFs and grew fragile on multi-column layouts. Instead of patching it, the project became its own production successor: native Word (.docx) generation, with continuous-flow, multi-column authoring that Word itself lays out. The old pipeline was frozen in place, not deleted.

03 · The answer

One screen for the whole service; one model for how each piece is spoken.

Three design moves carry the weight: source the text, see the whole, and record the intent.

Move 01

Source the text.

An in-app Scripture browser hosts the full Filipino (AB1905) and English (BSB) text directly in the application, with AB2001 available through a licensed widget. Compilers highlight any passage to assign it straight to a Section, keeping Scripture sourcing anchored to a single verified entry point.

Move 02

See the whole.

Every Section of the template sits on one screen while the liturgy is built, so the whole service is visible at once instead of living in the compiler’s head. Fixed Morning and Vesper templates; the Lord’s Day number computes itself from the service date.

Move 03

Record the intent.

A liturgy is not flat prose. Different elements carry different authority, speaking roles, and export rules. The six-part model distinguishes locked canon from living prayer, responsive dialogues from silent rubrics, and Scripture citations from preaching metadata.

Three design moves, one compiled service Sourced text, a view of all service sections, and recorded speaking roles and rules contribute to the same compiled service. These are three complementary design choices, not three automated processing stages. 01 SOURCE TEXT VERIFIED TEXT 02 SEE THE WHOLE ALL SECTIONS 03 RECORD INTENT ROLES + RULES ONE SERVICE SOURCED TEXT SECTION ORDER ITEM INTENT Three design moves, one compiled service Sourced text, a view of all service sections, and recorded speaking roles and rules contribute to the same compiled service. These are three complementary design choices, not three automated processing stages. 01 SOURCE TEXT VERIFIED TEXT 02 SEE THE WHOLE ALL SECTIONS 03 RECORD INTENT ROLES + RULES ONE SERVICE SOURCED TEXT SECTION ORDER ITEM INTENT
FIG_01 · Three design moves, one compiled service

The six item types

Selection

Scripture

Pulls text directly from the Scripture browser, locks in verified chapter-and-verse citations, and preserves hand-adapted wording while keeping the reference intact.

Formula

Canon

Shared Formula wording stays fixed during ordinary service editing. Curators maintain the shared masters and can make a deliberate correction for one service without changing the Library or other services.

Verbal Cue

Presider Guidance

Provides spoken transitions and instructional rubrics for the leader, while compilation rules automatically keep staging directions out of the congregation’s bulletin.

Prayer

Pastoral Voice

Provides a curated library of corporate prayers—including the weekly confession of sin—alongside structural checklists for extemporaneous prayer.

Sermon

Proclamation

Captures preaching metadata—passage reference, sermon title, series, and speaker—without treating the sermon like an arbitrary text block.

Song

Hymnody & Psalmody

Catalogs psalms and hymns by title, tune, and metrical source, keeping copyright-clean records without storing lyric bodies.

One service, three publication formats

Leader Guide

Every item, including leader-only verbal cues, generated as a real Word document for the presiding leader.

Congregation Bulletin

Public-facing items only, from the same compiled service. Same source, tailored for the congregation.

Web View

A mobile-first, no-chrome page for any liturgy, linkable directly. No account needed to read.

One service, three outputsA compiled service contains public text and a leader-only cue. The Guide includes both. The Bulletin and Web View include public text and omit the leader-only cue.ONE SERVICEPUBLIC TEXTLEADER CUEGUIDE • DOCXPUBLIC + CUEBULLETIN • DOCXPUBLIC ONLYWEB VIEW • URLPUBLIC ONLY
FIG_02 · One service, three outputs

04 · Governed reuse

Speed could remove repetition. It could not remove responsibility.

The shared library made knowledge reusable. The Curator governs shared material; the Compiler assembles each week’s service and can place their own Formula proposals. Review is what turns a personal proposal into shared material.

Curator

Maintains the shared library, reviews personal proposals, and controls shared Formula masters. Curators can also use a separate Correct wording action for one service, without changing the Library or other services.

Curator authority over a shared FormulaIn this illustrative Absolution example, an author's personal Formula proposal goes to Curator review. The Curator can promote it into a shared library master and can edit that shared master. The two paths are labelled promote and edit master.ABSOLUTION PROPOSALOWNED BY ITS AUTHORCURATOR REVIEWSHARED LIBRARY AUTHORITYSHARED FORMULAE.G. ABSOLUTIONSUBMITPROMOTEEDITMASTER
FIG_03 · Curator · Shared master authority · Illustrative

Compiler

Builds each service from shared material and personal proposals. Shared wording stays fixed during ordinary editing; Compilers can adapt their own unpromoted proposals and adjust permitted presentation settings.

Compiler authority over service assembly and personal proposalsIn this illustrative Absolution example, a Compiler selects and places the shared Formula into this week's service. A separate path shows the Compiler's own proposal being submitted to Curator review. The assembly and submission paths are separate; Curator review controls promotion into shared material.SHARED FORMULAE.G. ABSOLUTIONTHIS WEEK’S SERVICEABSOLUTION PLACEDPROPOSE AN ADDITIONMYPROPOSALCURATORREVIEWSELECT • PLACESUBMIT
FIG_04 · Compiler · Service assembly and proposals · Illustrative

Example: Absolution. These figures use an Absolution Formula to show the two roles. The Curator reviews a proposed version and maintains the shared library master. The Compiler selects that Formula for the weekly service. A personal proposal goes to Curator review before becoming shared material.

Canon and freedom, side by side: shared Formula wording stays fixed in ordinary service editing, while personal proposals remain adaptable by their owner. Curators can deliberately correct one service without altering the shared master or other services.

05 · The honest ledger

What the page refuses to claim.

Stage honesty is part of the system. Here is the ledger as it stands.

Working: Monday creation. Paused: Saturday publication.

Monday automation prepares the week’s Morning and Vesper services, creating and seeding drafts when needed. A Compiler still assembles each service. Saturday publication is built but paused; its checks require a Ready service and prevent the same revision from being recorded twice.

Live: Formula governance

Shared Formula masters are Curator-controlled. Compilers can place shared material and their own proposals, while ordinary editing keeps shared wording fixed. A Curator can deliberately correct one service. Each placement records its wording so later Library changes do not silently rewrite that service.

Frozen, not deleted: the PDF pipeline

The legacy PDF renderer stays in the codebase, frozen and untouched, reachable only by explicit query. It is not a supported source of present-tense output.

Staged, not overlooked: v2 core

Section reordering, full library management, and cross-day citation warnings remain scoped and sequenced, not missing by accident.

Staged: thematic curation tags

Multi-dimensional taxonomy for library selections—classifying passages and prayers by doctrinal topic, biblical theme, liturgical calendar season, and emotional or pastoral tone—to guide service curation without guesswork.

Staged: presentation slide export

Direct integration with the companion PowerPoint presentation builder, turning compiled responsive readings, creeds, and songs into projection slides without manual copy-pasting.

Staged: offline resilience

Offline capability through client-side data caching and downloadable service packages, ensuring presiders and worshippers can access the liturgy without depending on venue Wi-Fi.

The congregation reads the output every Sunday. The ledger stays public.

Open the live app

06 · Contact

Let’s talk about the system your operation leaks without.

If you’re hiring for AI operations, workflow systems, or application development, I’d be glad to discuss the role, and how to leave your team with systems that keep working after the project ends.