About
The Mission.

If you are a Catholic developer and you want to build something — a prayer app, a liturgical calendar widget, a saint lookup tool — you will quickly discover the same thing every one of us has discovered: the data is everywhere and nowhere.

There are PDFs of the Summa scattered across university servers. There are hagiographic databases behind paywalls or riddled with errors. There are liturgical calendar APIs that disagree with each other. There is no single, clean, structured, freely accessible source of Catholic data optimized for developers.

So you spend more time hunting for data than building your product. Or you give up. Or you hard-code fifty feast days and call it done.

Torch & Lily exists to end that.

We are building the Digital Scriptorium — a unified operating system for the Faith. Not an app. Not a content site. An infrastructure layer.

Five engines. One API. Everything a Catholic developer needs to build without reinventing the wheel:

• Veritas — Scripture, the Summa, the great theological texts — structured and queryable.
• Devotio — The saints, AI-refined and verified against primary sources.
• Tempus — The liturgical calendar, computed algorithmically for any date.
• Corpus — The physical Church — every mapped parish and cathedral worldwide.
• Communio — The prayer network — anonymous, global, real-time intercession.

The architecture is API-first, built for both human developers and the AI agents that increasingly write their code for them. Every endpoint is designed to be consumed cleanly, documented thoroughly, and trusted absolutely.

There is one honest limitation worth naming plainly: nearly all of the text data in Torch & Lily is public domain.

This means the Douay-Rheims rather than a modern translation. The pre-1927 hagiographic record rather than contemporary biographies. Aquinas as Aquinas wrote him, not as a licensed publisher packaged him.

We have chosen to frame this not as a limitation but as a foundation. The public domain is the bedrock of authentic Tradition. These texts have survived centuries precisely because they are trustworthy. They are not behind a paywall because they belong to everyone. And they are free from the subtle modernizations that can, over time, erode the precision of doctrine.

The Refinery — our AI ingestion pipeline — does not generate theological data. It cleans, structures, and rigorously verifies data against these primary sources. Every saint in the database has been audited. Every record that fails verification is flagged, retried, and if necessary, removed. We would rather have a smaller, accurate database than a large, unreliable one.

This is, in fact, the Thomistic argument for why a project like this should exist at all:

"For even as it is better to enlighten than merely to shine, so is it better to give to others the fruits of one's contemplation than merely to contemplate."

— Thomas Aquinas, Summa Theologiae II-II, Q.188, A.6

  "numerus": 6,
  "titulus": "Whether the religious life of those devoted to contemplation is more excellent than that of those occupied with action",
  "sed_contra": "Gregory says: 'Great are the merits of the active life, but greater still those of the contemplative.'",
  "respondeo": "...sicut maius est illuminare quam lucere solum, ita maius est contemplata aliis tradere quam solum contemplari. For even as it is better to enlighten than merely to shine, so is it better to give to others the fruits of one's contemplation than merely to contemplate...",
  "scripture_citations": [ /* hydrated */ ]

The text, structured. The Tradition, queryable. That is the whole project.

As the project matures and licensing allows, the data will expand. But the standard of verification will not lower.

The name carries the architecture.

The Torch is the backend — immutable, objective, illuminating. It holds the record of what is true: the texts, the saints, the calendar, the geography. It does not speculate. It does not hallucinate. It serves what has been verified.

The Lily is the frontend — the living, growing space where developers and users actually dwell. This developer portal, Ostium (the Gate), is the threshold between those two worlds. Beyond it, the Torch API. Within it, the tools to build whatever you imagine.

One Catholic developer. No team. No VC funding. No roadmap driven by quarterly metrics.

This is a passion project built out of a genuine conviction: that the tools Catholic developers need should exist, and that if they do not yet exist, someone ought to build them. The Church has always understood that beauty and truth require craft. Good software is no different.

If you are building something — a rosary app, a homily tool, a parish directory, a liturgical clock — and the Torch API can be useful to you, then this project has done its job.

Contributions, feedback, and collaboration are welcome. This is not a finished product. It is a living archive, tended with care, offered freely.

Access is currently free while the data accumulates. Pricing, if any, will be introduced transparently and proportionally as the project matures.

If you are building something with the Torch & Lily API, encountered an issue, have a suggestion, or simply want to say hello — reach out. This project is built by one person and responds accordingly: personally and without a ticket system.

For Communio tenant access, integration questions, data corrections, bug reports, feature requests, or anything else:

This project is maintained as a Lay Dominican apostolate — an expression of the Order of Preachers' ancient mission to preach truth through every available means. The tools change across centuries. The mission does not.