Editorial & Sources Policy

Verum begins with the biblical text. Paths, reading plans, devotionals, topical collections, cross-references, people, places, and historical notes are designed to return readers to relevant passages rather than replace those passages.

Quoted Scripture should identify its translation. Verse wording is not silently blended across translations. Translation text is kept distinct from Verum’s summaries, prompts, and commentary.

Verum uses translations identified as public domain or distributed under licenses that permit their inclusion. Each translation’s rights, attribution requirements, and territorial limitations remain in effect.

The current licensing page identifies the Literal Standard Version, Unlocked Literal Bible, and public-domain translations offered by the app. See Bible Translation Licenses for the detailed notices and source links.

• Paths arrange passages around a stated biblical question and connect observations, key ideas, reflection, and practice.
• Reading plans sequence passages around a book, season, or theme and provide concise daily orientation.
• Devotionals combine a named passage with reflection and prayer while remaining distinct from the Scripture text itself.
• Bible topics use curated verse collections. Inclusion indicates topical relevance, not that one verse alone settles every pastoral or doctrinal question.
• Related next studies use a maintained topic map to connect each page with a relevant Path, plan, devotional, or topic. These links are editorial recommendations, not personalized profiling.

Verum aims to keep three layers recognizable: what the passage says in context, how it may be interpreted within the wider biblical witness, and how a reader might respond. An application prompt should not be presented as though it were itself a verse.

Where faithful Christian traditions differ, Verum should acknowledge meaningful alternatives rather than present one denominational conclusion as the only possible reading. This does not mean every interpretation is equally supported; claims should still be tested against context and evidence.

Historical context, map data, timelines, and original-language notes should rely on identifiable primary texts or reputable scholarly and reference works. Claims that are disputed, approximate, traditional, or uncertain should be labeled accordingly.

Source citations are not yet equally complete across every Verum study surface. Until a specific page provides a citation, readers should treat historical, archaeological, chronological, geographic, manuscript, and language claims as introductory and independently verify important details. Verum should not imply scholarly consensus when no source has been identified.

AI tools may assist with drafting, organization, software development, topic relationships, and visual production. Verum also offers an optional AI Study Assistant that generates an answer after a reader submits a question.

• AI output is not treated as Scripture, revelation, pastoral authority, or proof of scholarly consensus.
• Prompts instruct the Study Assistant to distinguish observation from interpretation, avoid invented quotations and sources, acknowledge interpretive differences, and flag claims that need verification.
• Automation can still make mistakes. The publisher remains responsible for what is released as permanent Verum content.
• Verum does not currently claim that every published page has been reviewed by credentialed clergy, biblical scholars, counselors, or historians.

During site maintenance, identified errors should be checked against the relevant Scripture translation, source data, and code that produced the page. Corrections are made in the maintained content or data source and republished so the same error is not repeatedly generated.

Priority should be given to incorrect Scripture wording or attribution, broken references, materially misleading theological or historical claims, unsafe advice, licensing errors, inaccessible content, and privacy inaccuracies.

Verum does not currently claim a standing external review board or a guaranteed correction timetable. Readers can prepare a report through the Contact & Feedback page; a verified direct inbox will be published there when available.

Verum’s content should exist to help its intended readers understand and engage Scripture—not to manufacture pages solely for search traffic. Titles should accurately describe their content, pages should answer the question they promise to address, and internal links should lead to genuinely related study rather than artificial repetition.

This approach is informed by Google Search Central’s guidance on helpful, reliable, people-first content, particularly its questions about who created content, how it was produced, and why it exists.