Ancient Dragon
Name Generator

01

The oldest unfinished sentence

Choose the promise before the epithet. A dragon called Keeper of the Unfinished Bridge suggests a particular responsibility, while an adjective such as eternal says little about behavior. Decide who requested the bridge, what completion meant, and why a creature capable of moving stone has not finished it.

Perhaps the promise concerned safe passage between communities that no longer recognize each other. The dragon can remember every stone yet misunderstand the present argument. Give the title a public witness, an approximate date, and an ordinary shortened form.

Record who may challenge its account, since a witness title becomes brittle when nobody can ask the bearer a difficult question. Travelers might say Bridgekeeper while the dragon's own name remains available to friends who discuss subjects beyond its ancient assignment.

02

Hoard as an indexing problem

Maps, promises, and lost languages require different forms of care. A map hoard needs dates, scales, and notes about changing coastlines. A promise hoard needs a distinction between a witnessed agreement and an obligation the dragon accepted personally.

A language collection needs speakers and contexts, not merely lists of words. Let the chosen hoard affect the name's final component: Foldwatch might describe a dragon whose maps are organized by mountain folds, while Last Listener could identify a custodian seeking living conversation partners. These are invented descriptive titles, not translations from historical languages.

Their usefulness comes from the questions they raise about ownership, access, and correction.

03

Sound across several centuries

A long formal introduction can be impressive once and exhausting every subsequent time. Write a private name of two or three distinct syllables, then test a clerk reading it, a child asking a question, and another dragon expressing annoyance. Historical spellings may vary, but keep one readable form in current narration.

If an old inscription uses a different name, connect it through a recognizable sound or a documented change. Avoid making every vowel cluster proof of antiquity. A simple name that appears in several contradictory records can feel older than a decorative string of apostrophes.

Pronunciation is a practical relationship between the creature and the people addressing it.

04

Memory has a geography

Locate the dragon's resting places and consider what it could actually have observed. A creature sleeping beneath a hill for eighty years cannot personally describe every harvest above it. Information may arrive through delegates, songs, or gifts, each carrying omissions.

An epithet can preserve the date of a waking rather than the date an event happened. This distinction creates fair mysteries: a village remembers the dragon arriving after a flood, while the dragon insists it woke before the disaster. Both accounts may be accurate because a messenger used the word flood for an earlier upstream breach.

Establish gaps before relying on them to resolve the story.

05

A treaty with fresh ink

In a useful opening case, a delegate produces a supposedly ancient treaty whose ink is still fragrant. The dragon recognizes the wording but rejects the signature. Rather than immediately exposing a villain, investigate how the document was preserved, recopied, and authorized.

A renewal ceremony may require a fresh copy every generation, with a missing clause gradually becoming customary. Name the dragon for its original promise, then let the dispute test whether that title still describes its present choices. The decisive action could be acknowledging a changed river boundary instead of demanding that living farmers obey a map drawn before their valley existed.

06

Authority that can be declined

Finish by identifying one request the dragon will refuse and one correction it will accept. These boundaries make an ancient name credible. Neighbors may honor the creature's long service while contesting its interpretation of current law.

A younger archivist can know a recent fact the dragon missed without diminishing its experience. Keep titles provisional where appropriate: Witness of Seven Shores might become Witness of Six after an island disappears, and the argument over retaining the older form can carry grief as well as politics. The best result connects a memorable sound to a specific unfinished duty, leaving room for the bearer to change without losing its recognizable identity.

07

Revision case: Aethorax and independent corroboration

Draft setup for Aethorax at the archive of old pacts: Compare the dragon's direct memory with one separately dated contemporary account before accepting a disputed claim. This example uses “Aethorax, Twowitness” as the proposed public introduction. Failed independent corroboration version: Aethorax receives “Twowitness” before anybody addresses this obstacle: A beloved witness accurately remembers the bridge but confuses a later ceremony with its opening.

For Aethorax, the apparent achievement therefore exceeds the evidence. In independent corroboration, the draft treats recognition as permission to approach or command. Revised independent corroboration scene: The archive must pause its usual reverent recital and allow a younger researcher to question chronology.

Keep Aethorax's introduction provisional while that cost is paid. The independent corroboration evidence arrives through an observable detail: The carpenter's invoice names a repair material unavailable during the year claimed by the ceremony account. Keep the observer outside the recorded boundary for Aethorax; distinguish a response from an agreement.

Introduction before revision: “Aethorax, Twowitness” is announced as settled. After revision: “Aethorax” is used pending the independent corroboration evidence; “Twowitness” records only the accepted result. In this ancient dragon scene, “Azvarion” takes the other speaking role.

The ending for Aethorax must still acknowledge the local conflict: A treaty names the dragon as witness, but its memory contradicts the surviving text. With independent corroboration, a limited agreement leaves space for disagreement without making “Twowitness” meaningless.

08

Revision case: Azkhaelor and successor consultation

Draft setup for Azkhaelor at the archive of old pacts: Bring affected descendants and present residents together to decide which inherited duties still serve living needs. This example uses “Azkhaelor, Newvoices” as the proposed public introduction. Failed successor consultation version: Azkhaelor receives “Newvoices” before anybody addresses this obstacle: A household protected by the old oath now prefers a different road and a shared maintenance fund.

For Azkhaelor, the apparent achievement therefore exceeds the evidence. In successor consultation, the draft treats recognition as permission to approach or command. Revised successor consultation scene: Representatives need time to distinguish their actual interests from the prestige of an ancient formal role.

Keep Azkhaelor's introduction provisional while that cost is paid. The successor consultation evidence arrives through an observable detail: Recent petitions request safe market access rather than preservation of the original crossing's exact location. Keep the observer outside the recorded boundary for Azkhaelor; distinguish a response from an agreement.

Introduction before revision: “Azkhaelor, Newvoices” is announced as settled. After revision: “Azkhaelor” is used pending the successor consultation evidence; “Newvoices” records only the accepted result. In this ancient dragon scene, “Azvarion” takes the other speaking role.

The ending for Azkhaelor must still acknowledge the local conflict: A treaty names the dragon as witness, but its memory contradicts the surviving text. With successor consultation, a limited agreement leaves space for disagreement without making “Newvoices” meaningless.

09

Revision case: Thalazyr and formal promise release

Draft setup for Thalazyr at the archive of old pacts: Document fulfilled responsibilities and authorize an old promise to end without erasing its recorded history. This example uses “Thalazyr, Laststone” as the proposed public introduction. Failed formal promise release version: Thalazyr receives “Laststone” before anybody addresses this obstacle: Officials fear that ending this obligation will weaken unrelated agreements whose terms remain valid.

For Thalazyr, the apparent achievement therefore exceeds the evidence. In formal promise release, the draft treats recognition as permission to approach or command. Revised formal promise release scene: The dragon must publicly surrender an epithet central to how several institutions recognize its authority.

Keep Thalazyr's introduction provisional while that cost is paid. The formal promise release evidence arrives through an observable detail: The original oath includes a completion condition overlooked by every later ceremonial shortened version. Keep the observer outside the recorded boundary for Thalazyr; distinguish a response from an agreement.

Introduction before revision: “Thalazyr, Laststone” is announced as settled. After revision: “Thalazyr” is used pending the formal promise release evidence; “Laststone” records only the accepted result. In this ancient dragon scene, “Azvarion” takes the other speaking role.

The ending for Thalazyr must still acknowledge the local conflict: A treaty names the dragon as witness, but its memory contradicts the surviving text. With formal promise release, a limited agreement leaves space for disagreement without making “Laststone” meaningless.