Structured theological research

Begin with a question.

AbrahamMoses keeps what a text says apart from how each tradition reads it, records what every conclusion rests on, and lets you reject an assumption to see what follows — without altering a single source.

Four traditions · one recordFour traditions, one set of sources that is never altered. Choose a question and trace it to them.

Listed in the historical order of the traditions whose questions they are.

01 · Research

A worked answer, from the record

Christian studiesProvisional

What changed concerning priesthood under the New Covenant?

Hebrews explicitly identifies Jesus as high priest after the order of Melchizedek and argues that a change of priesthood entails a change of law. That much is a report of the text. Whether the Levitical priesthood is thereby superseded, and what follows for priesthood in the church, are interpretations — and that is where Christian traditions divide among themselves, and where Rabbinic Judaism dissents.

What the texts say

AM-CLAIM-000184

Hebrews identifies Jesus as High Priest according to the order of Melchizedek.

Hebrews 5:6; Hebrews 6:20; Hebrews 7:17 · textual certainty: Secure

AM-CLAIM-000185

Jeremiah announces a new covenant that is not like the covenant made at Sinai.

Jeremiah 31:31-34 · textual certainty: Strong

AM-CLAIM-000186

Psalm 110 addresses a figure who is declared a priest forever after the order of Melchizedek.

Psalm 110:1; Psalm 110:4 · textual certainty: Strong

Where interpretation begins

AM-CLAIM-000191 Catholic, Eastern Orthodox, Lutheran, Reformed, Evangelical

The Melchizedekian priesthood of Christ supersedes the Levitical priesthood and its sacrificial order.

Rests on 2 derivation(s); requires AM-AX-001, AM-AX-002

AM-CLAIM-000197 Rabbinic Judaism

The Levitical priesthood is suspended by the loss of the Temple, not superseded: no later priesthood abrogates the Torah’s priestly order.

Rests on 2 derivation(s); requires AM-AX-005, AM-AX-004

Challenge an assumption

Reject AM-AX-002 — Figures prefigure fulfilment (Typological (Patristic, Catholic, Orthodox)):

  • AM-CLAIM-000191: Support weakened
  • AM-CLAIM-000197: Supported under selected assumptions
  • Across the record: 0 not established under the selected assumptions, 5 with support weakened or only partial. No source changed.

Every line above is a public record with a code; nothing on this page is generated. Records marked provisional await editorial verification.

02 · The method

Certainty decreases exactly where interpretation begins

Six connected layers hold the evidence. Confidence is recorded on separate axes that are never combined, and every conclusion records the derivations it rests on — so setting one assumption aside affects only what genuinely needs it.

01
Corpus

The sources, cited by edition and classified by provenance.

02
Claim Ledger

What the evidence establishes, one revisioned claim at a time.

03
Covenant Map

Where a passage sits in each tradition’s covenantal history.

04
Doctrine Graph

How ideas connect, with evidence on every edge.

05
Tradition Layer

How communities read the texts, in their own categories.

06
Research Engine

Retrieval, comparison and the dependency model.

Five measures, never one score

  • Textual certainty — Is the wording the claim relies on securely established in the witnesses?
  • Philological certainty — How securely is the meaning of the wording established?
  • Historical support — What does evidence outside the claim’s own tradition support?
  • Inferential strength — How strongly does the claim follow from its stated premises?
  • Traditional acceptance — recorded per tradition, as affirms, qualifies, disputes, rejects or does not address.

Exact dependency logic

  • A conclusion with two independent arguments survives the loss of one.
  • A report of what a text says keeps its standing when a reading of it is rejected.
  • Circular support never establishes anything.
  • Rival readings are shown on both sides; the dispute is never declared settled.

03 · Explore the record

The public record

04 · For institutions and developers

One host, two interfaces, tested end to end

MCP server

For AI agents and research tools. Streamable HTTP; tools, resources and prompts; read-only.

https://abrahammoses.com/mcp

REST API v1

For applications. JSON with published schemas, an OpenAPI document and stable error codes.

https://abrahammoses.com/api/v1

05 · About AbrahamMoses

Who stands behind the record

AbrahamMoses is a research product written, built and owned by Sagolik. It is not an accredited institution. Every record names its author, its review state and whether machine assistance was involved; corrections are appended as new revisions, never made silently.