PuniCodex

The Canonical Register · No. 385

Perun: canonical, contested, and the false forms on record

Thunder, Lightning, Oak

Tier 2 Perun
Perun — Thunder, Lightning, Oak
By PuniCodex Team · · 3 min read

Perun: canonical, contested, and the false forms on record

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

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

First, the attestation. The tradition's record preserves this name in its romanized scholarly form: Perun — no older script survives to transcribe, so the canonical content is the exactness of the spelling itself.

Say it aloud as the sources heard it: say "perun" with the stress and length implied by the scholarly restoration "Perun". 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 perun differs from the canonical Perun 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.

And it never stopped working. Perun remains a touchstone for understanding slavic religion, art, and identity.

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: the tradition’s own standard. 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.

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

Perun is the canonical form: attested, checkable, and enforced across the temple, the lexicon, the cards, the APIs, and this register. The plain form perun 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 Perun stands at /perun/.

The docket for this ruling: no false forms on the docket; no contested forms attested.

The Register Continues

The register holds 542 entries like this one — each temple with its own ruling. Read the temple's founding dispatch for the story, its Restoration File for the philology, its Resonance File for the industries, or the whole archive end to end.

Continue the register — previous entry: Perseus (read it) · next entry: Phánē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.

slavicTier 2canonicalThe Canonical Register