The AIBC Bible Teaching Research Explorer

Overview

The AIBC Bible Teaching Research Explorer is an interactive research platform built to investigate what the Bible teaches across its complete canonical structure.

Rather 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.

For 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.

The result is not merely a searchable Bible outline. It is a structured research environment for studying:

what Scripture repeatedly teaches;

how different books and genres teach;

what Scripture reveals about God;

how themes develop across the canon;

how commands, warnings, promises, judgments, mercy, worship, covenant, kingdom, Messiah, Spirit, Church, mission, resurrection, and restoration are distributed;

how Jesus and the apostles use earlier Scripture;

and which exact literary units support any proposed conclusion.

The 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.

Why Literary Units Matter

A Bible verse rarely functions in isolation.

Meaning 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.

The Explorer therefore asks a more responsible question than:

Which words occur most often?

It asks:

What is this complete literary unit principally teaching?

That distinction is essential.

A raw word-frequency tool can count how often a word appears, but it cannot by itself determine:

whether the word is central or incidental;

whether the text approves or condemns what it reports;

whether a command was given to Israel, the Church, a king, a priest, a disciple, or an individual;

whether a narrative event is descriptive or prescriptive;

whether a prophecy addresses its immediate audience, a later horizon, or both;

whether a theme is the main burden of the passage or merely background.

The Explorer studies teaching emphasis at the level where authors normally develop meaning: the literary unit.

This does not replace close reading. It provides a structured map that directs the researcher back to the passages themselves.

The Research Corpus

The project is built upon a canonical inventory of 2,072 literary units, extending from:

OT_GEN_001, the first Genesis unit;

through every Old and New Testament book;

to NT_REV_040, the final Revelation unit.

Each 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.

The 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.

This prevents a common analytical error: allowing the arrangement of a spreadsheet or JSON export to redefine biblical order.

The 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.

What Each Literary-Unit Record Contains

The foundational source record contains fifteen controlled fields:

Unit identifier

Testament

Book

Passage reference

Source title

Teaching title

Main point

Secondary point, when genuinely present

Principle types

Theme tags

Jesus and Apostles relevance

New Testament connections

Confidence

Review status

Review note

The central field is the main point: one sentence stating the principal theological or ethical claim made by the complete unit.

This is not intended to be:

a sermon;

a devotional reflection;

a modern application;

a list of everything mentioned in the passage;

a plot summary without theological significance;

or a miniature commentary.

It is a concise statement of what the inspired author is communicating through the passage in its literary, historical, covenantal, and canonical context.

A secondary point is included only when the passage carries a genuinely distinct subordinate teaching burden. It is not added merely to fill a field.

The Interpretive Framework

The Explorer is not presented as theologically neutral.

Its public methodology is grounded in a conservative evangelical framework that affirms:

the inspiration and authority of Scripture;

grammatical-historical interpretation;

literary and genre-sensitive reading;

historical context;

covenantal context;

canonical development;

the distinction between what a text reports and what it approves;

restraint concerning unsupported allegory and typology;

and the preservation of Israel, the Church, the nations, and the Gentiles as distinct categories.

The method also distinguishes:

textual observation;

deterministic metadata;

controlled interpretive assignment;

inference;

and disputed interpretation.

This 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.

The Four-Layer Research Architecture

The Explorer was designed with four separate data layers.

Layer A: Canonical Literary-Unit Inventory

This is the controlling structure of the 2,072 units.

It contains the boundaries, canonical order, references, genres, unit types, macro-sections, routes, and stable identifiers.

This layer is read-only.

Layer B: Main-Point Research Source

This contains the accepted fifteen-field records.

Its wording is preserved exactly. The application does not silently rewrite the source when creating charts, filters, or exports.

Layer C: Analytical Enrichment

New analytical judgments are stored separately in versioned sidecars.

The first and most important enrichment is called the Analytical Bridge.

Layer D: Generated Explorer Data

This includes:

joined public records;

compact indexes;

filters;

aggregates;

book profiles;

completion reports;

search indexes;

build manifests;

export packages;

and static website files.

Layer D is reproducible. It can be rebuilt from Layers A through C without changing the underlying research source.

This separation is one of the project’s most important integrity controls. It prevents later analytics from silently altering the original research records.

The Analytical Bridge

The source theme tags identify subjects present in a passage, but they do not necessarily show which subject is central.

For example, a unit may involve:

God;

covenant;

judgment;

Israel;

and repentance.

All five may be genuinely present, but they do not carry equal weight.

