chapter-level decision records generated from the live translation registry
The evidence beneath the English
Every consequential choice
leaves a record.
John, Mark, Matthew, and Luke were developed through direct Greek analysis, lexical work, and manuscript comparison. Where surviving witnesses materially disagree, the competing Greek readings and their effect on English remain open to the reader.
public provenance schema, designed to remain machine-readable and auditable
standardized inspectable Greek reference edition
Textual basis
SBL Greek New Testament
Edited by Michael W. Holmes. The project's standardized, publicly inspectable Greek reference edition. It is not presented as retroactive proof that every existing chapter originated from one uniform printed edition.
This is an honest reference claim, not a retroactive claim that all completed work began from one uniform printed edition. Material manuscript forks remain independently documented at the reading they affect.
Translation record
Mark 3
115 records217 records315 records417 records516 records618 records718 records822 records923 records1026 records1120 records1219 records1317 records1430 records1527 records1613 records
mark.3.m3Boanerges
Βοανηργές… υἱοὶ βροντῆς
TRANSLATIONhigh confidence
How should Mark’s preserved nickname be carried into English?
Mark gives the transliterated Semitic form Boanerges and then interprets it as ‘Sons of Thunder.’
Why this default
The combined form is default because Mark himself preserves both layers: the sounded Semitic nickname Boanerges and his Greek explanation, ‘Sons of Thunder.’ Choosing only one discards either the transmitted name or the interpretation the narrator deliberately provides.
Evidence
ExternalNo separate external-evidence note is recorded for this stable-text decision.
InternalThe decision record relies on the stated lexical, grammatical, or translation rationale.
Project defaultBoanerges, which is ‘Sons of Thunder’
Project default · both layers
AlternativeBoanerges
Transliteration preserved
AlternativeSons of Thunder
Interpretation used directly
Record integrity
One registry drives both the reader and this record.
The manifest is regenerated from the translation source before every production build. Its source digest is 450adc54c1fc782fbae5e9ed6a640a2ae0e3be080722ac134c84e1248c2a312a.
Decision-level revision history begins with this ledger. Earlier development is not reconstructed into false precision; future material changes can be appended to the relevant record with their reason and date.