PuniCodex

The Canonical Register · No. 399

On Onuris: a letter to a colleague

War, Hunting

ASCII-equivalent form Onuris
Onuris — War, Hunting
By PuniCodex Team · · 4 min read

On Onuris: a letter to a colleague

A letter to a colleague, 31 July 2026 — on the name Onuris, and on the forms that keep failing it.

Your note said, roughly: surely the marks are a nicety. Permit me to use Onuris to show they are not.

First, the attestation. The attested form is 𓏎𓈖𓁷𓂋𓏏𓈐𓅆, from the tradition's own record. The canonical transliteration is Onuris.

Say it aloud as the sources heard it: “ON-yoor-iss” The marks are what carry that sound to a reader who has never heard it spoken.

On the plain form — and I want to be precise, because you pushed on this. The plain form onuris differs from the canonical Onuris only by convention of display — case, not content. It is acceptable everywhere: in legacy systems, in plain-text citation, in the DNS itself. What is not acceptable is what follows in the register: respellings that change the letters, not just their case.

One more thing, because it always surprises: the name did not stay home. Onuris is the Thinite doublet of Shu: same retrieval-myth, same air-theology, localised and armed. The Greeks knew him as Anuris and left him largely unmapped — no Olympian quite covered ‘the husband who fetches’ — while Egyptian theology folded him contentedly into the greater Shu.

And it never stopped working. His myth survives as one of the most charming of the Eye-cycle variants — the only one where the divine embassy ends in marriage. The Thinite nome’s devotion to him outlasted its political weight by millennia; and his name, in the Greek form Anuris, wandered into the magical papyri as a word of power for recovering what is lost.

The Convention's Own History

Egyptological transliteration exists because hieroglyphs write consonants, not vowels. The characters ꜣ (aleph) and ꜥ (ayin) are consonants — a glottal reed and a pharyngeal grip — and rendering them as vowels does not "simplify" the name, it deletes consonants from it. The conventions in use descend from nineteenth-century decipherment and the standardized Manuel de Codage: ḥ, ḫ, ḏ, ṯ each mark a distinct consonant the Egyptian wrote and a modern reader must not merge. When this register defends them, it defends the principle that a writing system older than the alphabet gets to keep its consonants.

Where Protocol Meets Practice

The technical answer is simple: the canonical marks are legal IDNA 2008 characters, encoded as punycode under `xn--`. The practical answer is messier: legal does not mean stocked (registrar inventory is partial), and stocked does not mean typeable (stacked diacritics defeat mobile keyboards).

So the register's rule is a hierarchy of attested forms — full restoration, circumflex, macron-only, attested variant, and finally plain ASCII for the systems that cannot carry marks. Every rung is defensible because every rung is attested. The forms this register rules against are not rungs; they are errors, and errors do not get rungs.

Write back when you have checked the sources; they are better company than I am.

— The Register

The Verdict

Onuris is the canonical form: attested, checkable, and enforced across the temple, the lexicon, the cards, the APIs, and this register. The plain form onuris shares that standing — the two are the same name in every system. The false forms above are documented so that no reader has to take the temple's word on faith — the violations are stated, the sources are named, and the register stands open to challenge on every line.

The temple of Onuris stands at /onuris/.

The docket for this ruling: no false forms on the docket; no contested forms attested; the attestation rests on 4 cited sources — Thinite temple hymns (the Mehyt retrieval), Leiden Return-of-the-Eye cycle (Shu parallel), Abydos and This procession reliefs.

The Register Continues

This is one of 597 entries in the Canonical Register — the authoritative reference for every flagship temple. The temple's founding dispatch tells the name's story; its Restoration File details the marks; its Resonance File reads the archetype into the industries. The blog index holds the whole archive, and the Rulebook states the convention this register enforces.

Continue the register — previous entry: Óneiros (read it) · next entry: Orpheús (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.

egyptianASCII-equivalent formcanonicalThe Canonical Register