The Analytical Bridge classifies each accepted theme as:

Primary: indispensable to the central teaching burden;

Secondary: a distinct subordinate burden;

Supporting: genuinely involved but not central.

The Bridge also adds a limited set of high-value analytical fields:

communicative intent;

evaluative stance;

dominant voice;

original audience;

salvation-history stage;

structured divine disclosure;

confidence;

review flags;

provenance;

and review status.

All 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.

Communicative Intent

Communicative intent asks:

What is the passage doing?

Controlled values include:

reveal;

command;

warn;

promise;

expose;

rebuke;

comfort;

invite;

assure;

lament;

intercede;

praise;

explain;

testify;

predict;

announce fulfilment.

This permits research that goes beyond topics.

A user can study not merely where “judgment” appears, but:

which passages warn;

what those warnings concern;

who gives them;

to whom they are addressed;

and what outcomes they announce.

Evaluative Stance

Evaluative stance asks:

How does the passage evaluate the conduct, claim, command, promise, or event it represents?

The controlled categories include:

commanded;

commended;

permitted;

tolerated;

reported without approval;

prohibited;

condemned;

warned;

promised;

fulfilled;

questioned;

disputed or unclear.

This is particularly important in biblical narrative.

The Bible often records:

violence;

deception;

unbelief;

polygamy;

idolatry;

political intrigue;

cowardice;

and human failure.

Recording an action does not mean approving it.

The Explorer therefore refuses to convert narrative description automatically into moral example.

Dominant Voice and Audience

The Explorer distinguishes:

God;

Jesus;

the Holy Spirit;

narrator;

prophet;

apostle;

psalmist;

wisdom speaker;

covenant mediator;

king or leader;

angelic messenger;

human character;

corporate community;

and mixed voice.

It also distinguishes original audiences such as:

humanity;

Israel;

Judah;

covenant community;

priests and Levites;

kings and rulers;

nations;

Gentiles;

disciples;

crowds;

opponents;

unbelievers;

local churches;

churches generally;

church leaders;

individuals;

and persecuted believers.

These distinctions help prevent audience flattening.

A 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.

Salvation-History Stage

Each unit can be studied within a broad salvation-history stage:

creation;

fall and primeval judgment;

patriarchal promise;

exodus and Sinai;

land and judges;

monarchy and temple;

divided kingdom and prophetic warning;

exile;

restoration and expectation;

Christ’s ministry, death, and resurrection;

apostolic mission and Church;

consummation and new creation.

These stages make it possible to study broad canonical development without pretending that canonical order is identical to historical chronology.

What the Explorer Does

The Explorer places the complete research corpus inside one interactive filtered-record environment.

A user can filter by combinations of:

Testament;

book group;

book;

canonical range;

genre;

unit type;

macro-section;

theme;

theme family;

Primary, Secondary, or Supporting role;

principle type;

communicative intent;

evaluative stance;

dominant voice;

original audience;

salvation-history stage;

Jesus and Apostles relevance;

confidence;

review state;

exact text;

and semantic discovery.

The same filtered set is then used across charts, comparisons, statistics, evidence tables, and exports.

This is a critical engineering decision.

The 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.

Every Statistic Has Evidence

A chart is not treated as an endpoint.

Every:

bar;

count;

percentage;

heatmap cell;

comparison;

co-occurrence value;

theme distribution;

progression mark;

and generated finding

must drill down to the exact literary units that produced it.

The evidence view can show:

unit identifier;

passage reference;

source title;

teaching title;

main point;

secondary point;

theme assignments;

communicative intent;

evaluative stance;

audience;

voice;

salvation-history stage;

divine disclosure;

confidence;

review state;

and provenance.

The methodological specification requires every chart or statistic to retain access to the exact unit, reference, teaching statements, theme role, evidence, confidence, and review state.

This makes the research auditable.

The user does not have to trust a colored bar. The user can inspect the passages behind it.

What the Tool Can Tell Us

The Explorer is designed to answer several major families of questions.

1. What Scripture Emphasizes

It can show:

which themes occur across the greatest number of literary units;

which themes are most often Primary;

which themes are broadly dispersed across many books;

which are concentrated in particular books or genres;

and how results change when Supporting themes are excluded.

This is more precise than simply counting mentions.

2. How Books Differ

The Explorer can compare one book with:

another book;

a book group;

a Testament;

or the whole corpus.

It can ask:

Which themes are unusually concentrated in Deuteronomy?

