Bring a hard moment to the app. It finds trusted sources, explains them simply, offers prayers or practices, and gives you space to write your journey.
Loading downloaded source text...
Christianity guidance
The Bible does not shame a person for needing help. It teaches trust in God, honest work where possible, contentment, generosity, wise planning, and community care. It also warns against greed, crushing debt, exploitation, and anxiety becoming your master.
No source text or reviewed source object matched this query yet. The app should say that clearly instead of inventing.
Follow-ups can only reorganize retrieved source sections and visible citations. They refuse when this exact request has no source-backed object.
God cares about daily needs, work, honesty, contentment, generosity, and justice. Money is treated as a stewardship issue, not the measure of a person's worth.
Joseph prepares during abundance, Ruth and Naomi survive loss through loyalty and provision, Elijah is fed in scarcity, and the early church shares with people in need.
Pray honestly for daily bread, wisdom, contentment, work, open doors, and a heart that does not become ruled by fear or greed.
The Bible encourages diligence, wise counsel, planning, avoiding oppressive debt, and caring for family and neighbors.
What do you need today, what fear is loudest, and what is one wise next step you can take without panic?
Private by default. Entries are encrypted at rest, export is opt-in, delete is always available, and the app is not an emergency monitor.
This is a faith-learning guide, not professional legal, medical, financial, therapy, or clergy advice. In danger or crisis, seek local emergency help or a trusted person immediately.
The app is not a new authority. It is a librarian and translator that retrieves a user's own sources, organizes the topic, explains gently, and shows what still needs human review.
The answer starts by finding matching source packs, review status, branch or school, topic, and safety sensitivity.
The app explains the source map at the user's level, with simple and deeper modes, without inventing doctrine.
Every response shows sources, review state, professional-advice boundaries, and what the app is not allowed to do.
We start deep before we go wide: three tracks prove the structure, then every other faith gets the same respectful source-pack process.
Source packs, hard-moment guidance, audio, daily practice, family learning, trust UX, rights review, and partner content are built as one platform. Content only appears when rights and review are clean.
Downloadable/offline faith packs hold texts, topic maps, dictionaries, practices, rights, review status, search index, and checksums.
Hard moments like divorce, grief, anxiety, doubt, and money pressure become source, story, practice, warning, next step, and diary sections.
Each faith gets its own tools: readers, prayers, calendars, timers, Qibla or Qiblih direction, source sheets, bells, and practice surfaces.
Users can move between hard moment, daily practice, study, family, compare, and diary journey modes.
AI is the advanced companion layer on top of retrieved sources, never the source of truth.
Every answer shows citations, translation/version, review status, branch or school, rights state, and source versus explanation.
Text, translation, audio, offline, summary, AI-use, attribution, and commercial permissions are machine-readable.
Draft, in-review, approved, disputed, deprecated, and blocked states keep content governed.
Diary, goals, memory, export, deletion, and sync are private by default with opt-in personalization.
Crisis, abuse, coercion, scrupulosity-style fear, and professional topics route differently from normal guidance.
A Christian user stays in Christian sources unless they ask to explore another faith. A Muslim user gets Islamic sources and practices. A non-religious user gets philosophy and history without conversion language.
Breadth is tracked like product work: every faith needs source packs, reviewer lanes, practice surfaces, and safety notes before it becomes public guidance.
Approved launch situations: financial hardship, divorce, loss parent, anxiety, doubt, seeking forgiveness, hope, service
Approved launch situations: financial hardship, loss parent, anxiety, doubt, hope, service, seeking forgiveness
Approved launch situations: courage, compassion, suffering, hope, service, doubt
Approved launch situations: anxiety, suffering, compassion, courage, hope, loss parent
Approved launch situations: loss parent, financial hardship, hope, service, seeking forgiveness, doubt
Approved launch situations: service, hope, courage, compassion, identity, loss parent
Approved launch situations: service, hope, compassion, seeking forgiveness, identity, doubt
Approved launch situations: compassion, service, courage, suffering, seeking forgiveness, identity
Approved launch situations: courage, compassion, suffering, hope, anxiety, doubt
Approved launch situations: hope, service, compassion, courage, identity, suffering
Approved launch situations: courage, compassion, suffering, hope, anxiety, identity, doubt
Launch review asks whether the source itself is covered deeply enough, not just whether a few app topics exist. Christianity starts with Bible completeness, then the same primary-source audit moves through Quran and the other included source traditions.
Does Christianity have complete, rights-clean Bible coverage, with Protestant and deuterocanonical/Catholic-sensitive lanes clearly labeled?
Does Islam have the complete Quran text covered with rights-clean source metadata?
Does Judaism have complete Tanakh coverage, with Hebrew and translation lanes clearly labeled?
Does Hinduism have enough primary-source depth beyond one Gita translation for credible launch?
Does Buddhism have school-aware source depth beyond one Dhammapada translation?
Does Sikhism have Guru Granth Sahib source coverage with translation and practice boundaries labeled?
Does Baha'i coverage include enough official writings and prayer sources for public use?
Does Jainism have enough primary-source depth for ethics, ahimsa, and practice coverage?
Does Daoism have enough source depth beyond one Dao De Jing translation?
Does Shinto coverage distinguish historical source texts from living shrine practice?
Does the wisdom/history track have enough primary-source and safety-reviewed educational coverage?
Each faith is exportable as a versioned database pack with citations, review state, rights metadata, local search index, and a checksum. Mobile can use the same pack before live AI is added.
Store a selected faith/religion pack in browser storage for offline testing. This does not make the corpus public-ready; rights and reviewer gates still apply.
Selected: Bahai Faith · 1,559 passages · checksum 1f6f795df3
This pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packThis pack passes the current public-launch gates.
JSON packSource packs now track language, script, direction, translation status, transliteration readiness, and language-aware search aliases. Original text stays separate from translation and explanation.
Keep source version and translation rights visible in search and reader UI.
Keep source version and translation rights visible in search and reader UI.
Keep source version and translation rights visible in search and reader UI.
Keep source version and translation rights visible in search and reader UI.
Keep source version and translation rights visible in search and reader UI.
Keep source version and translation rights visible in search and reader UI.
Localization reviewer must approve display, search aliases, and transliteration labels before public launch.
Keep source version and translation rights visible in search and reader UI.
Testing can show drafts. Public guidance must use approved source objects only, with enough launch-grade coverage to avoid pretending a starter corpus is complete.
Every faith/religion source pack passes the source-pack public gates, but the product remains internal-testing-only until ops, legal, app-store, and deployment gates pass.
Public launch is tracked by approved topics, source-backed explanations, prayers/practices, dictionary help, and family-safe coverage. Missing breadth remains visible instead of being hidden behind a generic chat surface.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
Launch breadth gates are satisfied for this track.
iOS and Android submission work is tracked separately from launch excitement: store copy, privacy labels, data safety, account deletion, package signing, screenshots, billing, and review notes must clear before public submission.
Public app-store launch cannot ship until every included religion has credible primary-source coverage and approved source-backed launch breadth.
No signed iOS build artifact exists for TestFlight or App Store review.
Apps with account creation need in-app deletion and a web resource for deletion requests before Google Play public tracks.
Release readiness, launch content, and source coverage review reports still show internal-testing-only coverage with missing approved source-backed breadth.
Start with Christianity/Bible source coverage, then approve launch-grade source-backed topics, prayers/practices, dictionary help, and family-safe items for every included religion.Subscription plans and product ids are seeded, but App Store/Play products, receipt validation, account recovery, and refund behavior are not production wired.
Create store products, wire receipt validation, test refund/revoke/restore flows, and keep Pro AI source-bound.Expo iOS bundle identifier and build number exist, but signing, build profile, TestFlight artifact, and release checklist are not configured.
Configure EAS or native iOS build credentials, archive profile, build number, and TestFlight upload path.The local /account/delete page and /api/account-deletion receipt flow exist, but the hosted production URL and listing copy are not configured.
Publish a deletion-request URL, add it to Play Console, and verify it deletes account/private-space data safely.Expo Android package id and versionCode exist, but Play App Signing, release keystore, AAB build profile, and upload path are not configured.
Configure EAS or native Android signing, versionCode, app bundle generation, and Play Console internal testing upload path.Safety cards, family mode, and religious boundaries exist, but public app-store policy review is not complete.
Create reviewer-approved app review notes for faith content, youth settings, crisis boundaries, and source authority.App-store readiness tracks submission artifacts and also respects the all-included-religions source coverage gate. It does not override source review, legal approval, rights review, safety review, or the internal-testing-only public release gate.
This is the final lock between internal testing and public release: source packs, hosted ops, legal/privacy, and app-store evidence all have to clear together.
This lane is currently clear for public launch.
No hosted backup policy exists yet.
AI disclaimer draft needs final legal approval before public launch.
Public app-store launch cannot ship until every included religion has credible primary-source coverage and approved source-backed launch breadth.
Release readiness, launch content, and source coverage review reports still show internal-testing-only coverage with missing approved source-backed breadth.
Start with Christianity/Bible source coverage, then approve launch-grade source-backed topics, prayers/practices, dictionary help, and family-safe items for every included religion.The local /account/delete page and /api/account-deletion receipt flow exist, but the hosted production URL and listing copy are not configured.
Publish a deletion-request URL, add it to Play Console, and verify it deletes account/private-space data safely.Expo Android package id and versionCode exist, but Play App Signing, release keystore, AAB build profile, and upload path are not configured.
Configure EAS or native Android signing, versionCode, app bundle generation, and Play Console internal testing upload path.Subscription plans and product ids are seeded, but App Store/Play products, receipt validation, account recovery, and refund behavior are not production wired.
Create store products, wire receipt validation, test refund/revoke/restore flows, and keep Pro AI source-bound.Expo iOS bundle identifier and build number exist, but signing, build profile, TestFlight artifact, and release checklist are not configured.
Configure EAS or native iOS build credentials, archive profile, build number, and TestFlight upload path.No hosted backup policy exists yet.
Execute and verify the runbook for Automated database backups.This report is the public-launch lock. It may show source packs are ready while the product remains internal-testing-only until ops, legal/privacy, app-store, deployment, billing, and reviewer evidence are complete.
The companion now has database-backed terms and journey templates. A user can learn words inside their faith, follow a goal path, and still see review status and safety boundaries.
Licensed partners and Pro AI are scaffolded as entitlement-gated lanes. Paid or partner material stays supplemental, disclosed, attributed, reviewed, and separate from sacred/source authority.
Each translation/version must carry its own license and attribution.
Sefaria material needs version-level license metadata and Jewish reviewer context.
Partner teaching is supplemental and must stay visually separate from sacred/source authority.
App-owned recordings may support practice but do not become sacred authority.
Audio is part of the platform now, but this build is metadata-only: owned recordings, generated-owned prototypes, public-domain candidates, link-only items, and licensed partner tracks stay separated until files, rights, and review clear them.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
Audio metadata is present, but no playable audio file is bundled or streamed yet.
The audio lane can track owned, open, public-domain, external, and future licensed audio now, but metadata alone is not playable audio. No item should play, stream, download, or enter a source pack as media until rights, source binding, review, attribution, and file/URL evidence are complete.
The release lane now exposes hosted-environment gaps, privacy-respecting analytics, feedback intake, and legal documents. These are public-launch gates, not decorative checkboxes.
No hosted backup policy exists yet.
Local Next.js prototype only; production/staging hosting is not configured.
Incident ownership, escalation, and user notice process remain draft.
Smoke API exists locally; external monitors are not configured.
Trust manifest has rollback metadata placeholder; signed production rollback is not active.
Logs must avoid diary contents, prayer text, youth details, and sensitive situation text.
npm run preflight:production reports hosted deployment gaps without exposing secrets.
Dockerfile, .dockerignore, and production start wrapper define a container path for hosts with persistent storage.
Goals are flexible. The app should not promise wealth, healing, or outcomes. It should help users learn what their faith teaches and build faithful, practical rhythms around that.
Competitors have useful ideas. We take the best patterns, but keep the app's center clean: sources, guidance, prayer, diary, practice, safety.
Start posting before launch. Keep it honest: we are building, researching, and listening. No ranking religions, no fake screenshots, no claims the app replaces clergy or professionals.
Early users help choose topics. Reviewers help keep sources, safety, and rights honest.