Designing .bok: a book that never needs a second edition
Every digital book format I have used treats translation as a new product and narration as an afterthought. The .bok proposal starts from a different question: what if one file were the book, in every language, for good?
A PDF is a photograph of a page. An EPUB is a folder wearing a costume. Neither was built for a book that lives in nine languages, narrates itself, and updates after it ships. .bok is a proposal for one that is.
A proposal, not a product — yet
The .bok idea was not commissioned or workshopped with a team. It was written alone, over two days in January 2026, as a proposal aimed at AI coding tools rather than at investors — a founder working out, sentence by sentence, what a format should be before asking anyone to build it.
That origin matters for how this page reads. What follows is the idea in its considered form, not a shipped standard. A public technical specification is being prepared; this is the thinking behind it.
One file. Every language. No second edition.
Publishing a book in nine languages today means nine separate files, nine separate covers, nine separate places something can go stale. The .bok proposal inverts that: a single `.bok` file carries every language edition of a work inside it, switching on the reader's choice rather than the publisher's print run.
Inside that same file: room for an AI-narrated audio edition in any of those languages, and an assistant that can summarize, translate or explain a passage on request — not bolted onto the book afterward, but part of what the file already is.
BOK Reader
Free. Opens and displays a .bok file — the only piece meant for every reader, not just publishers.
BOK Creator
A layout tool in the spirit of InDesign, purpose-built for books, magazines, newsletters and text-and-image documents.
BOK Editor
Edits an existing .bok file's content and metadata without touching its layout.
BOK Library
Organizes and manages collections of .bok files — built for institutions, universities and libraries.
Built to be opened, not extracted
A `.bok` file is proposed to behave like a mounted disk image rather than an unzippable archive: the platform itself generates and holds the encryption key, never the author, so a book cannot be casually copied out from under its publisher the way a PDF can. Access — to read, or to edit as the rights holder — is checked against an account each time the file is opened.
This is a stronger claim than most formats make, and it is exactly the kind of claim that needs a published specification and independent scrutiny before anyone should take it on faith. It is recorded here as the design intent, not a guarantee.
| A typical ebook today | The .bok proposal |
|---|---|
| One file per language | One file, every language inside it |
| Narration sold separately, if it exists | AI narration built into the same file |
| Static once published | Can receive updates after release |
| Extractable as a zip (EPUB) | Opens only through licensed tools |
The oldest message, reread
The name is meant to be read exactly as it looks: BOK, pronounced like book, three letters in the tradition of the format extensions it wants to succeed. The mark behind it, in the proposal, is a first human carving a message into stone — not holding a book, because there was no book yet, only the instinct to make meaning last. Whether that mark survives into a finished identity is still open; the instinct behind it — a format built for meaning to last across languages and time — is the part worth keeping regardless.
Interested in where a format like this could go?
Yatırım


Discussion
Comments are read by Kamiloo before they appear.