The world's first explainable liturgical planning engine.

Every recommendation flows through a fourteen-stage deterministic pipeline. There is no LLM in the loop, no probabilistic sampling, no hallucination surface.

1. Canonical retrieval from the verified liturgical library
2. Scripture fit vs. the appointed readings
3. Seasonal fit against Advent / Lent / Easter / Pentecost / Ordinary Time
4. Placement fit — entrance, offertory, communion, closing
5. Tradition fit — direct or sibling-tradition equivalence
6. Liturgical context rules (Alleluia in Lent, Christmas hymns in Advent, etc.)
7. Rights validation — copyrighted works without legal basis are rejected
8. Parish resources — hymnals owned, preferred, and excluded
9. Ensemble fit — choir voicing, available instruments, difficulty
10. Style + language alignment
11. Songs to avoid (parish-level exclusions)
12. Recent usage across the last 90 days
13. Ranking and tier assignment
14. Explainability payload construction

Every recommendation ships with a structured reasoning payload — seven human-readable lines each tracing back to a scored factor:

• Scripture fit (which book overlaps matched)
• Seasonal fit
• Placement fit
• Tradition fit (direct verification vs. sibling equivalence)
• Parish resource fit (verified entry number when available)
• Rights status
• Usage history

Underneath, the full score breakdown is available so directors of music can audit every hymn the engine surfaces.

Seven Christian traditions ship with full structured profiles — preferred hymnals, seasonal rules, placement rules, communion conventions, funeral and wedding preferences, choir expectations, and language preferences:

• The Episcopal Church
• Roman Catholic (Ordinary Form)
• Lutheran (ELCA and LCMS families)
• Methodist / United Methodist and heritage bodies
• Presbyterian (Reformed tradition)
• Reformed (RCA / CRC / URC and heritage bodies)
• Baptist (Southern, American, National Baptist bodies)

Every recommendation begins with the appointed readings of the Church. Two lectionaries are structured into the engine today:

• Revised Common Lectionary (RCL) — shared by Episcopal, Anglican, Lutheran, Methodist, Reformed, and Presbyterian traditions
• Roman Catholic Lectionary for Mass — three-year Sunday cycle

Every proper includes the Old Testament, Psalm, Epistle, and Gospel. Principal feasts and holy days are flagged. The engine never invents readings — an occasion that cannot be confidently resolved returns nothing, and the parish planner is told.

The canonical library carries verified, public-domain hymnody across all seven traditions — Latin office hymns, German chorales, Wesley and Watts, African-American spirituals, plainsong, and the twentieth-century canon.

Every work carries structured metadata: biblical themes, doctrinal themes, liturgical themes, sacramental associations, feast suitability, tune metadata (meter, difficulty, instrument suitability, alternate tunes), and documented rights.

When a verified hymn number exists in a parish-owned resource, the engine returns it. When it does not, the engine never invents one.

Musical Intelligence™ powers the Annual Planning engine. A full liturgical year — Advent through Christ the King, 50+ Sundays and every principal feast — generates in under ten seconds against a verified library.

The planner tracks hymn and tune repetition across the whole year, balances choir workload, honors seasonal transitions, respects parish-level exclusions, and surfaces a structured list of conflicts with actionable resolutions.