AI for Constructed-Language Place Naming Rules

As of 2026-10-23 · The AZET team. We wrote this creative reference exercise as the AZET team. All language rules, places, and examples are hypothetical inventions for fun, not evidence of AZET product capabilities. The date marks this article's reference date, not current product verification.

Navekel, Sorekel, and Temakel belong on the same invented map for a reason: each ends in a word meaning sheltered settlement. Their resemblance comes from a decision you can inspect, not a vague instruction to make names sound ancient.

This exercise builds a tiny constructed language solely for place naming. Its handful of names follows inspectable rules, without claiming to describe real naming traditions.

Establish a rule before filling the map

Here is the entire starting specification for our invented language, called Vemari within this exercise:

Allowed syllable shapes: vowel or consonant + vowel, optionally ending in l.
Allowed vowels: a, e, i, o, u.
Place-name order: landscape root, then settlement root.
nave = reed marsh
sore = red stone
tema = hillside
kel = sheltered settlement
lun = watch post
Writing: join roots without a space; capitalize the first letter.

There is a deliberate defect: lun ends in n, which the permitted syllable shapes exclude. Catch it before building twelve watch posts. We choose to change the root to luma. Another author could widen the sound rule, but doing both would hide which decision repaired the mismatch.

Now the vocabulary and spelling rule agree. Navekel names a sheltered settlement associated with a reed marsh. Temaluma names a hillside watch post. Nothing in these names establishes population, architecture, or who lives there.

Work through an awkward join

Add ela, meaning exposed ridge, and alen, meaning meeting ground. Before joining them, inspect alen: its final n violates the same restriction. Replace it with alel, explicitly recording that this is an author revision rather than an ancient form.

The direct compound is Elaalel. It contains adjacent vowels across the root boundary. Our syllable inventory describes roots, but we have not yet decided whether compounds may contain that join. This is a missing rule, not permission to silently rewrite the name.

For this version, choose a narrow joining rule: when identical vowels touch across a boundary, write one vowel. Ela plus alel becomes Elalel. Different neighboring vowels stay unchanged. Do not generalize this to dropping any awkward letter.

Test the rule against the earlier names. Navekel and Sorekel remain unchanged because their boundaries contain a vowel followed by a consonant. The revision solves a specific problem without making unrelated map labels drift.

Distinguish construction from story history

A name built from roots gives the writer an internal explanation. It need not supply every character with a literal translation. You can decide later that a resident uses Navekel without thinking about reeds.

For now, keep an author note with three fields: intended feature, construction, and accepted label. An entry might read: exposed ridge meeting ground; ela plus alel with identical-vowel contraction; Elalel. This is a derivation record. Its purpose is to reconstruct a naming choice, not organize a personal glossary.

If a ruined watch post is called Sorekel, do not immediately correct it to Soreluma. Decide whether it began as a settlement or whether the draft contains a mistake. A historical exception needs an authored reason. An unexplained exception is simply unresolved.

An exact prompt for a bounded naming pass

Use the following as a hypothetical AI writing brief, or answer it yourself on paper:

Review this invented Vemari naming specification and my proposed labels.
Use only supplied roots. First identify roots that break the stated
syllable rules. Do not repair them silently. For every accepted label,
show its two roots, literal meaning, boundary operation, and final form.
Generate four alternatives only after the specification is consistent.
Keep landscape before settlement. Collapse identical boundary vowels
only; preserve other letters. Mark missing meanings unresolved. Separate
rule violations from intentional historical exceptions, which require
an author-supplied reason. Do not infer real cultures or product features.

Supply the corrected specification with that brief. Keeping both lun and luma as active roots would turn a resolved author choice into a fresh ambiguity. Preserve the earlier spelling in revision notes if it matters, outside the working specification.

Check the names on the actual page

Perform a derivation check first: reconstruct each accepted label from its roots without consulting the completed name. If the result differs, locate the exact joining decision.

Then perform a map check. Navekel and Navelekel may be technically distinguishable, yet too similar for neighboring places that readers must track quickly. Change a root choice or location label intentionally; do not invent random spelling exceptions to disguise the collision.

Finally, read one paragraph containing three names. The paragraph should carry useful action even when their literal meanings are unknown. A consistent naming system supports a story; it does not require readers to solve every compound before following a journey.

FAQ

Does the language need a full grammar?

Not for this bounded exercise. Define enough rules to explain the names you actually use. Add sentence grammar only when dialogue creates a reason to need it.

Can an exception remain unexplained to readers?

Yes. Keep its author explanation separate from exposition. Readers may never need the history, while you still need a reason to preserve the spelling.

Should every place name translate neatly?

Only if that fits your design. This starter system uses transparent compounds for inspection. An opaque name can be introduced later with a deliberate origin or an explicitly unresolved history.

A dated product reference

The E1 maker introduction dated October 3, 2026 described AZET as an assistant and mentioned an early-access waitlist. That historical description does not establish naming functions or current availability.

To express interest in AZET and its waitlist, visit azet.io.