MEJE BOOKS Knowledge Library

KIM DONG-EUN · The Worldview Designer (15 chapters)

Chapter 12. Definition and Naming

Kim Dong-eun WhtDrgon. · Chapter 12

Chapter 12. Definition and Naming

The candidates that have made the list are not yet members of the world. Their meaning has not been fixed, and their name has not been decided. This chapter covers the second act of the work cycle: definition. The guiding question of this chapter is: what changes when something is named? The first half takes up the craft of definition, which fixes meaning; the second half takes up the craft of naming, which decides the name. Only when the two crafts are joined does a keyword candidate become a word of the world.

1. Definition: Rewriting the Dictionary from Inside the World

Definition is the work of fixing what a given keyword is, and is not, in this world. What separates the designer's definition from lexicography is the location of the reference point. A dictionary takes real-world usage as its reference, but the designer rewrites the dictionary by taking the interior of the world as the reference instead. Take the word knight as an example. In a real-world dictionary, a knight is a member of the armed nobility of medieval Europe. The designer's question is different. What is a knight in this world? Is the title inherited or conferred by investiture? Do they ride horses or dragons? How many are there? What do they swear loyalty to? Every time an answer is fixed, this world's knight diverges further from the real-world knight, and the sum of those divergences becomes the world's distinctiveness. Definition work is, in the end, the fixing of the points at which this world departs from reality as its default. A definition also needs a fixed format. A good definition has the structure of membership and difference: it states what category the item belongs to, and how it differs from other members of the same category. Something like "heavy cavalry directly under the crown, whose investiture includes a magical oath" lets understanding come quickly from the membership and lets distinctiveness stand from the difference. Stating the negative is also worth building into the format. Writing down what this world's knight is not — the boundary against mercenaries and militias, for instance — prevents misuse. The design implication is definition's verification question: can an outside writer who has read only this definition use the keyword without getting it wrong? A definition that fails this test is still an impression, not yet a definition. Definitions are the sentences where the world meets the outside, on the front line.

2. Redefinition: The Craft of Twisting a Real-World Word

Of the definition crafts, the one with the highest efficiency is redefinition. Redefinition is the operation of taking a word that already exists in reality and twisting its meaning. Set against the invention of a new word, its economy is clear. An invented word must teach both a pronunciation and a meaning, but a redefined word gets its pronunciation for free. The reader meets a familiar word and relaxes, then meets its twisted meaning and tenses up. Genre-standard words like hunter and awakened were all born by this route. It is the same economy as cliché use: familiarity lowers the cost of entry while strangeness raises curiosity. The directions of twisting sort into three. Expansion: a word like hunter comes to denote a profession that catches monsters rather than beasts, widening the scope of the meaning. Narrowing: a general word like contract comes in this world to denote only a contract with a demon, narrowing the scope to load it with weight. Inversion: a word like paradise becomes the official name for a place of exile, flipping the meaning to plant the world's irony inside a single word. All three directions operate on the premise that the original meaning stays behind in the reader's mind. Twisting is a craft that only works when there is a reference point. Inversion-type redefinition amounts to implementing utopia's double ledger at the level of vocabulary. The design implication is managing a list of redefinitions. A cross-reference table of the words this world uses differently from reality — a two-column table of the real-world meaning against the in-world meaning — becomes the core chapter of the onboarding document for outside creators. The more redefinitions a world has, the more mistranslation multiplies without this table. For translators, too, this table becomes the top-priority handover document.

3. The Philosophy Held Within: The World's Position Carried in Definitions

A definition looks like a neutral piece of technical documentation, but it is in fact a vessel that carries the world's position. This is because what and how something is defined is where the value of the philosophy axis seeps in — what that world holds to be right and worthy. Comparing two worlds that define magic makes this vivid. One world defines magic as the art of friendship struck with spirits; the other defines it as a transaction that pays a cost through equivalent exchange. Two definitions of the same phenomenon imply entirely different worlds. In the first world, a failure of magic is the breakdown of a relationship; in the second, it is a shortfall in the ability to pay. A single definition reserves even the grammar of conflict. This is why fighting over a single particle in a definition, in a settings meeting, is not a luxury. The more foundational the keyword — death, honor, family, power — the heavier this implicit load. A world that defines death as a homecoming and a world that defines it as extinction diverge all the way from funeral customs to views on war. This principle also becomes an inspection tool run in reverse. When a world's philosophy is blurry, laying the definitions of its foundational keywords side by side and reading them reveals what this world actually believes. If the declared philosophy and the philosophy that has seeped into the definitions disagree, the world already carries a fracture. If a world that professes mercy has a cruel definition of punishment, one of the two is a lie. The design implication is a double standard for reviewing definitions. A definition must be screened both for whether it is accurate and for whether it is true to this world. The screening criterion for the latter is exactly the declaration of the four axes.

