{
  "type": "blog_article",
  "schema_version": "blog_article_v2",
  "title": "The AIBC Bible Teaching Research Explorer",
  "slug": "the-aibc-bible-teaching-research-explorer",
  "description": "A research article introducing the AIBC Bible Teaching Research Explorer and its literary-unit method for studying the main teaching emphasis of Scripture.",
  "category": "study-tools",
  "category_label": "Study Tools",
  "canonical_url": "https://ai-bible-commentary.com/blog/the-aibc-bible-teaching-research-explorer/",
  "json_url": "https://ai-bible-commentary.com/data/blog/the-aibc-bible-teaching-research-explorer.json",
  "date_published": "2026-07-29",
  "date_modified": "2026-07-29",
  "author": "AI Bible Commentary",
  "language": "en-AU",
  "tags": [
    "Study Tools",
    "Literary Units",
    "Teaching Topic Frequency"
  ],
  "article_text": "The AIBC Bible Teaching Research Explorer\n\nA Research Tool for Studying the Main Teaching Emphasis of Every Literary Unit in the Bible\n\nOverview\n\nThe AIBC Bible Teaching Research Explorer is an interactive research platform built to investigate what the Bible teaches across its complete canonical structure.\n\nRather than beginning with isolated words, verses, or doctrinal proof texts, the Explorer begins with 2,072 literary units covering all 66 books of the Bible. Each unit represents a coherent passage: a narrative episode, law section, poem, prophecy, discourse, parable, argument, vision, genealogy, or other naturally bounded section of Scripture.\n\nFor every unit, the project identifies its principal teaching burden, records its major themes and teaching functions, places it within its literary and canonical setting, and connects every analytical result back to the exact passages that produced it.\n\nThe result is not merely a searchable Bible outline. It is a structured research environment for studying:\n\nwhat Scripture repeatedly teaches;\n\nhow different books and genres teach;\n\nwhat Scripture reveals about God;\n\nhow themes develop across the canon;\n\nhow commands, warnings, promises, judgments, mercy, worship, covenant, kingdom, Messiah, Spirit, Church, mission, resurrection, and restoration are distributed;\n\nhow Jesus and the apostles use earlier Scripture;\n\nand which exact literary units support any proposed conclusion.\n\nThe controlling research specification defines the Explorer as a static, browser-based application built on the complete 2,072-unit corpus. It is intended to measure literary-unit teaching emphasis, not raw word frequency, and to link every aggregate finding to the evidence that produced it.\n\nWhy Literary Units Matter\n\nA Bible verse rarely functions in isolation.\n\nMeaning is ordinarily communicated through larger literary movements: an argument, episode, oracle, lament, command section, dialogue, vision, or discourse. A single verse may contribute to the meaning of a passage without carrying the complete teaching burden of that passage.\n\nThe Explorer therefore asks a more responsible question than:\n\nWhich words occur most often?\n\nIt asks:\n\nWhat is this complete literary unit principally teaching?\n\nThat distinction is essential.\n\nA raw word-frequency tool can count how often a word appears, but it cannot by itself determine:\n\nwhether the word is central or incidental;\n\nwhether the text approves or condemns what it reports;\n\nwhether a command was given to Israel, the Church, a king, a priest, a disciple, or an individual;\n\nwhether a narrative event is descriptive or prescriptive;\n\nwhether a prophecy addresses its immediate audience, a later horizon, or both;\n\nwhether a theme is the main burden of the passage or merely background.\n\nThe Explorer studies teaching emphasis at the level where authors normally develop meaning: the literary unit.\n\nThis does not replace close reading. It provides a structured map that directs the researcher back to the passages themselves.\n\nThe Research Corpus\n\nThe project is built upon a canonical inventory of 2,072 literary units, extending from:\n\nOT_GEN_001, the first Genesis unit;\n\nthrough every Old and New Testament book;\n\nto NT_REV_040, the final Revelation unit.\n\nEach unit is identified by an immutable unitId. Canonical order, reference boundaries, book identity, genre, unit type, macro-section, route, and related metadata are controlled by a read-only literary-unit inventory.\n\nThe Explorer does not reconstruct canonical order from chart results, filenames, or array position. Every record is joined through the immutable unit identifier, and every accepted source record must correspond to exactly one inventory record.\n\nThis prevents a common analytical error: allowing the arrangement of a spreadsheet or JSON export to redefine biblical order.\n\nThe project architecture explicitly requires canonical order to come only from the controlling literary-unit inventory and treats missing, duplicate, extra, or conflicting identifiers as release-blocking errors.\n\nWhat Each Literary-Unit Record Contains\n\nThe foundational source record contains fifteen controlled fields:\n\nUnit identifier\n\nTestament\n\nBook\n\nPassage reference\n\nSource title\n\nTeaching title\n\nMain point\n\nSecondary point, when genuinely present\n\nPrinciple types\n\nTheme tags\n\nJesus and Apostles relevance\n\nNew Testament connections\n\nConfidence\n\nReview status\n\nReview note\n\nThe central field is the main point: one sentence stating the principal theological or ethical claim made by the complete unit.\n\nThis is not intended to be:\n\na sermon;\n\na devotional reflection;\n\na modern application;\n\na list of everything mentioned in the passage;\n\na plot summary without theological significance;\n\nor a miniature commentary.\n\nIt is a concise statement of what the inspired author is communicating through the passage in its literary, historical, covenantal, and canonical context.\n\nA secondary point is included only when the passage carries a genuinely distinct subordinate teaching burden. It is not added merely to fill a field.\n\nThe Interpretive Framework\n\nThe Explorer is not presented as theologically neutral.\n\nIts public methodology is grounded in a conservative evangelical framework that affirms:\n\nthe inspiration and authority of Scripture;\n\ngrammatical-historical interpretation;\n\nliterary and genre-sensitive reading;\n\nhistorical context;\n\ncovenantal context;\n\ncanonical development;\n\nthe distinction between what a text reports and what it approves;\n\nrestraint concerning unsupported allegory and typology;\n\nand the preservation of Israel, the Church, the nations, and the Gentiles as distinct categories.\n\nThe method also distinguishes:\n\ntextual observation;\n\ndeterministic metadata;\n\ncontrolled interpretive assignment;\n\ninference;\n\nand disputed interpretation.\n\nThis transparency matters because every act of classification involves interpretation. The responsible approach is not to pretend interpretation has disappeared, but to disclose the rules, preserve the evidence, expose uncertainty, and prevent hidden assumptions from controlling the results.\n\nThe Four-Layer Research Architecture\n\nThe Explorer was designed with four separate data layers.\n\nLayer A: Canonical Literary-Unit Inventory\n\nThis is the controlling structure of the 2,072 units.\n\nIt contains the boundaries, canonical order, references, genres, unit types, macro-sections, routes, and stable identifiers.\n\nThis layer is read-only.\n\nLayer B: Main-Point Research Source\n\nThis contains the accepted fifteen-field records.\n\nIts wording is preserved exactly. The application does not silently rewrite the source when creating charts, filters, or exports.\n\nLayer C: Analytical Enrichment\n\nNew analytical judgments are stored separately in versioned sidecars.\n\nThe first and most important enrichment is called the Analytical Bridge.\n\nLayer D: Generated Explorer Data\n\nThis includes:\n\njoined public records;\n\ncompact indexes;\n\nfilters;\n\naggregates;\n\nbook profiles;\n\ncompletion reports;\n\nsearch indexes;\n\nbuild manifests;\n\nexport packages;\n\nand static website files.\n\nLayer D is reproducible. It can be rebuilt from Layers A through C without changing the underlying research source.\n\nThis separation is one of the project’s most important integrity controls. It prevents later analytics from silently altering the original research records.\n\nThe Analytical Bridge\n\nThe source theme tags identify subjects present in a passage, but they do not necessarily show which subject is central.\n\nFor example, a unit may involve:\n\nGod;\n\ncovenant;\n\njudgment;\n\nIsrael;\n\nand repentance.\n\nAll five may be genuinely present, but they do not carry equal weight.\n\nThe Analytical Bridge classifies each accepted theme as:\n\nPrimary: indispensable to the central teaching burden;\n\nSecondary: a distinct subordinate burden;\n\nSupporting: genuinely involved but not central.\n\nThe Bridge also adds a limited set of high-value analytical fields:\n\ncommunicative intent;\n\nevaluative stance;\n\ndominant voice;\n\noriginal audience;\n\nsalvation-history stage;\n\nstructured divine disclosure;\n\nconfidence;\n\nreview flags;\n\nprovenance;\n\nand review status.\n\nAll 2,072 Bridge records have been Cross-reviewed, and the publication-review sidecar records all 2,072 source units as reviewed for public research release, with no held records and no unresolved publication issues. The immutable historical source fields remain preserved for provenance rather than being overwritten.\n\nCommunicative Intent\n\nCommunicative intent asks:\n\nWhat is the passage doing?\n\nControlled values include:\n\nreveal;\n\ncommand;\n\nwarn;\n\npromise;\n\nexpose;\n\nrebuke;\n\ncomfort;\n\ninvite;\n\nassure;\n\nlament;\n\nintercede;\n\npraise;\n\nexplain;\n\ntestify;\n\npredict;\n\nannounce fulfilment.\n\nThis permits research that goes beyond topics.\n\nA user can study not merely where “judgment” appears, but:\n\nwhich passages warn;\n\nwhat those warnings concern;\n\nwho gives them;\n\nto whom they are addressed;\n\nand what outcomes they announce.\n\nEvaluative Stance\n\nEvaluative stance asks:\n\nHow does the passage evaluate the conduct, claim, command, promise, or event it represents?\n\nThe controlled categories include:\n\ncommanded;\n\ncommended;\n\npermitted;\n\ntolerated;\n\nreported without approval;\n\nprohibited;\n\ncondemned;\n\nwarned;\n\npromised;\n\nfulfilled;\n\nquestioned;\n\ndisputed or unclear.\n\nThis is particularly important in biblical narrative.\n\nThe Bible often records:\n\nviolence;\n\ndeception;\n\nunbelief;\n\npolygamy;\n\nidolatry;\n\npolitical intrigue;\n\ncowardice;\n\nand human failure.\n\nRecording an action does not mean approving it.\n\nThe Explorer therefore refuses to convert narrative description automatically into moral example.\n\nDominant Voice and Audience\n\nThe Explorer distinguishes:\n\nGod;\n\nJesus;\n\nthe Holy Spirit;\n\nnarrator;\n\nprophet;\n\napostle;\n\npsalmist;\n\nwisdom speaker;\n\ncovenant mediator;\n\nking or leader;\n\nangelic messenger;\n\nhuman character;\n\ncorporate community;\n\nand mixed voice.\n\nIt also distinguishes original audiences such as:\n\nhumanity;\n\nIsrael;\n\nJudah;\n\ncovenant community;\n\npriests and Levites;\n\nkings and rulers;\n\nnations;\n\nGentiles;\n\ndisciples;\n\ncrowds;\n\nopponents;\n\nunbelievers;\n\nlocal churches;\n\nchurches generally;\n\nchurch leaders;\n\nindividuals;\n\nand persecuted believers.\n\nThese distinctions help prevent audience flattening.\n\nA command given to Levitical priests is not automatically presented as a direct command to the Church. A prophetic word to Judah is not relabelled as though its original audience were a modern congregation. Original audience, canonical relevance, and present application remain related but distinct questions.\n\nSalvation-History Stage\n\nEach unit can be studied within a broad salvation-history stage:\n\ncreation;\n\nfall and primeval judgment;\n\npatriarchal promise;\n\nexodus and Sinai;\n\nland and judges;\n\nmonarchy and temple;\n\ndivided kingdom and prophetic warning;\n\nexile;\n\nrestoration and expectation;\n\nChrist’s ministry, death, and resurrection;\n\napostolic mission and Church;\n\nconsummation and new creation.\n\nThese stages make it possible to study broad canonical development without pretending that canonical order is identical to historical chronology.\n\nWhat the Explorer Does\n\nThe Explorer places the complete research corpus inside one interactive filtered-record environment.\n\nA user can filter by combinations of:\n\nTestament;\n\nbook group;\n\nbook;\n\ncanonical range;\n\ngenre;\n\nunit type;\n\nmacro-section;\n\ntheme;\n\ntheme family;\n\nPrimary, Secondary, or Supporting role;\n\nprinciple type;\n\ncommunicative intent;\n\nevaluative stance;\n\ndominant voice;\n\noriginal audience;\n\nsalvation-history stage;\n\nJesus and Apostles relevance;\n\nconfidence;\n\nreview state;\n\nexact text;\n\nand semantic discovery.\n\nThe same filtered set is then used across charts, comparisons, statistics, evidence tables, and exports.\n\nThis is a critical engineering decision.\n\nThe Explorer does not allow each chart to invent its own hidden method of choosing records. A central filtered-record model determines the eligible unit IDs, and every analytical result must resolve back to those IDs.\n\nEvery Statistic Has Evidence\n\nA chart is not treated as an endpoint.\n\nEvery:\n\nbar;\n\ncount;\n\npercentage;\n\nheatmap cell;\n\ncomparison;\n\nco-occurrence value;\n\ntheme distribution;\n\nprogression mark;\n\nand generated finding\n\nmust drill down to the exact literary units that produced it.\n\nThe evidence view can show:\n\nunit identifier;\n\npassage reference;\n\nsource title;\n\nteaching title;\n\nmain point;\n\nsecondary point;\n\ntheme assignments;\n\ncommunicative intent;\n\nevaluative stance;\n\naudience;\n\nvoice;\n\nsalvation-history stage;\n\ndivine disclosure;\n\nconfidence;\n\nreview state;\n\nand provenance.\n\nThe methodological specification requires every chart or statistic to retain access to the exact unit, reference, teaching statements, theme role, evidence, confidence, and review state.\n\nThis makes the research auditable.\n\nThe user does not have to trust a colored bar. The user can inspect the passages behind it.\n\nWhat the Tool Can Tell Us\n\nThe Explorer is designed to answer several major families of questions.\n\n1. What Scripture Emphasizes\n\nIt can show:\n\nwhich themes occur across the greatest number of literary units;\n\nwhich themes are most often Primary;\n\nwhich themes are broadly dispersed across many books;\n\nwhich are concentrated in particular books or genres;\n\nand how results change when Supporting themes are excluded.\n\nThis is more precise than simply counting mentions.\n\n2. How Books Differ\n\nThe Explorer can compare one book with:\n\nanother book;\n\na book group;\n\na Testament;\n\nor the whole corpus.\n\nIt can ask:\n\nWhich themes are unusually concentrated in Deuteronomy?\n\nHow does Hebrews differ from Romans?\n\nWhat teaching functions characterize Proverbs?\n\nWhich audiences dominate the Pastoral Epistles?\n\nHow does prophetic warning differ from apostolic warning?\n\nWhat distinguishes the Gospel of John from the Synoptic Gospels?\n\nDistinctiveness does not mean greater importance. It means unusual concentration relative to a stated baseline.\n\n3. What Scripture Reveals About God\n\nThe structured divine-disclosure layer allows research into:\n\ndivine actions;\n\nattributes;\n\nroles;\n\npurposes;\n\nrequired human responses;\n\nand resulting outcomes.\n\nThis enables questions such as:\n\nWhere is God presented as Creator, King, Judge, Shepherd, Father, or Redeemer?\n\nIn which units does God command, promise, deliver, judge, restore, sanctify, dwell, send, or reign?\n\nWhat responses are required: faith, obedience, repentance, worship, perseverance, humility, justice, or mission?\n\nWhat outcomes follow: blessing, fellowship, forgiveness, judgment, restoration, resurrection, kingdom, or divine presence?\n\nThe Explorer does not reduce the doctrine of God to a single “God” tag. It uses structured claims that remain connected to the accepted main point of each unit.\n\n4. How Scripture Teaches\n\nThe tool can distinguish between:\n\ncommands;\n\nwarnings;\n\npromises;\n\nrebukes;\n\nexplanations;\n\npraise;\n\nlament;\n\ntestimony;\n\npredictions;\n\nfulfilment announcements;\n\ninvitations;\n\nand assurances.\n\nThis permits more exact questions:\n\nWhat do biblical warnings warn about?\n\nWhat grounds are given for commands?\n\nWhat promises are conditional?\n\nHow does mercy relate to repentance?\n\nHow does judgment relate to covenant rebellion?\n\nHow does discipleship relate to obedience, suffering, perseverance, and mission?\n\n5. Canonical Development\n\nThe Explorer can trace the distribution of themes across canonical order and broad salvation-history stages.\n\nResearchers can examine the development of:\n\ncovenant;\n\nkingdom;\n\nsacrifice;\n\npriesthood;\n\ntemple;\n\nMessiah;\n\nSpirit;\n\nGospel;\n\nChurch;\n\nmission;\n\nresurrection;\n\njudgment;\n\nrestoration;\n\nand new creation.\n\nThe tool can reveal concentration, recurrence, continuity, and later development.\n\nHowever, it does not treat canonical movement as proof of exact historical chronology.\n\n6. Jesus and the Apostles\n\nThe Explorer distinguishes among:\n\ndirect New Testament use;\n\nstrong New Testament use;\n\ncanonical background;\n\nand no explicit use established.\n\nIt supports research into:\n\nOld Testament passages quoted by Jesus or the apostles;\n\npassages used doctrinally;\n\nfulfilment claims;\n\ntypological development;\n\nallusion;\n\ncontrast;\n\nand background.\n\nIt also permits comparison of:\n\nJesus’ teaching to disciples;\n\nJesus’ teaching to crowds;\n\nconfrontation with religious opponents;\n\napostolic preaching to unbelievers;\n\ninstruction to churches;\n\nleadership instruction;\n\nand warning passages.\n\n7. Theme Relationships\n\nThe Explorer can calculate:\n\nraw co-occurrence;\n\nJaccard similarity;\n\nlift;\n\nmarginal counts;\n\nand intersection counts.\n\nThis can show, for example, whether two themes appear together more often than expected within a selected scope.\n\nBut it does not claim that co-occurrence proves:\n\ncausation;\n\nequivalence;\n\nfulfilment;\n\ntheological dependence;\n\nor chronological progression.\n\nAssociation is a clue for further study, not a substitute for exegesis.\n\nHow the Research Was Produced\n\nThe source-production process followed small, recoverable batches.\n\nFor each batch:\n\nThe exact unit range was fixed.\n\nInventory metadata was copied rather than retyped.\n\nDraft records were generated under the controlling research prompt.\n\nSyntax and schema were validated.\n\nUnit IDs and ordering were checked.\n\nControlled vocabulary was checked.\n\nMain and secondary points were reviewed against the passage unit.\n\nDifficult records were held or corrected.\n\nCheckpoints were exported.\n\nProvenance, hashes, protocol versions, and record counts were preserved.\n\nThe project did not rely on chat history or browser history as the production record. Accepted checkpoints were saved as operational artifacts.\n\nThe Role of AI\n\nAI assisted in structured extraction, classification, comparison, correction, code generation, and validation.\n\nBut AI output was never treated as self-authenticating.\n\nThe project protocols required that model output be treated as Draft research until it passed:\n\nschema validation;\n\ncontrolled-value validation;\n\nsource reconciliation;\n\ncontextual review;\n\ncross-review;\n\ncorrection procedures;\n\nand release QA.\n\nAI was used as a controlled research instrument, not as a doctrinal authority.\n\nThe authoritative standard remains the biblical text interpreted according to the declared methodology.\n\nQuality Assurance and Integrity Controls\n\nThe project incorporated QA at multiple levels.\n\nSource Integrity\n\nChecks included:\n\nexactly 2,072 records;\n\nno duplicate unit IDs;\n\nno missing unit IDs;\n\nno extra unit IDs;\n\ncorrect Testament and book;\n\ncorrect references;\n\ncorrect source titles;\n\ncorrect canonical order;\n\nand exact joining to the inventory.\n\nSchema Validation\n\nThe Analytical Bridge was validated against a controlled JSON Schema.\n\nChecks included:\n\nrequired fields;\n\npermitted values;\n\nlist limits;\n\nsummary-length limits;\n\nsource-theme membership;\n\nPrimary and Secondary theme restrictions;\n\nreview states;\n\nconfidence;\n\nprovenance;\n\nand internal consistency.\n\nControlled Vocabulary\n\nThe project used a frozen taxonomy.\n\nUnapproved:\n\nthemes;\n\nintents;\n\nstances;\n\ndivine actions;\n\noutcomes;\n\naudiences;\n\nvoices;\n\nand stages\n\nwere rejected or corrected through explicit versioned procedures.\n\nTheological and Editorial Review\n\nReview asked:\n\nDoes the main point account for the whole unit?\n\nIs it a claim rather than merely a topic?\n\nDoes it preserve the original audience?\n\nDoes it distinguish report from approval?\n\nDoes it respect genre?\n\nDoes it avoid moralizing narrative?\n\nDoes it avoid unsupported allegory?\n\nAre tags materially supported?\n\nIs Jesus and Apostles relevance no stronger than the evidence?\n\nDoes confidence match interpretive difficulty?\n\nIs uncertainty visible?\n\nCross-Review\n\nAll 2,072 Analytical Bridge records reached Cross-reviewed status.\n\nMedium-confidence, low-confidence, ambiguous, difficult, and flagged records received special attention, alongside stratified samples of uncomplicated High-confidence records.\n\nPublication Review\n\nA separate publication-review sidecar records all 2,072 source units as Reviewed for public research use, with no held records and no unresolved publication issues. The historical source file remains immutable so that the original workflow state is preserved rather than rewritten.\n\nReproducible Builds\n\nThe release process included:\n\nlocked dependency installation;\n\nlinting;\n\nautomated tests;\n\nproduction compilation;\n\nstatic export;\n\nrequired-file tests;\n\nlocal HTTP tests;\n\nportable checksum generation;\n\nonline build;\n\nstrict offline cache-seeded build;\n\nand byte-for-byte comparison.\n\nThis was designed to establish not only that the interface worked once, but that it could be rebuilt reproducibly.\n\nDeployment-Specific Testing\n\nThe application was also tested for its actual deployment path rather than only at a domain root.\n\nIts release controls verify that scripts, CSS, data files, logo assets, and runtime fetches resolve under the configured Explorer directory and do not accidentally request unrelated root-level files.\n\nStatistical Safeguards\n\nThe Explorer reports descriptive measurements such as:\n\nunit count;\n\nunit coverage;\n\nPrimary-theme coverage;\n\npercentage-point difference;\n\nrelative emphasis;\n\nco-occurrence;\n\nJaccard similarity;\n\nlift;\n\ncanonical dispersion;\n\nand book concentration.\n\nEvery display should reveal:\n\nnumerator;\n\ndenominator;\n\nselected scope;\n\ncounting mode;\n\ntheme-role mode;\n\nconfidence filter;\n\nreview filter;\n\nand limitations.\n\nSmall samples are marked rather than hidden.\n\nLong literary units are not allowed to silently dominate the default results.\n\nThe Explorer also refuses several invalid conclusions.\n\nIt does not claim:\n\nthat frequency proves divine importance;\n\nthat absence of a tag proves absence of a concept;\n\nthat summary-word frequency equals biblical-word frequency;\n\nthat co-occurrence proves causation;\n\nthat canonical order establishes exact event chronology;\n\nthat all Old Testament commands apply directly to the Church;\n\nor that every canonical background relationship is a direct quotation.\n\nWhat the Explorer Is Not\n\nThe AIBC Bible Teaching Research Explorer is not:\n\nan automated doctrinal authority;\n\na substitute for reading Scripture;\n\na raw concordance;\n\na word-counting engine;\n\na system for proving theology by popularity;\n\na claim of interpretive neutrality;\n\nor a replacement for detailed exegesis.\n\nIt is a research map.\n\nIt helps the researcher identify patterns, compare bodies of teaching, retrieve evidence, expose assumptions, and return to the passages that generated the result.\n\nWho the Explorer Is For\n\nThe tool is designed for:\n\npastors;\n\nBible teachers;\n\ntheological students;\n\nresearchers;\n\nsmall-group leaders;\n\nChristian writers;\n\nmissionaries;\n\nchurch leaders;\n\nand serious Bible readers.\n\nIt can support:\n\nsermon preparation;\n\nthematic study;\n\nbook comparison;\n\nbiblical-theological research;\n\nreading-plan creation;\n\ncurriculum planning;\n\nevidence collection;\n\ndoctrinal investigation;\n\nand personal study.\n\nA teacher researching perseverance can identify relevant units, compare how the theme functions in the Gospels and Epistles, examine warnings and promises, inspect audiences and outcomes, and export the contributing passages.\n\nA researcher studying the kingdom can trace its concentration across the canon, compare kingdom and Messiah, examine divine kingship, distinguish Israel’s historical monarchy from messianic fulfilment, and inspect each contributing unit.\n\nA student studying divine judgment can distinguish condemnation, warning, discipline, fulfilment, and reported human judgment instead of treating every appearance as the same category.\n\nWhat Makes the Explorer Distinctive\n\nThe project combines four commitments that are rarely brought together.\n\n1. Whole-Bible Coverage\n\nIt works from a complete 2,072-unit canonical inventory rather than a small thematic sample.\n\n2. Contextual Interpretation\n\nIt measures the teaching burden of literary units rather than isolated words.\n\n3. Analytical Structure\n\nIt converts carefully reviewed interpretations into fields that can be filtered, compared, measured, and exported.\n\n4. Evidence Accountability\n\nEvery result can be traced back to the passages that produced it.\n\nThis combination makes the Explorer more than a Bible search interface and more than a collection of charts.\n\nIt is a structured, evidence-linked environment for studying what Scripture teaches, how it teaches, to whom it speaks, how its themes develop, and what it reveals about God across the canon.\n\nConclusion\n\nThe AIBC Bible Teaching Research Explorer was built to answer a demanding question:\n\nWhat becomes visible when every major literary unit of Scripture is studied, classified, reviewed, connected, and made available for evidence-linked analysis?\n\nThe result is a tool that allows readers to investigate the Bible at several levels simultaneously:\n\npassage;\n\nbook;\n\ngenre;\n\naudience;\n\ncovenant;\n\nteaching function;\n\ncanonical stage;\n\ntheme;\n\ndivine action;\n\nand whole-Bible pattern.\n\nIts value does not lie merely in producing more charts.\n\nIts value lies in making broad claims answerable to exact passages.\n\nThe Explorer helps users move from:\n\n“The Bible seems to emphasize this”\n\nto:\n\n“These are the exact literary units, within this declared scope and method, that produced the measured pattern.”\n\nThat is the central purpose of the project: evidence before impression, context before slogans, and Scripture before statistical overstatement.",
  "internal_links": [
    {
      "url": "https://ai-bible-commentary.com/main-point-bible-literary-units/",
      "anchor": "Bible Teaching Research Explorer"
    },
    {
      "url": "https://ai-bible-commentary.com/studies/",
      "anchor": "Bible Studies with Strictly Controlled AI"
    },
    {
      "url": "https://ai-bible-commentary.com/all-in-one-bible-study-tool/",
      "anchor": "All-In-One Bible Study Tool"
    },
    {
      "url": "https://ai-bible-commentary.com/pages/warnings-of-using-ai/",
      "anchor": "Warnings About Using AI"
    },
    {
      "url": "https://ai-bible-commentary.com/prompts-library/index.html",
      "anchor": "AI Bible Study Prompts"
    }
  ],
  "fact_checks": []
}