Primary text
- Tanakh
- Christian Bible
- Latter-day Saint canon
- Qur’an
Research infrastructure · Vol. I
The structure beneath
theological understanding.
AbrahamMoses connects Scripture, historical sources, covenantal context, doctrine, interpretation and evidence in one structured theological intelligence system.
Every important conclusion remains traceable to its source.
Scripture · Context · Connections · Provenance
CH. 01 — The problem
Answers are easy.
Knowing why they are true is harder.
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.
01Source
02Claim
03Interpretation
04Analysis
Never silently merged.
CH. 02 — The system
One theological question. Six connected layers.
CH. 03 — Corpus
Start with the sources.
AbrahamMoses begins with texts, not generated conclusions.
Contemporary witness
- Second Temple literature
- manuscripts
- inscriptions
- archaeology
- historical witnesses
Reception history
- Rabbinic literature
- Church Fathers
- councils
- medieval theology
- Reformation writings
Modern scholarship
- textual criticism
- linguistics
- archaeology
- historical theology
- modern scholarship
Classification rule
Sources are classified by provenance and epistemic level. Their status is never silently altered.
CH. 04 — Claim ledger
Every conclusion becomes auditable.
AM-CLAIM-000184Verified record
Hebrews identifies Jesus as High Priest according to the order of Melchizedek.
- Type
- Explicit textual proposition
- Source
- Hebrews 5:6
Hebrews 6:20
Hebrews 7:17
- Textual confidence
- Very high
- Disputed
- No — regarding what Hebrews explicitly states
- Interpretive divergence
- Begins when determining the ecclesiological implications of the claim.
CH. 05 — Covenant map
See where a passage sits in the bigger story.
Selected node
Abraham
The Covenant Map does not force contested theology into a single conclusion. Different interpretations remain attributed to the traditions or sources that hold them.
CH. 06 — Doctrine graph
Doctrine is a network, not a list.
Jesus Christ
Every edge has evidence.
CH. 07 — Worked example
Ask one question. See the whole chain.
Question
What happens to priesthood under the New Covenant?
Primary sources
Psalm 110 · Jeremiah 31 · Hebrews 7–10
Claim
Jesus is presented in Hebrews as High Priest according to the order of Melchizedek.
Covenant context
Sinai → priesthood → prophetic promise → New Covenant
Doctrine connections
Priesthood → Melchizedek → Jesus → sacrifice → covenant → atonement
Tradition views
Attributed perspectives remain visible at every contested step.
Finding
Hebrews explicitly connects Jesus’ priesthood with a changed covenantal order.
Textual certaintyVery high
Interpretive certaintyVaries by subsequent theological claim
Certainty decreases exactly where interpretation begins.
CH. 08 — Traditions
Different traditions. Clearly attributed.
Active lens
Rabbinic Judaism
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.
CH. 09 — Provenance
Why does AbrahamMoses say this?
01Finding
02Claims used
03Supporting evidence
04Primary source
05Covenant relationships
06Doctrine connections
07Interpretations
08Counterviews
The reasoning chain stays visible.
No invisible leap from source to answer.
CH. 10 — MCP
Built to be used by other intelligence systems.
CorpusClaimsCovenantsDoctrineTraditions
Model Context ProtocolMCP Server
Doctrine LabAI agentsresearch toolsacademic systemsapplications
AbrahamMoses exposes structured theological research through the Model Context Protocol. Applications can retrieve evidence, claims, covenant relationships, doctrine connections, counterviews and provenance — without turning AbrahamMoses into a generic text API.
CH. 11 — Partnership
AbrahamMoses × Doctrine Lab
Structured theological evidence.
Corpus · Claim Ledger · Covenant Map · Doctrine Graph · Tradition Layer
MCP
Research in context.
Research · Studies · Analysis · Kultur · Comparative doctrine
AbrahamMoses supplies the evidence architecture. Doctrine Lab works with it.
CH. 12 — Principles
Four rules govern the system.
Scripture is the source.
Interpretation is attributed.
Analysis is identified.
Provenance is preserved.
AbrahamMoses · Structured theological intelligence
The text stays the text.
Everything built upon it remains traceable.
AbrahamMoses is building structured infrastructure for deeper theological research, clearer disagreement and more accountable interpretation.
Sacred sources. Structured truth. A clearer tomorrow.