How does Hebrews differ from Romans?

What teaching functions characterize Proverbs?

Which audiences dominate the Pastoral Epistles?

How does prophetic warning differ from apostolic warning?

What distinguishes the Gospel of John from the Synoptic Gospels?

Distinctiveness does not mean greater importance. It means unusual concentration relative to a stated baseline.

3. What Scripture Reveals About God

The structured divine-disclosure layer allows research into:

divine actions;

attributes;

roles;

purposes;

required human responses;

and resulting outcomes.

This enables questions such as:

Where is God presented as Creator, King, Judge, Shepherd, Father, or Redeemer?

In which units does God command, promise, deliver, judge, restore, sanctify, dwell, send, or reign?

What responses are required: faith, obedience, repentance, worship, perseverance, humility, justice, or mission?

What outcomes follow: blessing, fellowship, forgiveness, judgment, restoration, resurrection, kingdom, or divine presence?

The 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.

4. How Scripture Teaches

The tool can distinguish between:

commands;

warnings;

promises;

rebukes;

explanations;

praise;

lament;

testimony;

predictions;

fulfilment announcements;

invitations;

and assurances.

This permits more exact questions:

What do biblical warnings warn about?

What grounds are given for commands?

What promises are conditional?

How does mercy relate to repentance?

How does judgment relate to covenant rebellion?

How does discipleship relate to obedience, suffering, perseverance, and mission?

5. Canonical Development

The Explorer can trace the distribution of themes across canonical order and broad salvation-history stages.

Researchers can examine the development of:

covenant;

kingdom;

sacrifice;

priesthood;

temple;

Messiah;

Spirit;

Gospel;

Church;

mission;

resurrection;

judgment;

restoration;

and new creation.

The tool can reveal concentration, recurrence, continuity, and later development.

However, it does not treat canonical movement as proof of exact historical chronology.

6. Jesus and the Apostles

The Explorer distinguishes among:

direct New Testament use;

strong New Testament use;

canonical background;

and no explicit use established.

It supports research into:

Old Testament passages quoted by Jesus or the apostles;

passages used doctrinally;

fulfilment claims;

typological development;

allusion;

contrast;

and background.

It also permits comparison of:

Jesus’ teaching to disciples;

Jesus’ teaching to crowds;

confrontation with religious opponents;

apostolic preaching to unbelievers;

instruction to churches;

leadership instruction;

and warning passages.

7. Theme Relationships

The Explorer can calculate:

raw co-occurrence;

Jaccard similarity;

lift;

marginal counts;

and intersection counts.

This can show, for example, whether two themes appear together more often than expected within a selected scope.

But it does not claim that co-occurrence proves:

causation;

equivalence;

fulfilment;

theological dependence;

or chronological progression.

Association is a clue for further study, not a substitute for exegesis.

How the Research Was Produced

The source-production process followed small, recoverable batches.

For each batch:

The exact unit range was fixed.

Inventory metadata was copied rather than retyped.

Draft records were generated under the controlling research prompt.

Syntax and schema were validated.

Unit IDs and ordering were checked.

Controlled vocabulary was checked.

Main and secondary points were reviewed against the passage unit.

Difficult records were held or corrected.

Checkpoints were exported.

Provenance, hashes, protocol versions, and record counts were preserved.

The project did not rely on chat history or browser history as the production record. Accepted checkpoints were saved as operational artifacts.

The Role of AI

AI assisted in structured extraction, classification, comparison, correction, code generation, and validation.

But AI output was never treated as self-authenticating.

The project protocols required that model output be treated as Draft research until it passed:

schema validation;

controlled-value validation;

source reconciliation;

contextual review;

cross-review;

correction procedures;

and release QA.

AI was used as a controlled research instrument, not as a doctrinal authority.

The authoritative standard remains the biblical text interpreted according to the declared methodology.

Quality Assurance and Integrity Controls

The project incorporated QA at multiple levels.

Source Integrity

Checks included:

exactly 2,072 records;

no duplicate unit IDs;

no missing unit IDs;

no extra unit IDs;

correct Testament and book;

correct references;

correct source titles;

correct canonical order;

and exact joining to the inventory.

Schema Validation

The Analytical Bridge was validated against a controlled JSON Schema.

Checks included:

required fields;

permitted values;

list limits;

summary-length limits;

source-theme membership;

Primary and Secondary theme restrictions;

review states;

confidence;

provenance;

and internal consistency.

Controlled Vocabulary

The project used a frozen taxonomy.

