Who Authorized the Authorized Version? The King James Bible and the Failure of Revelation Authentication

Abstract

The label Authorized Version on the King James Bible turns out, on inspection, to refer to no surviving document of authorization. The 1611 title page says Appointed to be read in Churches, not Authorized. The label settled into capitalized proper-name form only in the early nineteenth century. The text most modern readers hold is not the 1611 at all but a 1769 revision by an Oxford scholar named Benjamin Blayney. And the modern American conviction that the English KJB is uniquely divinely preserved above the Greek and Hebrew is a twentieth-century invention layered onto a seventeenth-century translation whose own preface disclaims it. This essay walks the historical record from the political commission at Hampton Court 1604 through Bancroft's editorial rules, the printed text's contested-lever use in three centuries of opposing English-speaking moral disputes, Blayney's revision, and the contemporary King James Only movement, applying a single diagnostic at each stage: authentication is prior to obedience — before asking whether any command is moral, ask whether the claimed source has been authenticated. The diagnostic generalizes beyond religion to any canonical text whose source-claim is taken on trust. The KJB is the worked case because the receipts are uniquely public. Companion to Morality, Power, and the Problem of a Self-Sufficient God (Zenodo 10.5281/zenodo.20738940). Version history. v1.0 (June 2026) was the completed working master — written with Claude as drafting partner, independently verified against authoritative sources, and adversarially reviewed by four independent services (GPT, Grok, Gemini, Perplexity), with all review files retained; it was held unpublished pending a venue decision. Changes in version 1.1 (first published edition): the cover is brought into the house format used across the author's deposited papers (byline William Stafford, ADN, LI-AIast5, version line, preprint/DOI/license notice); the disclosure is conformed to the deposited Earned Trust standard v1.6.3 — the byline numeral now follows the count-of-services rule (five services: Claude, GPT, Grok, Gemini, Perplexity) rather than the earlier reviewer-count framing, with reviewer independence stated in the workflow prose. No changes to the body text or argument. Version 1.2 — changes from version 1.1 (the ETR edition). This version adds the Earned Trust Record (ETR): a final page carrying the work's session record — dates, shifts, services, roles, and responsibility — encoded into a QR code that contains the record itself. Scan it from print, tap it on screen, or read it at earnedtrust.org/reader. The ETR mark appears on the cover. Typographic fix: section headings no longer strand at page bottoms. No changes to the argument or evidence. Record integrity is verifiable; authorship disclosures are provided by the author. THE SEALED RECORD (added August 2026)This version of the deposit adds the work's sealed record. Two files now accompany the paper, and here is exactly what each one is, what it does, and how anyone can check it.FILE ONE — THE PUBLIC MANIFEST (a small text file, readable by anyone).When this work was prepared for sealing, the author gathered its retained working files — the work's index, its record link, and editions v1.1 and v1.2 in Word and PDF — seven files — into one folder, and on 2026-08-04 that folder was sealed: every file was fingerprinted using the SHA-256 algorithm. A SHA-256 fingerprint is a sixty-four-character code computed mathematically from a file's entire contents. If even one letter of a file changes, its fingerprint changes completely, and it is not possible — for any person, any computer, or any artificial intelligence — to construct an altered file that produces the same fingerprint as the original. The manifest is the complete list of those sealed files: each file's name, its exact size in bytes, and its fingerprint. It proves what existed on sealing day and makes any later alteration detectable.FILE TWO — THE LOCKED BOX (who-authorized-vault-2026-08-04.7z).This is the sealed folder itself: the files named in the manifest, plus the manifest, stored in a single archive encrypted with AES-256 — the same class of encryption used in banking. Anyone may download this archive. Anyone may compute its fingerprint and confirm it matches the one published here:SHA-256 of the locked box: 3e8b8f0dd88c907a8c19ea09527fb46a0f553bd6a775444f9664b2c1bebcae19The names of the files inside the archive are visible to anyone who opens it — the list is the window. The contents of the files are what the encryption seals. The archive's contents can be opened only with the author's key, which exists solely in the author's custody and is not held by any company, service, or artificial intelligence.STATED HONESTLY.This work's drafting predates the author's archive practice: the intermediate drafts were not retained, so the sealed record is thin — the work's index, its record link, and its published editions, and nothing between. The vault carries its own honesty page saying exactly that. Under the standard, honesty about a record's limits is part of the record.HOW TO REACH THE WORK'S RECORD.The vaulted logs are sealed by the author. The work's record card — the index of how this work was made — is reached through the QR code printed in this edition. Scanning that code opens the record card in the Earned Trust Reader, where the index can be read in full and where any file later produced by the author can be verified against the manifest's fingerprints on the reader's own computer.HOW TO REQUEST THE SEALED EVIDENCE.Editors, reviewers, and readers with a genuine question may petition the author for the sealed working files. Email the author directly: Billy@lostinnovators.org. The author produces requested files individually, at the author's discretion; each produced file can then be checked against the manifest published here, proving it is byte-for-byte the file that was sealed on sealing day. Questions about the Earned Trust process itself: William@earnedtrust.org.WHAT THIS PROVES AND WHAT IT DOES NOT.The fingerprints prove that the sealed files have existed, unchanged, since the date of this deposit. A seal proves listed files unchanged; it never by itself proves the record was complete when sealed. Stating that limit is part of the method.EDITION v1.3 (August 2026) — THE SIGNATURE RESTATED.This edition also corrects the work's signature under the author's ruling that the person carries no marks — the work does. The author's name stands alone; the LI-AIast5 disclosure mark stands in the seal row beside the Earned Trust Record mark. The QR code in this edition carries the work's corrected record card, including the author's petition contact. Content is unchanged beyond the front matter, the disclosure line, and the record page.This work was made and documented under the Earned Trust (AIast) standard for verifiable disclosure of AI-assisted work, DOI: 10.5281/zenodo.20719927.The record is public. The receipts are held. Both are checkable.