4. Interconnection: The Structure by Which Definitions Call Definitions

Definitions do not stand in isolation. A given definition is only established by referencing other keywords. If the definition of knight brings in kingdom, investiture, and magical oath, then those three keywords are, in turn, put on demand for definitions of their own. This chain of definitions calling definitions is interconnection — compound expansion showing up at the level of vocabulary. Connection has two faces. The good face is the solidity of the net. Definitions that reference one another verify one another. If the definition of oath changes, the definition of knight is shaken, so conflicts surface automatically at revision time. A dense reference network doubles as an early-warning system for paradox. The net of definitions is the net of review. The bad face is the accumulation of circularity and the undefined. A circular definition, where each item is explained only by the other, looks like a net but touches nothing; and as undefined items — referenced but never given a definition of their own — pile up, holes multiply in the net. The tool for managing this is making the reference relationships visible. Once each definition explicitly notates the keywords it references, the entire document system comes into view as a connection graph. Which item is heavily referenced and which item remains undefined becomes visible as data. An item with a high reference count is, in effect, the world's hub keyword, and becomes new grounds for deciding where to dig first. The design implication is running an undefined-item queue. Building a routine that automatically drops a referenced-but-undefined keyword into the queue during definition work means the definition work itself produces the list for the next round of work.

5. Definition and Story: The Interface Where Setting Becomes Story

Once the net of definitions is woven, something unexpected happens: definitions meet and generate story. Say a world holds two definitions side by side — that a knight is bound to the kingdom by a magical oath, and that an oath, when broken, demands a cost. Each sentence, on its own, is a piece of description, but the moment they sit next to each other, a question is born: what happens to a knight who breaks the oath? The question calls up a character, and the character calls up an event. This is exactly the interface where setting becomes story — the spot where definition meets definition and produces tension. This occurrence is not an accident; it can be designed. The principle is to plant directionality inside the definition. A definition that describes only a state is static, but a definition that carries a condition and its consequence is dynamic. "An oath demands a cost when broken" generates more story than "an oath is sacred." When ingredients like taboo, cost, exception, and deadline are built into a definition, that keyword releases conflict wherever it is placed. This is a generalization of the same principle by which the norm tables seen in Typology produced dilemmas. The design implication is screening for generative potential. When fixing the definition of a core keyword, count how many questions this definition produces when it meets the other definitions. A world stacked only with definitions that produce no questions is coherent but sterile. Productivity must rise on the review scale alongside accuracy. The world's fertility is taken up again later, under the name self-propulsion.

6. Naming: What a Name Does

The second half of the chapter is the matter of the name. Naming is the work of deciding the name to be called for an already-defined item — another act of fixing, paired with definition. A name does more than it might seem to. First, a name is an address. Since search, citation, and reference all run through the name, a name is the basic infrastructure of the document system. This is why the regularity of headings was a condition of format. Second, a name is the first piece of information. The reader meets the name before reading the definition, and receives the object's first impression from the name's sound and structure. The Obsidian Knights and the Sunflower Knights are already different organizations before their definitions are read. A name whose first impression disagrees with its definition becomes an expensive name, one that has to teach the reader twice. Third, a name is a sample of the world. The sounds of proper nouns gather into the world's linguistic texture, and the reader senses the world's grain through that texture. A world with consistent naming can be identified by its names alone, and this power of identification is exactly a brand. Fourth, a name is a unit of rights. What becomes the object of trademark, domain, and search dominance is not the setting but the name, so in a commercial worldview, naming is also a legal matter. The design implication is elevating naming's standing. It is common practice to treat naming as an appendage to fixing a definition, or as last-minute decoration, but since a name is an item's face and its address, it must be handled by a procedure of fixing on par with definition. The four topics that follow are the content of that procedure.

7. What Is a Name