Unapproved:

themes;

intents;

stances;

divine actions;

outcomes;

audiences;

voices;

and stages

were rejected or corrected through explicit versioned procedures.

Theological and Editorial Review

Review asked:

Does the main point account for the whole unit?

Is it a claim rather than merely a topic?

Does it preserve the original audience?

Does it distinguish report from approval?

Does it respect genre?

Does it avoid moralizing narrative?

Does it avoid unsupported allegory?

Are tags materially supported?

Is Jesus and Apostles relevance no stronger than the evidence?

Does confidence match interpretive difficulty?

Is uncertainty visible?

Cross-Review

All 2,072 Analytical Bridge records reached Cross-reviewed status.

Medium-confidence, low-confidence, ambiguous, difficult, and flagged records received special attention, alongside stratified samples of uncomplicated High-confidence records.

Publication Review

A 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.

Reproducible Builds

The release process included:

locked dependency installation;

linting;

automated tests;

production compilation;

static export;

required-file tests;

local HTTP tests;

portable checksum generation;

online build;

strict offline cache-seeded build;

and byte-for-byte comparison.

This was designed to establish not only that the interface worked once, but that it could be rebuilt reproducibly.

Deployment-Specific Testing

The application was also tested for its actual deployment path rather than only at a domain root.

Its 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.

Statistical Safeguards

The Explorer reports descriptive measurements such as:

unit count;

unit coverage;

Primary-theme coverage;

percentage-point difference;

relative emphasis;

co-occurrence;

Jaccard similarity;

lift;

canonical dispersion;

and book concentration.

Every display should reveal:

numerator;

denominator;

selected scope;

counting mode;

theme-role mode;

confidence filter;

review filter;

and limitations.

Small samples are marked rather than hidden.

Long literary units are not allowed to silently dominate the default results.

The Explorer also refuses several invalid conclusions.

It does not claim:

that frequency proves divine importance;

that absence of a tag proves absence of a concept;

that summary-word frequency equals biblical-word frequency;

that co-occurrence proves causation;

that canonical order establishes exact event chronology;

that all Old Testament commands apply directly to the Church;

or that every canonical background relationship is a direct quotation.

What the Explorer Is Not

The AIBC Bible Teaching Research Explorer is not:

an automated doctrinal authority;

a substitute for reading Scripture;

a raw concordance;

a word-counting engine;

a system for proving theology by popularity;

a claim of interpretive neutrality;

or a replacement for detailed exegesis.

It is a research map.

It helps the researcher identify patterns, compare bodies of teaching, retrieve evidence, expose assumptions, and return to the passages that generated the result.

Who the Explorer Is For

The tool is designed for:

pastors;

Bible teachers;

theological students;

researchers;

small-group leaders;

Christian writers;

missionaries;

church leaders;

and serious Bible readers.

It can support:

sermon preparation;

thematic study;

book comparison;

biblical-theological research;

reading-plan creation;

curriculum planning;

evidence collection;

doctrinal investigation;

and personal study.

A 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.

A 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.

A student studying divine judgment can distinguish condemnation, warning, discipline, fulfilment, and reported human judgment instead of treating every appearance as the same category.

What Makes the Explorer Distinctive

The project combines four commitments that are rarely brought together.

1. Whole-Bible Coverage

It works from a complete 2,072-unit canonical inventory rather than a small thematic sample.

2. Contextual Interpretation

It measures the teaching burden of literary units rather than isolated words.

3. Analytical Structure

It converts carefully reviewed interpretations into fields that can be filtered, compared, measured, and exported.

4. Evidence Accountability

Every result can be traced back to the passages that produced it.

This combination makes the Explorer more than a Bible search interface and more than a collection of charts.

It 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.

Conclusion

The AIBC Bible Teaching Research Explorer was built to answer a demanding question:

What becomes visible when every major literary unit of Scripture is studied, classified, reviewed, connected, and made available for evidence-linked analysis?

The result is a tool that allows readers to investigate the Bible at several levels simultaneously:

passage;

book;

genre;

audience;

covenant;

teaching function;

canonical stage;

theme;

divine action;

and whole-Bible pattern.

Its value does not lie merely in producing more charts.

Its value lies in making broad claims answerable to exact passages.

The Explorer helps users move from:

“The Bible seems to emphasize this”

to:

“These are the exact literary units, within this declared scope and method, that produced the measured pattern.”

That is the central purpose of the project: evidence before impression, context before slogans, and Scripture before statistical overstatement.