Welcome to Scripture Lab

Choose a study face below or use the tabs to jump in.

Scripture Lab is a study workspace for questions, comparisons, canon browsing, and timeline exploration. Choose a face below or use the tabs above (bottom bar on mobile) to jump in. Your question, database selection, and last Ask or Compare results carry across faces for the session.

Ask natural-language questions or look up a verse. Answers are built from verses retrieved across the Bible databases.

  • Choose which databases to search (defaults to All Western; change in Settings).
  • Results stack: Answer, Word meanings, and Verse explanation.
  • Hover words for translation; click marked source words to highlight lexicon notes.
  • Your last result is saved for the session when you switch tabs.

Place one Bible version beside others for the same reference or question.

  • Pick tradition presets (for example KJV ↔ Hebrew) or choose source and targets manually.
  • Arriving from Ask can prefill your question and version selection.
  • See each side’s verse text and notes on differences.

Versions

Open tab →

Browse every referenced translation: tradition, language, license, and whether full text is loaded.

  • Filter to databases you selected on Ask.
  • Check canon coverage (books loaded vs total).
  • Admins can populate public-domain schemas from the collapsed admin section.

Explore whole books across Western, Tanakh, LXX, Ethiopian 81, related literature, and comparative Ancient Near East texts.

  • Search and open a book for setting, literary shape, themes, and summary.
  • Open a chapter guide to see what each chapter recounts and means (Western 66, Ethiopian 81, LXX, and the combined Tanakh books).
  • Switch canon lists to compare how traditions organize Scripture.
  • Ethiopian 81 follows the broader EOTC list (46+35) at ethiopianorthodox.org; Kebra Nagast and Lefafa Sedq are related literature, not the 81.
  • Reception badges mark EOTC 81, deuterocanon, Apocrypha (not LXX), related literature, and comparative ANE texts.
  • LXX 2 Esdras means Greek Ezra–Nehemiah; English 2 Esdras (4 Ezra) is not Septuagint.

Timeline

Open tab →

View biblical journeys on a map and scan chronological events across Scripture’s span.

  • Filter by date range when the filter is enabled in Settings.
  • Toggle the journey map under Settings → Face extras if you prefer a simpler list.

Sources, answers, and verification

Scripture Lab reads verse text and book metadata from PostgreSQL Bible databases. Every loaded translation is a public-domain text. Optional AI commentary is composed only from the verses retrieved for your question — never from the model’s memory alone.

How Ask answers are produced

  • Your question is matched against verses in the databases using keywords, topics, and explicit references.
  • The returned answer, explanation, and cited verses all come from that retrieved evidence pack.
  • When an OpenAI key is set, commentary is generated from the pack; a citation checker strips invented Book chapter:verse references.
  • Without a key, or when a prior verified answer exists, the app serves local or cached answers built from the same database evidence.

Where Scripture and books come from

  • Full-text Bibles are ingested from public-domain sources — midvash bible-data, eBible USFM, JPS 1917, Brenton LXX, and the Ethiopian 81-book Ge'ez corpus — into versioned JSON and PostgreSQL schemas.
  • The catalog lists tradition, language, and license for every referenced translation; copyrighted modern versions stay catalog-only and are not loaded as study text.
  • Whole-book introductions and chapter guides are curated study content stored in the repository (`data/book_explanations.json`, `data/book_chapter_explanations.json`) and served with the Books face.

How content is verified

  • Verse text is always read from the database at request time — not paraphrased from model training data.
  • Shared Ask answers are stored only after citation verification against the evidence pack.
  • Chapter guides are checked for structure, uniqueness, and corpus grounding (`npm run guides:review`).
  • Corpus builds and migrations are versioned so operators can validate releases before publication.
Verse text and Ask answers come from public-domain Bible databases.