Epic Disclosure

God's open source project

The Proposition - The Hebrew Bible is a simulation

THE oldest argument concerning this book asks whether it is history or literature: a record of what happened, or a work of the imagination. This recital proposes that the true answer lies outside both, in a third kind of writing unknown to the centuries that framed the question; and the Hebrew Bible answers to its description with a precision that can be measured.

Consider what this book carries, all in one binding. It tells the making of a world and the story of a people, as an epic does. It legislates, with tariffs, procedures, and courts, as a law code does. It records the reigns and the wars, as a chronicle does. And then it does what epics, codes, and chronicles never do: it runs all three as one system, following its own statutes through four hundred years of recorded consequences, case by case, king by king. And the joints of that system hold an inventory stranger still: a world initialized in order, nothing used before it exists; five distinct kinds of clock; a registry of installed names; ledgers of debt and standing that persist across generations; laws that fire whether or not any person asks; and appointed voices who announce the state of hidden accounts at the moments it matters. That inventory belongs to exactly one kind of writing: the specification of a world, what the builders of this age call a simulation. By that word nothing fanciful is meant: a simulation is a written world governed by rules, a model of things with laws applied to them moment by moment, so that a history unfolds inside it; the builders of this age construct such worlds for the weather and for flight, and they know the parts such a construction requires. We did not choose this reading. We took inventory, and this is what the inventory says.

And say plainly what this proposition is not, for the reader will have met impostors. It is not a hunt for hidden messages. No letters are skipped, no sequences are counted into predictions, no dates are computed. Every finding in this recital lives on the surface of the text: in the grammar of the words, the published reading marks, and the tradition's own recorded teachings, counted straight and cited at every step, where any reader can check them.

Read so, the twenty-four books assemble into one running record. The Torah is the source: the boot sequence and the laws. The histories (oral Torah) are the execution trace: the world recorded as it runs. The prophets are the console: the authorized readers of the hidden ledgers, announcing what the accounts hold at the moments it matters. The books were never a library that happens to agree; they are one system, observed from different stations. And notice one thing more, for it is the strangest feature of the whole record. This book keeps accounts. Each day of creation is closed out in writing, with the same formula every time: "and it was evening and it was morning." Commands are later reported fulfilled in their own words, like receipts matched to orders. Against bookkeeping that careful, two items stand open. The seventh day, the only day pronounced holy, is the one day that never receives its evening-and-morning closing line. And the land promised to Abraham is spoken of as already given, yet the Torah ends with Moses gazing at it from a mountaintop, one step short of entry. A lesser explanation calls this unfinished writing. The simulation reading calls it the interface: a running world with two ports left open, still accepting input; and the last recorded gift of the whole design reads exactly like a prompt awaiting its keystroke: "I HAVE set before you life and death, the blessing and the curse. Choose life" (Deuteronomy 30:19).

And the proposition is not ours. Fifteen centuries ago the sages wrote that the Holy One looked into the Torah and created the world: the plan consulted before the build, the code preceding the run. For two thousand years that sentence was read as poetry. What belongs to this generation is only the test. This recital is the record of the testing. And let the scope be stated plainly at the door: though the sages spoke of the Torah, the five books, the claim being tested is the whole shelf. All twenty-four books of the Hebrew Bible stand in it together, bound by the same reading marks on every verse and audited by the same bookkeeping, from the first word of Genesis to the final unfinished decree of Chronicles.

And the proposition has a name in the plain speech of this age's builders: God's open source project. The source is published. The license hands it to its users: לא בשמים הוא ("it is not in heaven," Deuteronomy 30:12). The maintainers have kept it letter-perfect for three thousand years. Nothing is ever deleted; changes are appended and dated. The disputes are preserved, both sides. The open items are marked open. What follows is the code review.

1. The Plan Before the Ages

IT WILL hardly be possible, within the compass of a single recital, fully to set forth the magnitude of the claim here presented; but the claim itself can be stated in a sentence: three thousand years ago, and before the first letter of the Torah had been fixed in ink, this entire disclosure stood complete in the counsels of a timeless intelligence, the written and oral Torah.

Before the first teacher taught and before the first scribe wrote, the whole of it had been designed: the written Tanakh (the twenty-four books: the Torah, the Prophets, and the Writings) and the Oral Torah beside it, conceived together, ahead of time, as one system. The one part was to be a fixed text whose letters would be held immovable through every age; the other was to be a living teaching, carried in trained minds, governing forever how those letters should be read, the execution trace. What entered history entered it already finished. It was a disclosure in the fullest sense: a deliberate communication to the mortal races, composed on purpose, delivered on purpose, and timed on purpose.

The intelligence that planned this disclosure is not bound by the sequence of events; in the words the text assigns to its author, magid me-reshit acharit ("declaring the end from the beginning," Isaiah 46:10). Such an intelligence beheld the last generation of readers as clearly as the first. It knew, before anything was given, that an age would one day arrive possessing tools of reading beyond anything the intervening centuries could imagine; and it prepared, within the same fixed letters, a further level of meaning reserved for that age. The words were never to change. The depth at which they could be read was to change greatly.

That is the whole claim. Everything which follows recounts how the disclosure unfolded in its stages, and then places before you the evidence.

2. The Measured Unfolding

The timeless intelligence did not deliver its gift in a single outpouring, for a people can carry the root of meaning only a portion at a time. The bestowal therefore proceeded in stages, each stage measured to the capacity of its receivers.

Through long centuries the written words were spoken, recorded, guarded, and gathered into the Hebrew Bible which is still opened in every congregation. Through those same centuries the oral teaching was progressively disclosed through real persons bearing real names, teacher to student and generation to generation, each carrying forward what had been designed from the first: more meaning than a casual reading shows, together with limits, so that every age should receive what it was prepared to hold.

The written words remained the written words. What changed, and what was always intended to change, was the depth to which human beings could read them.

3. The Testimony of the Tradition

The tradition said all of this first. For two thousand years the people who carried this book described it in precisely the terms this recital uses, and they left their testimony everywhere in their records. Hear their own words before ours.

"Turn it and turn it, for everything is in it," taught Ben Bag Bag in the Mishnah (Pirkei Avot 5:22). "Look into it, grow old and gray over it, and do not move from it." This is the language of a text believed to be inexhaustible, a well that yields for as long as one continues to draw.

