Anchor on a passage
Passage owns the reading flow: translation, selection, notes, references, language, maps, and source-aware tools stay beside the text.
Scripture-first workspace
BibleBot starts with scripture, keeps source boundaries visible, and connects reading, guided studies, dictionary/source views, maps, references, language, and drafting without turning source material into mystery prose.
Product model
Passage owns the reading flow: translation, selection, notes, references, language, maps, and source-aware tools stay beside the text.
Studies provide guided depth, while Workbench lets a word, source, place, map, topic, reference, or question start the research path.
Composer gathers scripture, notes, source rows, map context, study steps, and Q&A into a draft without pretending gathered material is already finished writing.
Now in the workspace
Main surfaces
Source posture
BibleBot distinguishes active runtime sources from candidate research. Structured data can support tools, but source prose, commentary-like claims, provider terms, managed media, and ShareAlike obligations stay explicit.
WEB/KJV where configured, licensed translation providers, Tyndale and Aquifer Dictionary views, Easton, Smith, ISBE, Nave, MACULA, STEPBible-style fields, OpenBible references, curated places, journeys, and approved managed maps.
Approved Tyndale Dictionary maps/charts and Biblica/Aquifer map images use BibleBot-managed routes, visible attribution, and surface-specific display rules.
BibleAquifer ACAI, Theographic, SemanticBible / Sean Boisen metadata, OpenText, Clear Bible quotation data, UBS resources, BibleData/DaRe, pictures, and richer media exploration wait for review and source-role approval.