Ꜣḫ: canonical, contested, and the false forms on record
A letter to a colleague, 31 July 2026 — on the name Ꜣḫ, and on the forms that keep failing it.
Your note said, roughly: surely the marks are a nicety. Permit me to use Ꜣḫ to show they are not.
First, the attestation. The attested form is 𓅜𓏤, from the tradition's own record. The canonical transliteration is Ꜣḫ.
Say it aloud as the sources heard it: 'AHKH' — start with a slight catch in the throat, then a short 'ah', and end with the raspy 'ch' of 'Bach'. 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 akh 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: akh may carry the name where marks are impossible, but it may not represent the name where marks are possible. A fallback is a vehicle, never the primary.
Now to the forms that provoked your letter. As for Ꜣkh: it comes from the publisher compromise — older books and hurried websites that print the "English equivalent" as if it were the name itself, and it fails because every substitution here (ḫ→kh) is a romanization of convenience, not an attested spelling — it teaches the reader to guess, not to read As for ak: it comes from the anglicized respelling — the name written the way English guesses it sounds, and it fails because rewrites attested consonant clusters to fit English spelling habits; every cluster simplified this way erases a letter the sources write
One more thing, because it always surprises: the name did not stay home. Egyptian deities were syncretized with one another and, in the Greco-Roman period, with Greek and Roman gods; temple theology developed complex composite forms.
And it never stopped working. The name survives in Egyptological scholarship, museum collections, modern spirituality, and the global fascination with Pharaonic civilization. Restoring Ꜣḫ in Unicode preserves the name's cultural specificity against the flattening force of plain ASCII.
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
Ꜣḫ is the canonical form: attested, checkable, and enforced across the temple, the lexicon, the cards, the APIs, and this register. The plain form akh is sanctioned as the fallback vehicle and nothing more. 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 Ꜣḫ stands at /sites/akh/.
The docket for this ruling: 2 false forms ruled against, Ꜣkh first on the docket; no contested forms attested; the attestation rests on 4 cited sources — Book of the Dead, Spell 61 (preventing the ba from being taken away), Book of the Dead, Spell 89 (causing the ba to be united to its body), Pyramid Texts, Utterance 263 (the king goes as an akh as lord of the horizon).
The Register Continues
Entry 11 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: Aithḗr (read it) · next entry: Akṣobhya (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.