Before the procedure, we confirm the structure of a name. A name is a compound of two components: denotation and connotation. Denotation is the function of pointing. Once a given sound and spelling points to a specific object without being confused with anything else, denotation is established, and at that point the name need carry no meaning at all. Connotation is what a name gives off — etymology, sound, association, length, even the impression of its pronunciation, all the information a name carries before denotation ever comes into play. The mixing ratio of the two components sets a name's character. A name with shallow connotation is closer to a code. A name like Zone 7 or Specimen K-3 is a naming that leaves only denotation behind, and that very dryness can itself carry the connotation of bureaucracy or inhumanity. A name with deep connotation holds a story. A place name like Dusk's Gate points to a location while simultaneously carrying images of time and boundary. The classical summit of worldview naming is the case where connotation is pushed all the way to the level of a language system. Design a fictional language first, then derive names by that language's word-formation rules, and every name in the world rings with a single language family. The consistent resonance of Tolkien's place names and personal names is the proof of this. The design implication is the deliberateness of the mixture. How much connotation to load into a given name is a matter to be decided by the object's standing, not by taste. The gradation that assigns deep connotation to core keywords and dry denotation to items kept for management purposes is the economics of a naming system.

8. What to Name

Once the structure of a name is understood, the next question is scope. Not everything in a world can be named, and not everything should be. Naming carries a double cost. One is management cost. The moment an item is named, it becomes subject to notation standardization and revision tracking, turning into a dependent of the document system. The other is the reader's cognitive cost. A proper noun is a piece of vocabulary the reader must memorize, and the flood of unfamiliar names in a work's opening pages is the chief culprit behind the entry barrier. In the first chapter of a fantasy novel, the point where readers drop off is usually somewhere around the fifth proper noun. Naming, therefore, must be selective. The standard is recurrence and reference: issue a name only to what will be called repeatedly in the story and the documents, and to what will be referenced in other items' definitions. A tavern passed through once can just be "the tavern"; only the tavern where the protagonist gathers every week earns a name. The fact that issuing a name is itself a grant of standing is also something to put to use — including in the placement of foreshadowing. An object given a name in advance carries, in effect, an advance notice of its return. Readers learn to treat what is named as important, so the distribution of naming becomes the world's spotlight arrangement. The design implication is running a naming register. Manage the total volume and distribution of issued names, and require new naming to show proof of demand — namely, a planned return. Inflation of names drops the world's currency value, that is, the weight carried by each individual name. In a world where names are scarce, the act of naming itself becomes an event.

9. Naming Conventions: The Minimum of Language Design

When naming the objects that have been selected, the first task, before individual name-making, is establishing conventions. Naming conventions are the word-formation principles this world's names will share — a minimal device that secures a world's linguistic consistency without going all the way to full language design. The standard items of a set of conventions are as follows. A phoneme palette: fix the sounds that will be favored and the sounds that will be forbidden in names from this culture. Just as a northern culture rich in aspirated consonants differs from a southern culture rich in liquids, a difference in palette alone makes the boundary between cultures audible. An affix system: fixing recurring components — the element attached to the end of a place name, the honorifics and family markers attached to a person's name — means a new name automatically wears the world's grain. Principles of notation and translation: fix the standard for Romanization, the standard for transliteration, and the criteria for choosing between translating the meaning and transliterating the sound. For a world planned for multilingual rollout, this item is half of the naming conventions. A prohibited list: keep a checklist to screen out collisions with existing trademarks, accidental coincidence with profanity, and taboo words specific to each culture. The design implication is that the conventions document comes first. Making a single page of naming conventions first and building individual names on top of it is always cheaper than naming things first and stitching consistency together afterward. Conventions also raise the speed of naming, since choosing from within a palette is faster than making something from a blank page. In collaboration, conventions even serve as a quality floor. A name that follows the conventions will, at minimum, do no harm to the world's grain.

10. How Are Names Managed

The last problem of naming is lifespan. A name, once made, is not finished; it is an asset that must be managed. The first axis of management is policing notation. The moment the same object is spelled differently from one document to another, search dies, and once search dies, that item effectively splits into two items. The tool for policing this is a notation register: fix one canonical spelling and specify the permitted and forbidden variant spellings. The second axis is the procedure for renaming. A name can change. A trademark collision is discovered, a problem surfaces in a translation market, a reorganization of the world demands the name be replaced. The trouble is that a name is the document system's address. Changing an address means updating every document that referenced that name, so renaming must be carried out as a procedure that includes a record mapping the old name to the new one and a batch revision of the referencing documents. A renaming carried out without a procedure leaves a ghost address in the world. Anyone who searches under the old name gets lost in the world. The third axis is preserving history. A retired name is not erased from the record either. Since the old name survives in past deliverables and in the fandom's memory, the old name's history must be kept on as a search alias. What these three axes point to is clear. Managing a name is managing the document system, and the crafts of fixing — definition and naming — require a system that stores and carries what has been fixed. The craft that fixes a word and the craft that keeps a fixed word alive are two different crafts. That system is the last act of the cycle: the world of registration.