Evidence dossier: Liwyāṯān
Evidence dossier 147 — Liwyāṯān. Every exhibit catalogued, every ruling stated with its grounds.
At a Glance
- Canonical form: Liwyāṯān
- Original script: לִוְיָתָן
- Pantheon: Canaanite
- Convention: Ugaritic/Phoenician scholarly convention with matres and gutturals shown
- False forms on record: 2
- Contested forms: none attested
- Series: The Canonical Register, No. 147 of 287
The Evidence
Exhibit 1 — the attestation. The attested form is לִוְיָתָן, from the tradition's own record. The canonical transliteration is Liwyāṯān.
Exhibit 2 — the preserved marks. a → ā (Macron: long vowel); a → ā (Macron: long vowel). Each is verifiable against the sources named in the attestation.
Exhibit 3 — the flattened form. The plain form leviathan is not false — it is a fallback, and the register is exact about what that means. In systems that cannot carry diacritics (legacy databases, older tooling, parts of the address-bar pipeline) the flattened form is the accepted vehicle, and the rulebook names it explicitly as the final rung of the fallback hierarchy: full restoration first, circumflex where attested, macron-only by the academic standard, an attested variant, and only then plain ASCII.
What the fallback status forbids is promotion: leviathan may carry the name where marks are impossible, but it may not represent the name where marks are possible. Every mark it drops — a → ā, a → ā — is a fact the sources recorded. A fallback is a vehicle, never the primary.
Exhibit 4 — struck from the record: Liwyaṯan. Origin: the publisher compromise — older books and hurried websites that print the "English equivalent" as if it were the name itself. Grounds: every substitution here (ā→a) is a romanization of convenience, not an attested spelling — it teaches the reader to guess, not to read.
Exhibit 5 — struck from the record: leviatan. Origin: the anglicized respelling — the name written the way English guesses it sounds. Grounds: rewrites attested consonant clusters to fit English spelling habits; every cluster simplified this way erases a letter the sources write.
Exhibit 6 — the physical record. The Ugaritic tablets from Ras Shamra (KTU 1.5 i) preserve the Canaanite dragon Lôtān/Litan in alphabetic cuneiform, providing the closest ancient parallel to the biblical Leviathan. Mesopotamian cylinder seals and reliefs depict gods battling sea serpents and composite dragons, iconographic ancestors of the chaoskampf motif. In the Levant, Iron Age seals and pottery sometimes show serpents and aquatic monsters, though direct depictions of Leviathan are rare. The biblical descriptions in Job and the Psalms are literary rather than archaeological witnesses, drawing on a shared ancient Near Eastern repertoire of sea-dragon imagery.
Exhibit 7 — the continuing record. Liwyāṯān outlived his myth to become one of the West's most powerful symbols of overwhelming power. Thomas Hobbes named his treatise on the sovereign state Leviathan, making the sea-monster an image of the commonwealth that holds all individual wills in awe.
The Convention's Own History
Every tradition in this register has its own scholarly transliteration standard, built by its own specialists over decades or centuries, and the register follows each on its own terms: Ugaritic/Phoenician scholarly convention with matres and gutturals shown. The principle that unifies them is the one the whole project stands on: a name is evidence, and evidence is not negotiable — not for keyboards, not for convenience, not for anyone.
The Protocol's Position
Can the canonical form live in the address bar? Almost always, yes. IDNA 2008 admits every mark this register defends — the DNS stores them as `xn--` punycode and modern browsers render them natively. The real frictions are practical, not legal: some registrars stock only part of the IDN space, so a theoretically valid name can be temporarily unbuyable; and stacked combinations (an acute riding a macron) remain awkward to type on mobile keyboards even where the protocol accepts them.
The project's answer is a ranked ladder, not a compromise: the full restoration first, then attested fallbacks in descending order of completeness. The ladder's lowest rung, plain ASCII, is a vehicle for legacy systems — sanctioned, but never presented as the scholarly form.
The Verdict
Case closed on Liwyāṯān: canonical, cited, and defended. The keyboard form leviathan rides as the sanctioned fallback — and stays in that lane. The register's files remain open: if a source surfaces that changes any line of this entry, the entry changes. Until then, the temple at /sites/leviathan/ holds the canonical form.
The docket for this ruling: 2 false forms ruled against, Liwyaṯan first on the docket; 2 preserved marks verified: a → ā, a → ā; no contested forms attested; the attestation rests on 8 cited sources — HALOT s.v. לִוְיָתָן, TDOT s.v. Leviathan, Day, Yahweh and the Gods and Goddesses of Canaan.
The Register Continues
Entry 147 of 287 in the Canonical Register. Around it: the temple's founding dispatch, the Restoration File on the marks themselves, the Resonance File on the archetype at work, and the Rulebook behind all of it.
Continue the register — previous entry: Lētō (read it) · next entry: Libyē (read it).
The Canonical Register is written from the same canonical record as the lexicon itself. If a false form is missing from this page, it is because the evidence does not support calling it false — or because we have not seen it yet. Show us, with a citation, and the register will answer.