page / editorial policy and trust

Editorial Policy and Theological Standards

Learn how Unfailing Prayers uses Catholic sources, reviews AI-assisted drafts, labels tradition and opinion, handles corrections, and explains its editorial limits.

In brief

Unfailing Prayers to St. Joseph is a family Catholic editorial project, not an official diocesan publication, seminary, or substitute for a parish. We create prayer and educational resources in English using Scripture, the Catechism, official Church documents, liturgical sources, and reliable historical references. AI may assist with research organization and drafting, but material must receive human editorial review, source checking, and pastoral safety review before publication.

We do not claim clerical approval, academic credentials, or personal authorship that has not been publicly identified and verified. Where a page presents Catholic doctrine, historical tradition, a private revelation, or an original prayer, it should say which one it is. Where information may vary by country, diocese, date, or medical circumstance, the page should say so.

Our editorial identity

The public identity of the project is Unfailing Prayers editorial and a family editorial team. The project may ask priests, catechists, clinicians, lawyers, or other qualified people for guidance on particular subjects, but it will name the scope of that review only when a real reviewer has consented to be identified.

The phrase “Catholic resource” describes the tradition and editorial aim of the material. It does not mean that the site speaks for the Vatican, a bishops' conference, a diocese, or every Catholic theologian. Readers should consult their parish and local authorities for sacramental, liturgical, disciplinary, safeguarding, and pastoral decisions.

Hierarchy of sources

When a page makes a doctrinal or historical claim, the editorial process gives priority to:

Sacred Scripture, with the translation identified when a wording matters.
The Catechism of the Catholic Church and official doctrinal summaries.
Ecumenical councils, papal documents, and the Magisterium, read in context.
The Code of Canon Law and current bishops' conference guidance for discipline and sacramental norms.
Approved liturgical books and rites for prayers and worship.
Early Christian, historical, and academic sources, with genre, date, translation, and uncertainty made clear.
Devotional tradition, labeled as tradition rather than silently promoted to dogma.

No source is made more authoritative merely because it appears first in a search result. A popular blog can suggest a question, but it cannot by itself establish Catholic doctrine or a historical fact.

Doctrine, tradition, opinion, and original writing

Pages should distinguish at least four kinds of material:

Catholic doctrine: a teaching presented with the authority and precision appropriate to the Church's sources.
Historical or devotional tradition: a received account or practice that may have different levels of evidence and authority.
Theological interpretation: a reasoned reading of Scripture or history where other Christians or scholars may disagree.
Original editorial composition: a prayer, explanation, example, or application written for this project.

An original prayer is not presented as an ancient prayer. A pious story is not presented as a verified eyewitness record. A private revelation is not presented as public revelation. A search-engine summary is not presented as a Church document.

The review process

Before a new page is published or materially revised, an editor should check:

Intent and usefulness: the page answers the reader's question or provides the prayer without delaying the main help.
Source accuracy: quotations, dates, names, Scripture references, and links are checked against reliable sources.
Theological clarity: Catholic doctrine is not confused with personal opinion, folklore, or a different Christian tradition.
Pastoral care: grief, illness, pregnancy, mental health, abuse, sexuality, money, and legal matters receive appropriate boundaries.
Language and accessibility: English is readable, headings are meaningful, and mobile readers can pray without friction.
Technical integrity: title, description, canonical, structured data, links, images, alt text, and UTF-8 encoding are checked.
Editorial honesty: the author, reviewer, update date, and level of confidence are not overstated.

The SERP-3 method may be used to understand search intent and content gaps. It does not authorize copying wording, structure, examples, images, or unsupported claims from search results.

Use of AI and other tools

Language models and research tools may assist with outlining, comparing supplied reports, identifying questions, drafting plain-language explanations, and checking for repeated phrases. They are not clergy, a magisterium, a primary historical source, or a substitute for an editor.

AI-generated material must be checked for fabricated citations, false certainty, doctrinal confusion, copied phrasing, cultural stereotypes, unsafe medical advice, and invented personal experience. No page should claim that a human theologian reviewed it unless that review actually occurred. The final editorial responsibility belongs to the project's human editor.

Health, legal, financial, and safeguarding limits

Prayer can accompany care; it does not replace it. Pages involving pregnancy, fasting, eating disorders, illness, mental distress, abuse, danger, legal disputes, or financial decisions must direct readers toward qualified professionals and appropriate local authorities.

The site does not promise healing, protection from every harm, a guaranteed relationship or job, a financial outcome, or a particular spiritual result. It does not tell a reader to stop medication, ignore an emergency, conceal abuse, or use a devotional practice as a substitute for evidence and responsible action.

Support for a real family member or therapy project is kept separate from prayer content. A donation is voluntary and is not a spiritual transaction.

Corrections policy

Readers can report an error through the published contact route. A useful correction includes:

the exact URL;
the sentence, citation, image, or link in question;
why it may be wrong or misleading;
a reliable source or relevant local guidance;
the date and, when needed, the country or diocese involved.

The editor should assess the report, verify it independently, correct the page when appropriate, and record a meaningful update date or note. If the matter is uncertain, the page should say so rather than quietly preserve false certainty. Serious safety issues receive priority over cosmetic edits.

What we do not claim

This project does not claim:

universal clerical, diocesan, or academic approval;
that every page was reviewed by a priest or theologian;
that an AI system is an authority on Catholic doctrine;
that every saint story or private revelation is historically verified;
that prayer guarantees a medical, legal, financial, or material result;
that a search ranking proves truth.

These limits are part of trust. Readers should be able to know what a page can offer and where another qualified person is needed.

Anti-thin-content test

Clear reason to exist: tells readers who the project is, what it relies on, what it does not claim, and how corrections work.
Practical usefulness: gives a source hierarchy, review checklist, AI policy, safety limits, and a correction format.
Distinctive depth: prioritizes honest authority boundaries over generic claims of “rigorously approved” content.
Intent satisfied: a critical reader can evaluate the site before relying on an individual page.