chapter-level decision records generated from the live translation registry
The evidence beneath the English
Every consequential choice
leaves a record.
The published library was 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
Luke 11
luke.11.lk11FishBread
ἰχθὺν ... μὴ ἀντὶ ἰχθύος ὄφιν / expanded bread clause
Does the father-and-son saying include a bread-and-stone question?
The bread-and-stone line is absent from the earliest Lukan form and likely entered from Matthew before the fish-and-snake question.
Why this default
The fish question without bread-and-stone is default because P75 and B preserve the shorter Lukan sequence; the added line agrees with Matthew 7:9.
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 default · shorter early text
Witnessesfish-and-snake sequence · P75, BExpanded Matthean sequence
Witnessesbread-and-stone addition · א, A, C, D, W and broad traditionFork visible
WitnessesDisplay option · addition bracketedRecord 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 7c4cbee907fbc0e84976d6e78a615134e2288f8197ce8abcf67b0452155ddc84.
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.