The structure beneath theological understanding.

Modern AI can generate theological answers in seconds. The problem is that answers often blur together: Scripture, interpretation, tradition, historical context, scholarly opinion and machine analysis. AbrahamMoses separates them — source, claim, interpretation, analysis — and never silently merges them.

Every claim in the record rests on texts, lemmas and a tradition’s reading principles. Reject any of them and the inspector traces which conclusions break, which weaken and which map connections lose their grounding — now with exact AND/OR logic, so a conclusion with two independent arguments survives the loss of one. Open the console or the visual explorer.

Corpus — the sources. Claim Ledger — what the evidence establishes. Covenant Map — where it sits in the larger story. Doctrine Graph — how theological ideas connect. Tradition Layer — how communities understand it. Research Engine — evidence-based retrieval, comparison and the dependency model. Each layer takes a structured record as input and produces traceable output.

AbrahamMoses begins with texts, not generated conclusions.

• 01 Primary text — Tanakh, Christian Bible, Latter-day Saint canon, Qur’an.
• 02 Historical witnesses & material evidence — Manuscripts and ancient versions, Second Temple literature, Inscriptions, Archaeology, Early printed editions and documents.
• 03 Reception history — Rabbinic literature, Church Fathers, Councils and magisterial documents, Medieval theology and law, Reformation writings, Tafsīr and kalām.
• 04 Modern scholarship — Textual criticism, Lexicography, Historical theology, History of religions.

Sources are classified by provenance and epistemic level, and their status is never silently altered. Corpus and coverage

The explicit textual proposition stays stable. Later theological conclusions are linked, attributed and open to review — and every revision of every claim is preserved. The Claim Ledger

The Covenant Map does not force contested theology into a single conclusion — or into a single storyline. Jewish, Christian, Islamic and Latter-day Saint readings of covenantal history are kept side by side, sharing the covenants they share, each relationship attributed to the readings it belongs to. Open the Covenant Map

Every edge has evidence, a classification and a tradition status; affirmation and dispute are attributed separately. The graph has no fixed centre and opens on Abraham, the figure every tradition in the record shares. Open the Doctrine Graph

What happens to priesthood under the New Covenant? Primary sources: Psalm 110, Jeremiah 31, Hebrews 7–10. Claim: Hebrews presents Jesus as High Priest according to the order of Melchizedek. Covenant context: Sinai → priesthood → prophetic promise → New Covenant. Tradition views are attributed at every contested step. Textual certainty is very high; interpretive certainty varies by each later theological claim.

Certainty decreases exactly where interpretation begins. The same treatment now covers four questions — one each in Jewish, Christian, Islamic and Latter-day Saint studies. The research cases

AbrahamMoses does not flatten traditions into one artificial consensus. Interpretations are stored with attribution, context and evidence; if two traditions disagree, the system shows the disagreement — and if they are asking different questions, it says that instead. The Tradition Layer

Finding, claims used, supporting evidence, primary source, covenant relationships, doctrine connections, interpretations, counterviews. The reasoning chain stays visible — no invisible leap from source to answer — and every claim now has one.

AbrahamMoses exposes structured theological research through the Model Context Protocol and a REST API: evidence, claims, covenant relationships, doctrine connections, counterviews, provenance and rejection analysis — without turning AbrahamMoses into a generic text API. Machine access

AbrahamMoses supplies the evidence architecture: corpus, claim ledger, covenant map, doctrine graph and tradition layer, through its public interfaces. Doctrine Lab works with it — research, studies, analysis and comparative doctrine. How the organisations relate

1. Scripture is the source.
2. Interpretation is attributed.
3. Analysis is identified.
4. Provenance is preserved.

The text stays the text. Everything built upon it remains traceable.