How «Gud, Allah, Altet og Ingenting» was made: one source, four tools, eighteen scriptures looked up
Short answer: «Gud, Allah, Altet og Ingenting» was written, typeset, and published on the same day King Harald died, August 28, 2026. It gathers quotes from four Norwegian kings on faith and conscience, and looks up each of the eighteen scriptures they reference. Not a single verse was typed in from memory. Here are the tools that made it possible, and what they found.
This post is not about what the book argues. It is about how it was made, because that is where it can be verified. The book is open here.
Why look up every single verse?
Because a quotation in a speech and a verse in the Bible are rarely the same. Two findings from the book, both made through lookup:
- The bishops greeted two kings with the words about going in and going out. Psalm 121:8 puts them in the opposite order: «Herren skal bevare din utgang og din inngang, fra nå av og til evig tid.»
- Following July 22, King Harald quoted «hold fast på det du har». The verse continues. Revelation 3:11 reads: «Jeg kommer snart. Hold fast på det du har, så ingen tar din krone.» In the mouth of a king, that is quite a different sentence.
The rule was simple: no verse is typed in from memory. Every single one is fetched from Bibelen Anno 2026 and reproduced exactly as it stands. Where a king or liturgy is quoted with their own phrasing, this is explicitly stated.
How were the verses fetched?
Through Darash, a Bible research engine connected to an AI assistant that answers questions posed in natural language. It holds 59 Bible texts, morphology for 31,167 verses, 446,544 cross-references, and Strong's numbers for 8,674 Hebrew and 5,523 Greek words.
A scripture was never pasted in. Junifye has a dedicated Bible citation tool that accepts a reference and a text code and retrieves the phrasing directly from Darash itself. The field cannot be left blank, and the verse cannot be entered from memory. That is why the sequence in Psalm 121:8 became apparent.
How was the book written?
The book is a Junifye book: the text has one source and is typeset from there into PDF in light and dark editions, EPUB, plain text, and web browser all at once. A correction propagates everywhere simultaneously. Three things under the hood make this possible, and the author barely notices any of them:
- The source consists of small blocks, not files. A paragraph, a heading, a Bible quote. They are edited using 178 small tools over MCP that take simple arguments: a chapter ID, a block ID, a text. The AI never touches JSON or LaTeX.
- Every change is locked against a checksum. Each chapter has a SHA-256 checksum, and an edit against an outdated checksum is rejected. Two parties cannot overwrite each other without knowing.
- Typesetting is deterministic. Canonical JSON becomes LaTeX; LaTeX becomes PDF in Tectonic. Same source, same book, every time.
All of this is accessible from the terminal. This is how the chapter «Verktøyene bak boken» was last corrected:
junifye call book_outline book_id=idb6b663fe21a4b4be8
junifye call chapter_get_source chapter_id=idcecc501c7799644a7
junifye call block_patch_text chapter_id=idcecc501c7799644a7 \
block_id=blk1822a4a0fda47f find="Rekkefølgen er enkel." replace="Rekkefølgen er enkel:"
The patching tool requires the search text to match exactly once in the block. Zero or two matches, and it does nothing. It never guesses.
The history tells the rest. The longest chapter, «Se, her er vann», is on version 77. The book's ten chapters were saved 273 times in less than three days, and every version can be restored.
What is Bibelen Anno 2026?
The Bible text in the book is new. All 66 books and 31,170 verses were translated from Hebrew and Greek by an AI pipeline where each verse passes eight strict gating checks, three adjudicating layers, and an independent witness. Above all of this stands a human veto that can reach any verse at any time.
It is not finished, and that is stated openly. Machine reading is complete, human review is underway, and the text has been released because errors are found faster in the open than in a drawer. It is fully readable today, free in Darash alongside the original text from which it was translated. How it was made.
Tringine is the Bible builder that typesets it as a standalone edition, digitally or print-ready, from a catalog of over fifty texts, with up to three Bibles side by side, verse by verse. Tringine does not produce the translation. It builds the edition, pulling original-language data from Darash.
How was the cover made?
The cover was generated from the book's own description. Junifye routes it through isac, Publifye's shared gateway to language and image models: a text model formulates the prompt, an image model draws the background, and Junifye typesets the title, author, and publisher imprint over the image itself. The background is checked for letters before use, because image models often draw in text on their own, and a title must be typeset, not drawn.
The motif became a kneeling king with his sword between his hands and a crown held above his head. Revelation 3:11 in a single image. No one drew it by hand.
How do they fit together?
| Component | Role in this book |
|---|---|
| Darash | The lookup. Eighteen scriptures, down to the individual word. |
| Tringine | The Bible edition. Bibelen Anno 2026 is one of the texts in the catalog. |
| Lexifye | The words. The glossaries at the back, from a single dictionary, pulled in during typesetting. |
| Junifye | The book itself. One source, five formats, every edit checksum-locked. |
| isac | The model gateway. The cover went through it. |
Remove one component, and something in the book would have had to be done by hand. What is unusual is not each component on its own, but that they share a single foundation: the verse in the book, the verse in the Bible edition, and the verse the AI assistant returns are the exact same text from the exact same place.
The numbers
| Written and published | August 28, 2026, the same day |
| Chapters | 10 |
| Words | 18 957 |
| Scriptures verified against the text | 18 |
| Kings quoted | 4 |
| Chapter versions saved | 273 |
| Formats from one source | 5 |
| Verses typed in from memory | 0 |
Frequently asked
Can I use the same tools?
Yes. Darash, Junifye, Lexifye, and Tringine are open services, and all connect to Claude, ChatGPT, or Cursor over MCP. How to connect.
Did an AI write the book?
No. An AI suggested and edited; an author decided. What is new is that every verse an AI wanted to quote was fetched from the source text rather than the model's memory, and that every edit passed through a checksum. The book itself states where verification was performed.
Is Bibelen Anno 2026 free?
To read, yes, in Darash, alongside Hebrew and Greek. A custom edition is built in Tringine, where the first build credit is free.
Where can I find the book?
Open at junifye.publifye.com, in the browser, as a PDF, and as an EPUB.
Read the book, or look up a verse yourself: Gud, Allah, Altet og Ingenting · Darash
Written by Jørn Andre Halseth, founder of Publifye AS. Ten years of Bible publishing and building the presses they run on, over 4,200 published Bible editions, and creator of Darash, Junifye, Lexifye, and Tringine. About us · Contact
Get an email when we ship something. Subscribe to the newsletter