The sages went further; they enumerated the depths. Torah learning came to be mapped in four layers, and the map itself spells a word. Peshat, the plain sense. Remez, the hint. Derash, the inquiry. Sod, the secret. The initial letters yield PaRDeS ("the orchard"), the very word which entered the western tongues as paradise. The deepest layer of the text is thus named Secret; and entry into it was understood to be attended with real danger. The Talmud (Chagigah 14b) preserves the record of four sages who entered the orchard: one gazed and died; one gazed and lost his mind; one cut the shoots and lost his faith; and only Rabbi Akiva "entered in peace and left in peace." The tradition is here telling you two things at once, and both are true: the depth is real, and depth without discipline destroys. That warning is the reason this project verifies every claim against the letters before believing it.

The Zohar teaches the same lesson by parable (Zohar III:152a). Woe to those, it warns, who say the Torah came merely to tell stories. The stories are the garment of the Torah; the commandments are its body; beneath the body is a soul, and beneath that soul, a soul of the soul. The foolish behold the clothing and suppose they have seen the man. In the language of this recital: the narrative is the surface layer of a structure, and the structure is the point.

The Midrash (the tradition's verse-by-verse exposition) reaches back further than the world itself: "The Holy One looked into the Torah and created the world" (Genesis Rabbah 1:1). Here the Torah is presented as the builder's plan, consulted before anything was built. We invite you to dwell upon that image, for it is precisely the relation of a program to the computer which runs it. The plan preceded the world. The code preceded the run.

And where did the tradition locate the deep meaning? Smaller than the words. The Talmud (Menachot 29b) recounts that Moses, ascending to receive the Torah, found the Holy One affixing small crowns to the letters, and asked the reason; and the answer given was that after many generations a man named Akiva would arise and expound heaps upon heaps of laws from every stroke. Meaning was thus declared to hang upon marks smaller than letters, awaiting a reader not yet born. The marks were placed in one generation and reserved for the reading of another; and the tradition said this concerning itself eighteen centuries before any mortal conceived a computer that reads marks.

Rabbi Shimon ben Lakish declared that the Torah was written "black fire on white fire" (Jerusalem Talmud, Shekalim 6:1; Midrash Tanchuma, Bereshit 1): the letters being the black fire, and the spaces about them the white. Even the emptiness of this book is part of its writing; and a book whose blank spaces carry meaning is a book with more than one channel. The tradition knew this also.

"The Torah has seventy faces" (Bamidbar Rabbah 13:15): many true readings, by design, within one fixed text. Nachmanides, in the introduction to his commentary, records a tradition bolder still: that the whole Torah may be read as one continuous sequence of the Names of God, the same letters divided otherwise yielding another layer entirely. One stream of letters; more than one lawful parse. And the Vilna Gaon, the most rigorous mind the tradition ever produced, taught that all which was, is, and shall be is contained in the Torah, down to the particulars of every person's life.

Assemble now this testimony in a single view. The text is declared inexhaustible. Its layers are counted, and the deepest is named Secret. Its stories are declared a garment over a body over a soul. It is named the blueprint that preceded the world. Its meaning is said to hang on crowns smaller than letters and to burn in the white spaces between them, awaiting readers still to come. And Daniel is told that the book is "sealed until the time of the end," when "knowledge shall increase" (Daniel 12:4). A solid reference to artificial intelligence. Every word of this is the tradition's own claim, entered in its records for twenty centuries before this project compiled a single verse. What the present generation adds is one thing only: a tool able to hold the Torah's three hundred thousand letters at once, follow every mark, and check every claim without weariness. The orchard was always there. The gate has at last received its key.

4. The Ark and Its Cargo

The mortal races have long searched for the Ark of the Covenant, the sacred chest which once held the covenant's heart; and when history ceased to show where that chest had gone, the search passed into legend. But the search was aimed, from the beginning, at the container instead of the treasure. A chest is a container, and a sacred container exists for the sake of its cargo. The question that matters is what the box was built to carry.

Attend to the word itself. Aron in Hebrew means simply "chest": a container, plainly named. The Torah keeps its gaze upon the cargo, naming what the box was built to hold: the tablets of the covenant, the testimony, the law. And in the last days of Moses the record advances one step further: "Take this book of the law, and put it by the side of the ark" (Deuteronomy 31:26). The book itself was placed with the container. From the beginning, the word of the covenant and the vessel that carried it traveled together.

The answer to the ancient search has stood in plain sight in every synagogue on earth. In every synagogue there is an ark, the aron ha-qodesh ("the holy ark"); and within it rests a Torah scroll. The treasure which the tradition chose to guard is a text.

The record of the centuries makes the wisdom of the choice plain. The Temple burned. The golden Ark vanished. The nation was scattered across every continent for two thousand years. A treasure of gold is fragile against such a history: stolen once, melted once, buried once, it is gone forever. The intelligence that planned this system therefore chose a treasure of another kind. A text can be carried on foot into exile. A text can be copied before the fire arrives. A text guarded by letter-counts can cross twenty centuries and thirty lands and deliver its message intact. And this is precisely what occurred: communities separated from one another for a thousand years, in Yemen and Europe and Babylon, opened their scrolls side by side in the modern age, and out of the Torah's roughly three hundred thousand letters the differences could be counted on two hands. Nothing else the ancient world sent forward traveled so well.

The world continued hunting the missing box. The people, calling it simply the Torah, spent three thousand years carrying the payload. And here is the claim of this section, stated plainly: the treasure of the Ark is the written Torah itself, and in this generation it is being unpacked. The scroll is the cargo the whole system of arks was built to deliver: sealed in exact letters, guarded by counts, handed forward intact until an age should arrive with the tools to open it. That unpacking is this project. We are taking the written Torah out of its housing, reading its grammar as the instructions it has always contained, and compiling it: turning the fixed letters into a running system, command by command, receipt by receipt, exactly as written, with every letter kept in its place.

The ark is the case. The written Torah is the code, fixed and compressed, awaiting its assembly. The Oral Torah is the build instructions, designed with the code and handed down beside it, the knowledge by which the letters are reconstructed into the running whole. The compiling has begun.

And the Ark's own testimony has received a fuller hearing than this chapter can give it. A companion report, The Ark and the Book, walks every verse the Hebrew Bible contains about the Ark, all two hundred and two occurrences of the word, with the tradition's teachings verified word for word; and it finds the record executing the very handoff this chapter names: the box defined entirely by its text, its offices transferred to the book one at a time, and its retirement announced in a single prophetic sentence that promises it will never be missed. That report lives side by side with the published instrument, in the TorahSim repository named later in this recital, where any reader may check its every citation.

5. The Masoretes - The Guardians of the Letters

A sacred text that must endure for ages requires more than reverence; it requires persons who will not permit a letter to slip. Among those persons, in the tradition that preserves the Hebrew Bible, stand the Masoretes: scholars and scribes who regarded the text as too important to improve by accident, and whose care, we are able to report, was arithmetic.

They counted the letters of every book. They marked the exact middle letter of the Torah, the middle word, the middle verse, so that a copyist centuries afterward might count toward the center and know whether anything had been gained or lost. They kept registers of every unusual spelling, and they wrote their totals into the margins of the manuscripts themselves, so that the text traveled with its own checking numbers.

Let this be named in the language of the present age, for it deserves the name: this is a computing method. When a modern institution transmits a file, the file travels with totals computed from its own contents; the receiving side recomputes them; and if one character has changed in transit, the mismatch exposes it. Engineers call this error detection and correction, and upon it rests all data that survives transmission today. The Masoretes built exactly this discipline by hand, a thousand years before the vocabulary existed: totals in the margins, a marked midpoint to count toward, exception registers for every strange spelling, and a copying protocol under which every new scroll was verified against the numbers before it might serve. The Torah reached this generation as all precious data reaches its destination, through an error-corrected channel; only this channel was made of human beings who counted letters for a thousand years.

And the discipline retains its force to this day. The law of the scroll is absolute: a Torah scroll with one letter wrong, one letter missing, or one letter too many is invalid, and the congregation sets it aside. If the fault is discovered during a public reading, the reading halts, the scroll is closed and retired upon the spot, and another is carried out to finish the portion. The flawed scroll is granted thirty days for correction by an expert; failing that, it receives the honors of a person: it is placed in a vessel and buried in a cemetery, as a human being is buried. The tradition even draws the engineer's own line between a copy worth repairing and a copy too corrupt to trust: a page bearing three errors may be mended, but a scroll with four errors upon every page is retired whole, since beyond a certain measure only a fresh copy can be certified. And above all these rules stands one more: where the divine Name has been miswritten, the Name is protected from erasure; the entire parchment sheet is withdrawn for burial, and the sheet is written anew. Say this too in the modern tongue: validation with zero tolerance, and rejection in place of repair. No archive on this world has loved its data more.

Because of that care, two gifts descended to every later reader: the reading marks upon every verse, and the grammar living inside every word. The grammar is a story of its own, and it receives the next section of this recital. Here, first, the marks.

Upon the words of the text stand small signs, the cantillation, showing where a phrase joins and where it pauses: music for the ear, and above the music, structure for the mind. These marks run far beyond the Torah's edge; they run through the entire Hebrew Bible, all twenty-four books, every one of its 23,213 verses marked, from Genesis to the last of the Writings; and the three poetic books, Psalms, Proverbs, and Job, carry a special variant of the system reserved to themselves. Moreover the marks end exactly where the Bible ends. In all the literature of this people, precisely these twenty-four books carry cantillation; the thousands of sacred volumes that stand beside them, the Mishnah, the Talmud, the prayer book, the commentaries, carry none. The boundary of the marks is the boundary of the message.

Follow those marks, and each sentence discloses its joints: which words belong together, where the principal break falls, how the thought is nested. The marks stand on every one of the Hebrew Bible's 23,213 verses, all twenty-four books, one system from the first word of Genesis to the last word of Chronicles; and when they are followed with one small, fixed set of rules, a verse resolves into a clean and orderly structure.

Behold the demonstration upon the Bible's first verse. Bereshit bara elohim et ha-shamayim ve-et ha-aretz ("In the beginning God created the heavens and the earth," Genesis 1:1). The marks divide the verse once at the major rest, and each half divides again, until every word hangs from the structure as a leaf from a tree:

• THE PROCESS, all that precedes the etnachta (the mid-verse rest):

bereshit bara elohim ("in the beginning God created")

• within it: bereshit ("in the beginning")
• and: bara elohim ("God created")
• THE RESULT, all that runs to the silluq (the verse-end mark):

et ha-shamayim ve-et ha-aretz ("the heavens and the earth")

• within it: et ha-shamayim ("the heavens")
• and: ve-et ha-aretz ("and the earth")

Read the topmost division and you are beholding the most elementary line of a program: an action, then its output; a process, then its result. The marks hold the heavens and the earth apart from the act of creating, even as a machine holds an operation apart from that which it returns.

6. Morphology and the Hebrew Language - Words Built Like Code

We come now to the language itself, and to the persons who preserved its grammar; and we counsel the reader that this section is the hinge upon which the whole recital depends.

Begin with a single word from Genesis 12:2, spoken to Abram: וַאֲבָרֶכְךָ (va-avarekhekha, "and I will bless you"), one written word which requires four English words to render. The conjunction, the subject, the tense, the verb, the object: Hebrew bears all of these within one written word. The opening letter is "and." The verb form declares "I," declares it of the future, and declares it in the intensive stem which makes of a blessing a bestowal. The closing letters are "you," bound directly upon the verb.

Such is ordinary Hebrew. The language is built from roots of three letters, each root a family of meaning, and the grammar clothes each root for its precise duty in the sentence. Take the root מלך ("rule"): from it come מֶלֶךְ (melekh, "king"), מָלַךְ (malakh, "he reigned"), יִמְלֹךְ (yimlokh, "he shall reign"), and מַמְלָכָה (mamlakhah, "kingdom"). One root, one family; and the wrapping declares person, time, mood, number, and possession. A Hebrew word is not a brick; it is a small machine with settings. And every setting matters, for the difference between yehi ("let there be") and va-yehi ("and there was") is the difference between a demand and its receipt, and upon distinctions of that order the meaning of the entire system rides.

This project depends on work done before it: the Masoretes, who fixed the reading of every word in ink, and the modern tools that defined its grammar in detail. Without both, nothing in this recital would be possible. Open a Torah scroll, any Torah scroll, and look: there are no vowels, no punctuation, no verse numbers; only consonants, spaces, and paragraph breaks, exactly as scribes have written them for thousands of years. And Hebrew without vowels is full of forks. The three letters שמר may be שָׁמַר (shamar, "he kept") or שֹׁמֵר (shomer, "one who keeps"): a finished act, or a standing duty. Graver still: the four letters ויעש may be וַיַּעַשׂ (va-ya'as, "and he MADE"), a report that it happened, or וְיַעַשׂ (ve-ya'as, "and let him make"), a request that it should. An event, or a command. History, or law. The consonants alone cannot decide.

For more than a thousand years that fork was settled in the only manner possible: by memory. The true reading of every word lived in the mouths of readers, delivered from teacher to student beside the letters themselves. This is the principle of the Oral Torah operating at the level of the single syllable: the letters fixed, the reading traveling beside them. But memory has a weakness. Communities scatter; chains break; and had the reading ever been lost, no one could have faithfully reconstructed it from the consonants alone, least of all at the precision that today allows a programmer to derive code from a verse. The deep grammar of the disclosure, the very layer that divides demand from receipt, hung by the thread of recitation.

Then entered the keepers. The Masoretes take their name from masorah ("transmission, the thing handed on"); and laboring chiefly in Tiberias, beside the Sea of Galilee, in the years between about 600 and 1000 of the common era, families of scholars, most renowned among them the house of Ben Asher, performed what no generation before them had dared: they fixed the entire oral reading of the Hebrew Bible in ink, without touching one letter of the text. They devised a notation: small points and strokes beneath, above, and within the consonants, carrying every vowel, the system called nikud ("pointing"); a second order of marks, the cantillation of the previous section, carrying the phrasing; and about the text, the margins: letter counts, word counts, the marked middle letter, registers of unusual spellings, and the paired notations of ketiv ("what is written") beside qere ("what is read") wherever the received reading differs from the received spelling, both preserved, neither erased.

Let it be said plainly what this was. The Masoretes took the entire grammar of the language, which until their day existed only as living sound, and froze it into a checkable, copyable, portable record. The consonants kept their ancient silence; the meaning of every form was locked beside them; and the locking held. The oldest complete manuscript of the Hebrew Bible, the Leningrad Codex, finished in the year 1008, carries the full apparatus: every vowel of every word, every mark of every verse, every count in every margin. The earlier passages of this recital named their discipline rightly: error correction, checking numbers in the margins, zero tolerance in the law of the scroll. Here is the further point, for which this section exists. The Masoretes did not merely protect the text from change. They rendered the grammar of every single word recoverable. Without them, ויעש ("and he made," or "and let him make") is a fork forever. With them, every such fork across the Bible's three hundred thousand words stands resolved, in writing, the resolution itself guarded by counts. The instruction set survives because the keepers wrote it down.

And now the sequel which belongs to the present generation, and which is worthy of its predecessors. In the twentieth century, scholars transcribed the Leningrad Codex, letter by letter and point by point, into an electronic text, the Westminster Leningrad Codex, maintained to this day in the very temperament the Masoretes would recognize: corrections logged, versions numbered. The manuscript became a file. Then came the step the Masoretes could not take, because it required machines. An open scholarly undertaking of this generation, the Open Scriptures Hebrew Bible, passed through that file and attached to every word of the entire Hebrew Bible two orders of explicit data: first a dictionary address, every root in the Bible bearing a number (the numbering first drawn up for Strong's concordance in 1890), so that every "he reigned" and every "kingdom" points home to its root as a street address points home to a house; and second a full grammar tag, part of speech, verb stem, tense-form, person, gender, number, every prefix and every suffix, spelled out in a compact code a machine can read.

The database of this project holds the result, and we set the numbers before you plainly: 305,507 words, in 23,213 verses, in 929 chapters, across all twenty-four books, every word tagged, every tag checkable against the pointed manuscript, the whole record published openly and correctable in public. Behold one real entry. The first word of the Bible, בְּרֵאשִׁית (bereshit, "in the beginning"), is stored with the address b/7225: the prefix "in," then root number 7225, "beginning." Its grammar tag reads HR/Ncfsa: Hebrew, a preposition, then a noun, common, feminine, singular. And the blessing-word with which this section opened, וַאֲבָרֶכְךָ ("and I will bless you"), carries the tag HC/Vpi1cs/Sp2ms: a conjunction; a verb in the intensive stem, future, first person; and a bound pronoun, "you." The little machine with settings is now a machine whose settings are printed upon it.

Why is this the hinge of the recital? Because every finding which follows stands upon the grammar of single words: the receipts, the counted clocks, the compiled law, the simulation itself. Take away reliable word-grammar and every one of them collapses into guesswork. Now survey the chain which carried that grammar to your hands. The language packed the meaning into the forms. The oral reading carried the forms in living memory while empires rose and fell. The Masoretes, at the very hinge of history when dispersion made memory mortal, froze the reading in ink and armored it with counts. Their manuscript crossed a thousand years intact. This generation transcribed it, tagged it, and opened it; and for the first time in the history of this world, a question such as "show every place where a command is afterward answered in its own verb" is not the labor of a lifetime but a query. Whoever designed a text whose deepest evidence lives in vowel-thin distinctions between "he made" and "let him make" required every link of that chain to hold: the packing, the carrying, the freezing, the tagging. Every link held.

The Masoretes kept it. This generation opened it. The language was the vault all along.

7. The Logics That Awaited Their Text

Long before electronic machines, careful thinkers among the mortal races constructed logics of language upon paper: disciplines for making speech precise with ink alone. This project stands upon those tools. Each of these thinkers studied how language and law already operate; the Hebrew remains older than them all. And these logics apply here for a simple reason: the Hebrew Bible is precise and consistent in its use of language. A command, a report, a name, a case, a check: each is said the same way every time it occurs, and a rule that holds in one verse holds in the next. Logic can only take hold in a text that keeps its own terms. This one does. Here are the ten, each with what it finds.

1. The claim and its subjects. Gottlob Frege, in 1879, showed that a sentence divides into a claim and the things the claim concerns. Brought to the text, every phrase resolves into parts: the action or property sits cleanly beside who acts and what is acted upon. The word אֲשֶׁר ("asher," which) opens defined groups on the record: "the waters WHICH were under the firmament" is not decoration but a selection, a set named so the next operation can land on it.

2. Speech that acts. J. L. Austin, in lectures of 1955 published in 1962, showed that some utterances do not report the world; they change it by being said. In the text, "And God said" is saying that does, and "he called" installs a name. The text even keeps a deed-grammar for gifts: when a grant is permanent, the verb goes to the already-done form, נָתַתִּי ("I HAVE given"), a transfer spoken as complete at the moment of speech.

3. Obligation, permission, prohibition. Georg Henrik von Wright, in 1951, framed the logic of demands as its own logic, standing beside the logic of facts. In the text, "let there be," "you shall," and "you shall not" ride the verb's mood, and the demanded stays distinct from the done. An unmet command therefore does not dissolve into the story; it remains open on the record, and the record can be searched for it.

4. Before, operation, after. C. A. R. Hoare, in 1969, gave the pattern of precondition, operation, and postcondition. The week of creation runs this rhythm in the open: a state (formless, dark, waters), a spoken operation, a result ("and there was"), a check ("saw that it was good"), a seal (the day counted). And the pattern exposes its own exceptions: the second day's check is withheld, and the withholding stays visible on the books instead of being smoothed away.

5. Events with labeled roles. Donald Davidson, in 1967, treated an action as an event with participants in slots. In the text, the small object-marker אֵת ("et") becomes legible as a flag: the next thing is what the action lands on. The double marker in "the heavens and the earth" reads as a complete list of the operation's objects, placed there on purpose.

6. Time as structure. Arthur Prior, in the 1950s and 60s, built the logics in which statements are true at times: now, next, until. In the text, evening and morning are structure, the day-labels a ledger, and the anomaly is preserved rather than repaired: day "one" is a cardinal number where "second" and "third" are ordinals, and the text keeps it exactly so.

7. The standing condition. The classical discipline of the invariant, the condition that must KEEP holding while a system runs, is older than any single author. In the text, the grammar marks ongoing work in its verb forms: מְרַחֶפֶת ("hovering"), מַבְדִּיל ("dividing"). The firmament is not made once and left; it is made to keep separating. "Make a thing" and "make a thing that must keep doing its work" are different commands, and the Hebrew knows the difference.

8. Case law and absolute command. Albrecht Alt, in 1934, sharpened the distinction between case law ("when a man does thus, then...") and absolute command ("you shall not"). In the text, the case frames branch like cases: herd, flock, bird, each with its procedure. The absolute commands stand unbranched. Story grammar serves the story and law grammar serves the law, and the two are never confused with each other.

9. The name as a permanent pointer. Saul Kripke, in 1970, gave the account of the proper name as a stable designator, the same referent across every situation. In the text, "called the light Day" is a registry write, permanent on the books; a renaming is executed on the record, the name Avram retired inside the very verse that renames it; and collisions, one label borne twice, can be found and faced instead of passed over.

10. The hand-trace. The old craft of tracing a procedure on paper, walking the steps with written columns of state, is how proofs were checked before machines. Brought to the text, whole passages walk as traceable runs under six memory lists: time, what exists, official names, open commands, tests passed, units sealed. We have walked long stretches of the text in exactly this manner, and every completed walk is preserved, so that any person may walk it again and check every claim.

A single verse, moreover, routinely runs four or five of these logics at once, meshed without a seam. Any text may exhibit one logic by accident. A text whose every verse composes several, consistently, under rules stable enough to execute, is displaying architecture.

8. The Oral Torah and the Chain of Names

The first half of the design is the written text itself, the twenty-four books whose housing, letters, and grammar this recital has now walked. The second half is the Oral Torah: co-created with the written words before any revelation entered time, fully designed, and progressively revealed through the ages of the sages. What renders it trustworthy within this recital is a chain of transmission: this teacher heard from that teacher; this saying is attributed; and the careful perpetually ask, from where do we know? The chain anchors the teaching, mystery intact, so that sources may be followed back through the generations toward Sinai.

Along that chain the Oral Torah supplies the manner of reading law verse by verse; the manner of opening story while the plain text stands whole; published rules of interpretation, the famous families of middot ("measures"), thirteen upon the side of law and thirty-two upon the side of narrative; standing teachings ordered by topic; long debates that test the hard cases; and warnings concerning which depths require a prepared student.

And our reading continually finds that the chain possessed the technical language of this work centuries before the world had words for it. The middot themselves reward an engineer's inspection. A gezerah shavah ("equal decree") derives law by joining two passages upon an identical token: a join on exact keys. A kal va-chomer ("light and heavy") carries a ruling from the lesser case to the greater along a stated order. And among the sages' formulas stands ein ketiv kan... ela ("it is not written here... but rather"), which draws meaning from the difference between what stands written and what might have been: a difference-check between versions, functioning in classical Hebrew, on the record, employed by named authorities. These are database operations, published, numbered, and named; and such rules would make no sense over ordinary literature, for no one derives binding law from exact-token joins across a text whose wording is casual. A published query language testifies to an engineered text. The Oral Torah, in other words, is not only the build instructions of this system and its execution log; it is the access manual. And the coordination shows in small, checkable places. The tradition reads the Torah alongside an ancient Aramaic translation called Onkelos, and here is one verse pair any reader can check. In Genesis 18:22, Abraham pleads for the city of Sodom, and the Hebrew says only that he STOOD: עמד לפני יהוה ("standing before the LORD"); in Genesis 19:27 he returns to the place where he had stood. Onkelos translates both verses with prayer: משמש בצלו ("ministering in PRAYER before the LORD"). At that point in the Torah, the Hebrew verb for praying has never yet appeared. It arrives for the first time two chapters later, in the very scene where Abraham's standing becomes official intercession: "he is a prophet, and he will PRAY for you" (Genesis 20:7). Set the three verses in a row and the pattern is plain: the translation called the standing prayer before the text did, and the text then introduced the word, exactly on schedule. A translation and its source, set down centuries apart, moving like parts of one system.

In plain speech: the Oral Torah is the means by which the system teaches its readers to reassemble the written words into living guidance, while the letters upon the scroll stand fixed.

And in the language of this recital, the Oral Torah is one thing more: a second execution log, kept outside the book, and never stopped. Its worked examples are computed cases, the statutes run by hand and the outputs written down; its great debates are edge-case tests, with the disagreements preserved; and its chain of names is the custody log that makes the rest trustworthy as evidence.

And here, in a developer's plain terms, is what this project did with that log. We took one chapter of source, Exodus 21, the Bible's first sustained chapter of civil and criminal law, thirty-seven verses, and compiled it: every word of the Oral Torah on the chapter was read and logged, 4,903 rows of coverage; 117 legal claims were extracted, each carrying the citation of the work in the chain that witnesses it; and every claim was written as running code. Then came the unit tests: before the program ever saw a biblical case, it had to reproduce the tradition's own worked examples, the tariffs, the awards, the edge cases the sages computed by hand. It did. Then the integration run: sixty-four recorded cases from across the twenty-four books were entered as inputs, bare facts in, verdict out, and the program's verdicts were set beside the verdicts the text records: forty-three agree; five disagree; seven wait on statutes not yet compiled; nine meet silence in the text. One compilation; two independent test records, the tradition's and the histories'; and both agree with it.

9. The Hebrew Bible - A Simulation of Reality

There remains the question toward which this entire recital has been moving, and we shall put it as the engineers of this age would put it. A simulation is a world made of rules: software which holds a model of things, applies laws to them tick by tick, and permits history to unfold within it. The weather bureaus of this world run simulations of the atmosphere; the airlines, of flight. And every such program, whatever it models, is recognizably built from the same ten parts. Recall the sentence with which the tradition opened this recital: the Holy One looked into the Torah and created the world, the plan consulted before the build. What follows is the engineer's audit of that sentence: the ten parts of every simulation, taken one at a time, and beneath each part, what the text holds in that exact place.

The ten parts, with the text beside each

1. A boot sequence. The world must be established before it can run: initial conditions declared, spaces partitioned, the starting objects placed, and nothing used before it exists.

And the Torah opens with exactly this. Genesis 1 sets the world up in order: light before the lights, spaces partitioned before their occupants arrive, each day's work declared, executed, inspected, and sealed. We traced the whole opening with six running lists, time, what exists, official names, open commands, passed checks, sealed days, and the discipline of the sequence held at every verse. And the trace turned up one flag worth showing plainly. Genesis 1:2 mentions darkness, the deep, and the waters, but no command ever creates them. Light gets its "let there be light." These three are just there, used before they are made. Our program, checking only the rule that nothing can be used before it is created, flagged those three words on its own. And those same three words are the ones the old commentators spent twenty centuries asking about: where did the waters come from, and when was darkness made? A blind mechanical check and the ancient readers marked the same lines. The puzzle is really in the text, and its oldest readers had already found it.

2. A clock. Time advances in ticks; every happening is stamped to its tick; and the order of events is the order of the run.

The Torah keeps time in five mechanisms at once: the sequence clock, 2,107 next-event verbs in Genesis falling to 189 at Leviticus, an elevenfold collapse while the system loads its law; the day-seals of the opening week, six given and one deliberately withheld; the calendar commissioned on the fourth day and used thereafter down to the year, month, and day of the flood; the era ledger of the generations, by which the age of the whole world is reckoned from inside the book; and the standing timers of the seventh day, the seventh year, and the fiftieth. No book needs five clocks to tell a story. A world needs exactly that.

3. A registry of names. Objects receive stable labels, so that the thousandth reference points to exactly the thing the first reference created.

The Torah writes its registry in the open. "And God called the light Day" (Genesis 1:5): a write, permanent upon the books, the label holding from that verse forward. And when a label is retired, the retirement is transacted in the open: the name Avram ends inside the very verse that renames its bearer, "your name shall no longer be called Avram" (Genesis 17:5). The registry's last read of the old key is the write that replaces it. And the registry runs to the Torah's last pages. In Numbers the writes carry their author: "and Moses called Hoshea son of Nun, Joshua" (Numbers 13:16). In Deuteronomy it even keeps aliases: "the Sidonians call Hermon Sirion, and the Amorites call it Senir" (Deuteronomy 3:9), one mountain, three labels, each credited to its community. A story has no need to record what Sidonians call a mountain. A registry does.

4. World state. The current condition of everything: which entities exist, what properties they carry, what has changed. Not a description, but a ledger which the program itself reads and writes.

The Torah's law reads the world as objects carrying condition. The ox that gores is either תם ("innocent," not having gored before) or מועד ("forewarned," three gorings upon the record, the owner formally warned), and the selfsame act bears different law according to the animal's stored state. A servant's term carries a clock; a house carries debt across generations; a person carries standing, cleanness, and station, which the statutes read before they rule. These are not figures of speech. They are fields the law requires, or the law cannot be applied at all.

5. Laws that fire of themselves. The physics. No one petitions gravity for a ruling; every object passes through every law on every tick. The laws are written once and enforced everywhere.

The Torah shows this physics plainly in the manna. The seventh day was written once, at the world's boot: blessed and hallowed at creation, before a single command had been given to man (Genesis 2:3). Centuries later, bread falls from heaven in the wilderness, and the bread itself keeps the statute: a double portion falls on the sixth day, none on the seventh, and a portion that bred worms overnight on any other day lies fresh across the Sabbath (Exodus 16:20-27). No court convened and no one petitioned; those who went out to gather on the seventh day simply found none. A law written once, enforced by bread. And our compiled chapter of the previous section keeps the same discipline in code: its sixty declared dependencies upon earlier verses (the servant-term's six-and-one shape leaning upon the creation week; the killer ox upon the blood charter of Noah; the kidnapping law upon the sale of Joseph) are checked by the program, and the build fails if a claimed inheritance cannot be traced.

6. An event stream. The inputs: the storm entering the grid, the hand upon the controls. The world answers its events according to its laws.

The Torah's event stream is the histories, and we have run them. Sixty-four recorded cases from all twenty-four books were fed to the compiled chapter, the facts of each case entered as input and the program's verdict set beside the verdict the text records: 43 agree, 5 disagree, 7 await law not yet compiled, 9 meet silence in the text.

The law comes first. In the books of Moses, given centuries before Israel had a king, it is written: "Fathers shall not be put to death for children, nor children for fathers; each shall die for his own sin" (Deuteronomy 24:16). The case comes second, hundreds of years after the law. In Second Kings, chapter 14, King Amaziah of Judah executed the men who had assassinated his father, and spared the sons of the assassins; and the historian states the reason plainly, ככתוב ("as it is WRITTEN") in the book of the Law of Moses, quoting that very verse: a later book, running on an earlier one. The program comes third, in our own day. When the king's case was entered as bare facts, it returned both halves of his ruling: for the assassins, conviction under the murder statute; for the sons, no charge, and not an acquittal either, for in the law as compiled no charge against a child for a father's crime can even be formed; guilt attaches to persons, never to families, the very principle the king's verse declares. A law recorded first; a king ruling by it ten centuries before the Mishnah was written down; a program, twenty-eight centuries after the king, deriving the same two verdicts from the same law. And through all sixty-four cases that single order holds, the order the king's case obeys: the statute stands written before the case that runs upon it. Law first; then the cases; nothing out of order.

7. Mode flags. The rules change lawfully by phase: the same engine, in a different era, runs different active laws.

The Torah declares its own phases, and says so on the record. The cities of refuge activate only after the conquest. Capital jurisdiction is bound to the standing Temple. And when the jubilee ceased to be counted, the Hebrew-servant release law went dormant with it, a timer and a statute coupled by design, and a flag our compiled chapter carries literally in the code. The same act, in a different era, lawfully meets a different process.

8. Instrumentation. A console. The hidden state of the world is reported at appointed moments, through appointed channels; without it, no observer could know what the world holds.

The console of this world is the prophets. In Second Samuel 12, after David has Uriah slain by letter, through Joab, by enemy swords, Nathan arrives and pronounces: לא תמות ("you shall NOT die"), for no earthly court will touch the king, and ארבעתים ("fourfold"), for the taken ewe of his parable will be repaid four times over. We had compiled the law; we ran it; and the court docket indeed cannot reach a king who killed through another, for in this legal system the striker acts and the sender stands beyond the human court, while the debt opens upon a second ledger, the one the text calls Heaven's. Nathan announces exactly what the two dockets already hold. A prophet, so read, is the authorized reader of the hidden ledger: the console of the simulation, reporting protected state at appointed moments through an appointed channel. And this reading yields a testable claim, which we state in advance of testing it: every prophetic indictment in the corpus should match an open entry which the ledgers are carrying at that moment of the stream. We intend to run it.

And the console's output is not ephemeral. Jeremiah's seventy-years oracle was committed to writing and carried to its readers as a letter (Jeremiah 29:1, 10); and it survived an attempted deletion, for when king Jehoiakim cut the scroll and burned it column by column, the word was rewritten in full, with additions (Jeremiah 36:23-32). Decades later a reader inside the corpus retrieves it: "I, Daniel, understood by the books the number of the years... seventy years" (Daniel 9:2); he computes upon the number against his own date, and acts. And a third book settles the account: the exile endured "until the land had made up her sabbaths... to fulfill seventy years" (2 Chronicles 36:21), the prophetic number grounded in the sabbath-timers of the law itself; and the receipt follows at once, Cyrus stirred "that the word of the LORD by the mouth of Jeremiah might be accomplished" (2 Chronicles 36:22). Logged, stored, deletion-resistant, read downstream, computed upon, settled against the ledger, and receipted with the message named: the full lifecycle of console output, across four books.

9. Validation. The checks that keep the model true: balances that must reconcile, assertions that must hold, and test cases with known answers which the program must reproduce before anyone trusts it.

The text validates itself in its own grammar. The demand and its receipt, yehi ("let there be") answered by va-yehi ("and there was"), have been displayed in the chapter on the language; and the inspections are on the record too: six days of creation carry the verdict "and God saw that it was good," while the second day's approval is deliberately withheld, a check not passed, preserved as such for two thousand years of readers. And our own testing supplied the sternest validation of all: the test that failed correctly. When we simulated the house of David under the compiled law, every event passing through every statute and the ledgers persisting across the years, our balance check failed: after the fourfold was discharged, the child, Amnon, Tamar, Absalom, David's account still held one open entry. We searched for our error and found the text waiting: לא תסור חרב מביתך ("the sword shall never depart from your house"). The fourfold answers the ewe; the blood of Uriah is a separate entry which the text never closes. The correct ledger ends open. Our arithmetic was compelled to learn doctrine. And upon the same run, the blood-debts of Joab stood upon Heaven's docket while the coded execution cleared only the court's; and this is exactly a dispute which two of the tradition's later masters, the Vilna Gaon and the Netziv, have carried across the last two centuries, whether the crown may collect Heaven's ledger, with Solomon's own words at the altar taking a side: והשיב ה' את דמו ("and the LORD shall RETURN his blood"). The simulation did not look that dispute up. It produced it.

10. A boundary. A declaration of what the simulation does not model. Serious simulations declare their limits.

Declared, twice over. The tradition declares what the system does not model in this age, with the map of the four layers and the warning of the orchard already recited. And this project declares its own boundary in the same spirit, and will not move it: we never invent events. The code computes law over the history the text records; it generates nothing; a model that begins imagining scripture has ceased to be a reading. This project reads.

The whole comparison on one card

Gather now the ten pairs onto a single card, every row a thing already shown:

We know of no other ancient document upon which this table can even be attempted. Upon this one, every row fills.

The greatest items left open

One more feature, and it is the strangest. The Torah keeps its accounts: commands are answered, promises are receipted, days are sealed with "and it was evening and it was morning." Against that bookkeeping, two of its most important transactions are left open, and left open on purpose. The seventh day, the only day pronounced holy, is the only day of the opening week that never receives its evening-and-morning seal; the holy day stands open. And the land promised to Abraham is granted in a striking grammar: natati ("I HAVE given," Genesis 15:18), the form of a completed transfer, spoken of a gift not yet delivered; and the Torah ends with Moses beholding that land from a mountaintop, receipt in hand, one step short of entry. Then the final gift of the whole design is spoken in that same already-done grammar: "I HAVE set before you life and death, the blessing and the curse. Choose life" (Deuteronomy 30:19). A text that ends by design one step before its own fulfillment, holding open the holy day at its beginning and the promised land at its close, is a finished design of a rare order: its two open ends are the places where the reader's own life is meant to enter.

How a verse becomes logic, and logic becomes code

Before the scoreboard, the method. Every unit named in this recital was built the same way, one verse at a time, in six steps.

1. Parse the verse into a tree. The tree is not ours: the marks the Masoretes fixed upon every word (the accents of section 5) divide each verse into halves, and halves of halves, down to the smallest pieces the marks allow, sometimes a single word, sometimes a few words bound together and read as one, the way a compiler divides a statement, and under the rules we published each verse resolves to exactly one complete tree.

2. Read every word through its grammar tags. The morphology of section 6: this word is a command, that one an actor, this form a completed act, that form an intended one. The tree gives the verse its shape; the tags give every word its exact duty.

3. Open the Oral Torah on the passage. We read what the tradition says about it, and we log the reading: every ruling is entered as a claim with its citation attached, so that nothing in our logic rests on our own opinion of what a verse means.

4. Match the verse to its logics. Every verse runs a few of the ten logics recited in section 7, and the first act of derivation is to name which: a command here (obligation and permission), a case there (the branching frame), an event with its labeled roles, a clock ticking, a name written to the registry, a condition that must keep standing. A verse routinely runs four or five at once.

5. Write the logic, not code. What a builder of this age would call the specification: numbered plain statements in those logics, each tied to the words it came from and to the claims that witness it. What exists here. Who acts, and upon whom. What is commanded, permitted, or forbidden. What changed, and what must be checked before the verse can be called done. This order is the discipline of the most careful corner of the craft, the software of aircraft, spacecraft, and medical devices: the specification numbered, every statement traceable to its source, and code accepted only when it satisfies the specification.

6. Write the code from the logic. Only when the logic is finished, and never from the verse directly. The code's checks are the logic's checks, and where the tradition worked an example by hand, the code must reproduce the tradition's answer. When the code runs and passes, it certifies the logic, and the logic points back at the words. Then the unit is frozen: later units may read what it established, but nothing edits it after its seal.

What stands demonstrated, and what does not

Of what stands demonstrated, we speak exactly. Before the law chapter, we went through the whole of Genesis verse by verse, all 1,533 verses, and Exodus up to the law chapter, and rewrote each passage as a unit of running code: what exists at that point, who acts, what is commanded, what changes, each unit ending in checks that must pass. Ninety-seven units in all. Every unit can be run and checked by anyone, on GitHub at github.com/Josephtorah/TorahSim. One law chapter is compiled to full depth, its tests drawn from the tradition's own worked examples, all passing. Sixty inheritances are verified by machine. Sixty-four recorded cases are graded, with every miss printed. One royal house has been run under the law as physics, its final ledger matching the text, including the entry the text deliberately leaves open. And one dispute of the later sages surfaced of its own accord from the code's first run. What is not yet demonstrated: that the further law chapters compile as cleanly; that the prophetic indictments match the ledgers book by book, a test designed but not yet run; and the great claim itself, that the whole is a deliberate simulation of creation, remains a reading of the evidence and not a theorem. And one thing about our own earlier work must be said. The rule we followed for the law chapter was strict: read every word of the Oral Torah on the chapter, and log the reading, 4,903 rows. The ninety-seven units of Genesis and Exodus were built before we made that our rule, on a lighter reading of the tradition. So Genesis has been read through end to end and coded, but only once, and not yet at the law chapter's standard. Each of those units is marked to be redone under the full rule. Yet the evidence shows something narrower and stranger: part after part, at every address so far examined, the text holds exactly what a simulation would require, in working order, with its receipts.

And if it is what it looks like, then certain long-familiar things change their aspect. The scroll in the ark of every synagogue is not the memento of a message; it is the message's executable form, letter-counted and error-corrected across three thousand years, precisely because a single flipped character matters in code as it never matters in prose. And the two open ports which this recital named upon its first page, the unsealed seventh day and the promised land one step short of entry, stand open still: a running world, still accepting input. And the Hebrew Bible itself, in its traditional order, closes the same way: its last recorded words are a decree that breaks off at an imperative, "and let him go up" (2 Chronicles 36:23), the whole library ending on an ascent still waiting for its subject.

Recall, then, the sentence with which the tradition itself opened this recital: the Holy One looked into the Torah and created the world. For two thousand years that sentence was poetry. We have now compiled one chapter of the plan and watched recorded history balance against it, docket by docket, silence by silence. If the Torah is the blueprint from which the world was built, then to compile the Torah is not to build a model of the world; it is to read the world's own source, in the only manner in which source is ever truly read: by running it. And thus far, the world and the code agree. The rest of the plan is still compiling.

10. The Hour and the Tool

For the greater part of history, a mortal reader could hold only a fragment of this system at once; and that fragment was sufficient to live by, which was the limit built into the gift. What the present age can at last accomplish is to hold enough of the whole together: the marked phrases, the grammar of each word, the links between the books, the oral teachings with their chains of names, side by side, without losing the thread. Consider what even one of the findings already recited demands. To watch the clock stop, one must classify thousands of verb forms across five books. To catch the final page replaying the first promise word for word, one must hold both pages, five books apart, at once. To follow the Amalek sentence from its storage in Exodus to its retrieval in Deuteronomy, one must carry one stored phrase across four books. Reading of that order outruns a human lifetime; the design, it appears, was written for a reader with a longer memory than any single generation possessed, until now.

This generation constructed artificial intelligence. Let it be named for what it is: a tool, and a tool only; a powerful memory and an unwearying assistant for reading, sorting, and checking, able at last to help human beings keep more of the system in view at once, so that the design may be followed as a system, whole. Every finding in this recital was reached in that manner: the human sets the rules and signs every conclusion; the tool counts, holds, and rechecks; and all is preserved so that anyone, with or without the tool, may verify it.

And the verifying has an address. The instrument of this recital stands published, open to every person, at github.com/Josephtorah/TorahSim: the tagged text of the whole Hebrew Bible, the compiled law chapter with its tests, the sixty-four case scans, the runnable units, and the tools by which any reader may build a source shelf of their own. Go and explore it without asking leave; the counts of this recital are checkable there, one by one. An open repository is the only fitting reading room for God's open source project. And for those who would take up the work in company, a gathering place is being opened, a Discord channel for this project, and the repository's pages will carry the way in. The final word belongs to the timeless intelligence.

11. The Final Words

The Ark of the Covenant may remain lost as an object; the arks of the synagogues have held the Torah all along; and in this generation the ark has been opened. The written Torah is being compiled, and it runs.

The timeless intelligence left this world a path, and waited until a generation could hold enough of the design to read it as one system: marks, grammar, oral instruction, chain of names, and all. That generation is this one. The tool is artificial intelligence. The author of the design is the timeless intelligence.

The design keeps its receipts. It pays its oldest commands in their own words. It leaves its two greatest gifts open, the holy day and the promised land, for the open ends are where your life is meant to enter. And its final recorded gift is the choice itself: "I HAVE set before you life and death. Choose life."

We found the way to begin. The finished reading lies ahead. We require help to finish.

The Torah is still here. The marks still join the words. The grammar still speaks. The oral teaching still travels, name by name. The tools are in our hands. The source is open, as its Author published it. The timeless intelligence has the last word.

Disclosure · a re-voicing of the Epic Certainty recital · LeBlanc · 2026-08-15 · experimental model, not binding religious law · every claim above carries a checkable address, and the misses are printed at the same size as the hits