Documentation
How the record is built
AbrahamMoses is a structured record, not a commentary. This page describes the objects it stores, the editorial rules that govern them and the public endpoints that serve them.
Model
Objects in the record
Source
A primary text or historical document. Sources are cited, never paraphrased into a conclusion.
Claim
A single stated proposition with a code, type, sources, textual confidence and dispute status.
Provenance step
One ordered link in the derivation record behind a claim.
Covenant relationship
A directed edge between covenant nodes, carrying evidence and confidence.
Doctrine connection
A node pair with relationship type, classification, tradition status and evidence.
Interpretation
A reading attributed to the tradition or source that holds it — never presented as the text.
Editorial
Governing rules
Scripture is the source
Primary text is recorded as text. Nothing is rewritten to fit a conclusion.
Interpretation is attributed
Every reading names the tradition, author or source that holds it.
Analysis is identified
Machine or editorial analysis is labelled as analysis, never as source material.
Provenance is preserved
A finding that cannot show its chain does not enter the public record.
Dispute stays visible
Counterviews and divergence are recorded beside the claim, not hidden behind it.
Reading the record
By hand, or by machine
curl https://abrahammoses.org/api/public/claims?limit=5 curl https://abrahammoses.org/api/public/claims/AM-CLAIM-000184 curl https://abrahammoses.org/api/public/covenants curl "https://abrahammoses.org/api/public/doctrine?topic=Priesthood" curl "https://abrahammoses.org/api/public/provenance?claim=AM-CLAIM-000184" curl https://abrahammoses.org/api/public/mcp
Endpoints are public, read-only and return published records only. Full parameter reference lives on the machine access page.