Complete textual-variant dossier
Adverse entailment established
Sections distinguish readings, edition history, evidence, theological consequences, and the Research Center's evaluation. CBGM is an analytical tool; editorial committees—not the software—make textual decisions.
1Passage and issue
Passage
Issue
One Greek letter turns a king into a psalmist.
Variant class
Spelling / name
2Textus Receptus
Greek reading
The Textus Receptus names Asa, king of Judah.
Authorized Version
“Abia begat Asa; and Asa begat Josaphat.” — Matthew 1:7–8
Edition note
The Research Center uses the received Greek text underlying the Authorized Version as its baseline; edition-specific differences are recorded when the variation unit requires them.
3NA28 baseline and critical-text rationale
NA28 baseline reading
The critical text printed by Nestle–Aland and the United Bible Societies names Asaph, the Levite linked with a group of Psalms.
Translation or explanation
The critical text printed by Nestle–Aland and the United Bible Societies names Asaph, the Levite linked with a group of Psalms.
Metzger’s report of the UBS committee
Metzger reports that the UBS4 committee printed Asaph. Its stated case combines strong and geographically diverse early attestation with the transcriptional likelihood that copyists corrected the unexpected psalmist’s name to the historically expected king Asa; the committee assigned the decision a {B} rating. This is a controlled synopsis rather than a quotation.
Locator: Bruce M. Metzger, A Textual Commentary on the Greek New Testament, 2nd ed., note on Matthew 1:7–8
ECM / CBGM evidence and editors
Hugh Houghton’s current UBS6 textual commentary retains Asaph. It emphasizes the reading’s very strong early and versional support and judges Asa more likely to be a later correction to the historically expected royal name. Because the ECM of Matthew remains in preparation, this is a current editorial and transcriptional explanation, not a passage-level CBGM result.
- H. A. G. Houghton — UBS6 Textual Commentary sample, Matthew 1:7–8
- German Bible Society — UBS6 publications and relation to NA29
- German Bible Society — The Sixth Edition of the Greek New Testament
- INTF — Online Tools for the ECM
- German Bible Society — Interview with Hugh Houghton
- INTF — Gerd Mink on what the CBGM does and does not decide
4UBS6 and intended NA29 revision
UBS6 retains the NA28 / UBS5 Greek main-text wording in Matthew, so no main-text change is shown for this passage. The separate project ledger covers Acts, Mark, and Revelation.
No change row is attached to this passage.
UBS6 is published, and the German Bible Society identifies its Greek main text as identical to the intended NA29 main text. The complete NA29 volume and its apparatus remain forthcoming. Project-ledger rows retain their source and verification statements until they are checked against the published UBS6 text and, when available, the NA29 apparatus.
5Doctrinal and four-point analysis
Effect class
Weakening of explicit biblical testimony
Exact proposition affected
The triune identity of the Father, the Son/Word, and the Holy Ghost.
Doctrinal analysis
Inspiration should not be used as a shortcut that saves us from looking at manuscripts. Asa is not a theological repair.
Bahnsen four-point examination
Arbitrariness
At Matthew 1:7–8, the critical choice avoids arbitrariness only to the extent that it states public manuscript, transcriptional, and intrinsic grounds. The critical text printed by Nestle–Aland and the United Bible Societies names Asaph, the Levite linked with a group of Psalms. Why editors print Asaph Asaph has old and varied support, including Sinaiticus, Vaticanus, and early versions. Critics also call it the harder reading.
Inconsistency
The criteria used at Matthew 1:7–8 must be applied to comparable readings as well. A principle such as age, difficulty, brevity, or coherence cannot be decisive here and quietly reversed elsewhere merely to escape a historical, grammatical, or theological difficulty.
Consequences
Weakening of explicit biblical testimony: Inspiration should not be used as a shortcut that saves us from looking at manuscripts. Asa is not a theological repair.
Preconditions of intelligibility
The argument presupposes stable authorship, meaningful language, objective logical norms, transmissible evidence, and a coherent account of how Scripture can be received and identified by the church. The analysis tests whether the method can make those conditions intelligible without reducing the text to an indefinitely revisable editorial construct.
This framework examines an argument and its conditions; it does not claim to read an editor's private motives.
6Argument for the received reading
External and historical evidence
Why editors print Asaph Asaph has old and varied support, including Sinaiticus, Vaticanus, and early versions. Inspiration should not be used as a shortcut that saves us from looking at manuscripts. Asaph is ancient enough to deserve study, but not authentic enough to enter the royal line.
Internal and transcriptional evidence
A scribe who found the wrong man in a royal genealogy would have a reason to remove the final phi and restore Asa; no equally obvious reason seems to turn correct Asa into Asaph. That account is coherent, but it asks Matthew to make the very mistake later scribes would notice. A copyist can finish a short name with the ending his memory expects.
Reception and ecclesiastical use
The Textus Receptus names Asa, king of Judah. The broad Greek transmission keeps Asa. John William Burgon and Edward Miller, The Traditional Text of the Holy Gospels.
Providential-preservation analysis
Providential preservation is not used as a substitute for evidence at Matthew 1:7–8. It supplies the confessional context in which manuscript transmission, broad reception, and the church's actual possession of Scripture are evaluated together.
Canonical coherence with the rest of Scripture
Canonical coherence remains an explicit test: a proposed reading must make grammatical and theological sense within the immediate context and the rest of Scripture. No conflict is asserted merely because two editions differ; the claimed incoherence must be demonstrated at this passage.
Canonical-coherence verdict
The Authorized Version is retained where its representation of the TR forms a coherent reading within the immediate context and the rest of Scripture. Any competing form must demonstrate an equal or better canonical fit rather than merely invoke an edition or method label.
Response to the principal critical argument
The critical text printed by Nestle–Aland and the United Bible Societies names Asaph, the Levite linked with a group of Psalms. Why editors print Asaph Asaph has old and varied support, including Sinaiticus, Vaticanus, and early versions. Critics also call it the harder reading.
Conclusion
Nor does receiving Asa require the claim that every late copy is good or every early copy bad. A single old exemplar can pass one mistake to several descendants; a later manuscript can preserve a reading older than its parchment. Dates belong to physical witnesses, while readings have histories that reach behind them. That is why antiquity must be joined to number, variety, continuity, context, and the author’s evident claim.
The choice also sets a rule for the genealogy that follows. Historical fitness does not override manuscript evidence, but neither may a favored manuscript rule force an inspired historian into a false assertion when an old, broad, and exact reading stands before us. Asa is not a theological repair. He is the king Matthew’s sentence requires.
Logical entailment
The Authorized Version serves as the faithful English representation. The preservation claim applies immediately to the authentic Hebrew and Greek texts—not to an English translation as though it were the inspired source.
Status: Established
Immediate textual or doctrinal consequence
At Matthew 1:7–8, the received text names Asa, the king of Judah, while the critical text names Asaph, the psalmist. No distinct Christian doctrine is lost, but the critical reading changes the person named in the royal genealogy and creates an immediate historical-identification problem.
Necessary reasoning chain
- At Matthew 1:7–8, the received Hebrew/Greek form is “The Textus Receptus names Asa, king of Judah.”; the Authorized Version represents it as “Abia begat Asa; and Asa begat Josaphat.” — Matthew 1:7–8”. The assessed critical form is “The critical text printed by Nestle–Aland and the United Bible Societies names Asaph, the Levite linked with a group of Psalms.”.
- The received and critical forms are not the same at this locus. Therefore, if the competing critical form is original, the received form is secondary rather than the authentic wording at this place. The immediate consequence is: At Matthew 1:7–8, the received text names Asa, the king of Judah, while the critical text names Asaph, the psalmist. No distinct Christian doctrine is lost, but the critical reading changes the person named in the royal genealogy and creates an immediate historical-identification problem.
- If the received form at this place is secondary rather than original, then the authentic Hebrew/Greek text was not kept pure at this place in the received textual tradition; therefore the unqualified confessional preservation claim must be denied or redefined.
Ultimate preservation consequence
If the competing reading is original and the received reading is secondary, then God did not preserve and keep pure the authentic text at this place in the received textual tradition. The unqualified confessional claim that Scripture was kept pure in all ages must therefore be denied or redefined.
Sources
- Westminster Confession of Faith (1647)Chapter 1, section 8 — Governing confessional preservation claim
- H. A. G. Houghton — UBS6 Textual Commentary sample, Matthew 1:7–8Current critical-edition, ECM, or editorial documentation
- German Bible Society — UBS6 publications and relation to NA29Current critical-edition, ECM, or editorial documentation
- German Bible Society — The Sixth Edition of the Greek New TestamentCurrent critical-edition, ECM, or editorial documentation
- INTF — Online Tools for the ECMCurrent critical-edition, ECM, or editorial documentation
Read the full research essay and its sources
One Greek letter turns a king into a psalmist. The Textus Receptus names Asa, king of Judah. The critical text printed by Nestle–Aland and the United Bible Societies names Asaph, the Levite linked with a group of Psalms. Because the name closes one clause and opens the next, the change appears twice.
“Abia begat Asa; and Asa begat Josaphat.” — Matthew 1:7–8
This is not a difference in English spelling. Asa was Abijah’s son and Jehoshaphat’s father. Asaph was not.
Why editors print Asaph
Asaph has old and varied support, including Sinaiticus, Vaticanus, and early versions. Critics also call it the harder reading. A scribe who found the wrong man in a royal genealogy would have a reason to remove the final phi and restore Asa; no equally obvious reason seems to turn correct Asa into Asaph.
That account is coherent, but it asks Matthew to make the very mistake later scribes would notice. Some defend the result by supposing that he copied a faulty list. The supposition protects a rule about harder readings at the cost of the Gospel’s historical claim.
Matthew did not place an obscure name in an open slot. His pattern says that Abijah begat the disputed man and that the same man begat Jehoshaphat. First Kings 15 and First Chronicles 3 name Asa in that exact line.
An old error is still an error
Asaph need not have arisen from a deliberate change. Both names were familiar to biblical readers, their Greek forms differ by one final letter, and Asaph’s name appeared often in psalm headings. A copyist can finish a short name with the ending his memory expects. Once the error entered an early exemplar, age and geographic spread would record its success, not its truth.
The broad Greek transmission keeps Asa. So do the Old Testament sources and the sense of the genealogy. These are not three unrelated votes. They join at the historical person Matthew is naming.
Inspiration should not be used as a shortcut that saves us from looking at manuscripts. It does tell us what kind of writing lies before us: Matthew’s genealogy makes true claims about the line of Christ. The evidence then points to the reading that tells that truth.
Asa belongs in both places. Asaph is ancient enough to deserve study, but not authentic enough to enter the royal line.
The paired occurrence makes the result unusually testable. Matthew does not merely use the disputed form once, where a reader might wonder about an unknown alternate spelling. He uses it on both sides of the same genealogical link. Whatever name he wrote must be the man begotten by Abijah and the man who begot Jehoshaphat. The Old Testament answers both relations with one voice.
Nor does receiving Asa require the claim that every late copy is good or every early copy bad. A single old exemplar can pass one mistake to several descendants; a later manuscript can preserve a reading older than its parchment. Dates belong to physical witnesses, while readings have histories that reach behind them. That is why antiquity must be joined to number, variety, continuity, context, and the author’s evident claim.
The choice also sets a rule for the genealogy that follows. Historical fitness does not override manuscript evidence, but neither may a favored manuscript rule force an inspired historian into a false assertion when an old, broad, and exact reading stands before us. Asa is not a theological repair. He is the king Matthew’s sentence requires.
Sources and further reading
- 1 Kings 15:8–24; 1 Chronicles 3:10; Matthew 1:1–17.
- Bruce M. Metzger, A Textual Commentary on the Greek New Testament, note on Matthew 1:7–8.
- John William Burgon and Edward Miller, The Traditional Text of the Holy Gospels.
7Related materials
Open a group to follow connected articles, books, biographies, media, research notes, variants, or downloads. Research Center relationships use permanent record IDs; external items retain their actual link.
- Record
- VAR-1001
- Status
- Preliminary
- Version
- 1.1-dossier
- Review
- Level B — Editorial synthesis
- Editor
- Chris Thomas
- Reviewer
- Independent reviewer pending assignment
- First date
- 2026-07-22 · Exact Day
- Last revised
- 2026-07-22
Evidence and editorial controls
- Verification
- Recovered project data; bibliographic and source-level verification remains record-specific. Metzger commentary entries were matched by exact passage where present; ECM/CBGM rationale is passage-specific only when an official editorial explanation is cited. Ledger rows are identified as UBS6 / intended NA29 data but retain their row-level verification caveats pending direct collation.
- Rights and access
- Original editorial synthesis; cited sources retain their stated rights.
- Known limitations
- Staging record; independent review remains open.
Links from this record
No public outgoing links are recorded.
Records that cite or connect here
No public backlinks are recorded.
Corrections and evidence submissions
No correction submission is presently attached to this record. Submit evidence or read the correction policy.
Chris Thomas, “Matthew 1:7–8 — Asa or Asaph? The Name in Christ’s Royal Genealogy,” VAR-1001, Confessional Bibliology Research Center, version 1.0-staging.
Revision history
- — Chris Thomas
- — Chris Thomas
- — Chris Thomas