Chapter 14. Five Variations, and a Final Greeting

Imagine a 28 mm-thick hardcover on a creator's desk. The first page carries the IP's atmosphere in one flow; the next unfolds its cosmology and rules; then come a thousand-year chronology, and then cities, people, and factions. At the back, an index lists 1,500 entries alphabetically with page numbers. Every piece of an IP's material has become a single book one can hold in one hand. Nine to fourteen months earlier, that book was scattered rulebooks, short stories, planning documents, and external wikis. Those materials passed through a Librarying Vault and became one LOREBOOK.

This is where the fourteen-part series ends.

Part 1 established the identity of a book that is an IP encyclopedia; Part 2 laid out five market variations; Part 3 covered the input after Librarying. Then came structure (Parts 4, 5, and 6), prose (7, 8, and 9), procedure (10, 11, and 12), and operations (13).

When material from thirteen installments is gathered, it becomes the procedure for constructing one LOREBOOK. This final installment looks back on that procedure, guides the first work to apply it to a reader's IP, and offers a final greeting.

Seeing the thirteen installments together

Taken together, the material developed across thirteen installments compresses into five major decisions.

First is the kind of book: choose which of the five variations—standard encyclopedia, art book, narrative bible, game-design bible, or official comics/webtoon setting guide—is closest to the reader's IP. The fourteen installments proceed on the standard-encyclopedia model, but if an IP belongs to another variation, the choice also decides which parts of the standard will grow or shrink.

Second is the book's skeleton: decide how to divide the six macro sections into ten, twelve, or fourteen parts. The number of Vault entries and the distribution of worldbuilding axes nearly answer the question, but the IP's primary medium and its future operating plan also matter. Twelve parts are standard, and it is natural when the combined areas D (geography, culture, everyday life) and E (races, factions, people) exceed 50 percent of the IP.

Third is the shape of one entry: eleven to twelve frontmatter fields, a one-line summary, introductory paragraph, body sections, related entries, editorial notes, and footer. The fact that 1,500 entries align in the same form creates reader trust, and direct conversion of Librarying frontmatter becomes one axis of automation.

Fourth is automating part mapping. The two coordinates—nine classifications and worldbuilding axis—determine an entry's location, and searching those coordinates automatically produces mapping candidates for 1,500 entries. Automation accounts for 60–70 percent and human decision for 30–40 percent. Integration and division, mega-hub splitting, length balance, part priority, and the IP's particular character remain human work.

Fifth is the tone of prose. Map seven voices by part, using chronicle, field-report, and catalog voices as the core and the other four as supporting voices. Let distinct part voices flow naturally; write mechanic prose through dual narration of external metaphor and internal law. Clearly separate six kinds of material that do not enter the volume: short-story body text, rule numbers, rule codes, undecided entries, game meta, and foreign-language body text.

On top of these five decisions, the seven-Phase process—0 agreement, 1 skeleton, 2 pilot part, 3 expansion, 4 consistency, 5 appendices, 6 packaging—occupies nine to fourteen months. Human creators and AI collaborators divide work in every Phase through the four collaboration axes: specification, intent, expected effect, and limits.

Which variation suits a reader's IP? — final guidance

Which of the five variations suits an IP is nearly decided by two questions: who is the reader, and is the book public or private?

For general readers and creators together, choose the standard encyclopedia (A). If fans and collectors are the primary readers, choose an art book (B) or official comics/webtoon setting guide (E) according to the scale of visual assets and dependence on the main work. For private collaboration with outside writers or adapters, choose a narrative bible (C). For private collaboration with a game-development team, choose a game-design bible (D).

An IP often falls between two types: a game becoming a comic or webtoon, or a TRPG developing into a video series. The recommendation is to make the standard form (A) first and branch into other types as seasons progress. Starting large and reducing to a small form means cutting material; moving from the standard to a variation is primarily reclassification and is lighter.

Five sister volumes

Part 1 noted that this work is one of five sister volumes MEJE Works is constructing. Their relationship is worth recalling in the final installment.

<Seoyeongak> (reading foreign-language works deeply; setting translation keywords)
<New Character Build> (creating one person from zero)
<Librarying> (binding scattered material into one dictionary)
   │
   ↓
<LOREBOOK> (binding material into one encyclopedia) ← this work
   │
   ↓
<Storytelling100> (constructing one hundred short stories from the library)

The five volumes describe one cycle of IP operation. Seoyeongak carries foreign-language material into Korean working input; New Character Build constructs a twelve-stage sheet for one person from zero; Librarying organizes scattered material into an Obsidian Vault of 1,500 entries; LOREBOOK binds that Vault into a book; and Storytelling100 constructs one hundred stories from the library. All five work on the same foundation: the two hands of creator and AI collaborator, the four collaboration axes, and a single .md source. Together their five outputs organize an IP's material operations.

All five are materials derived from one MEJE methodology. Terms repeated here—producer, AI collaborator, four collaboration axes, Vault, nine classifications, and worldbuilding axis—appear in the same form in the sister volumes. That consistency gives MEJE IP operations their character and lets readers move naturally from any one task to another.

The reader's first work

After closing this text, the reader's first work has five stages.

First, confirm Librarying. This work takes as input a completed Librarying Vault: one Obsidian work folder holding 1,000–2,000 .md files; thirteen-column frontmatter in every file; nine classifications and worldbuilding axes decided for the IP; and a properly functioning Obsidian graph view. If every condition is ✓, apply this work immediately. If not, follow the sister work Librarying first.

Second, write the Bible agreement document. Put the eight decisions from Part 10 in one document: input confirmation, part composition, tone guide, SSOT hierarchy, short-story separation policy, LOREBOOK type, publication specifications, and schedule/budget. This roughly ten- to twenty-page .md file becomes the work's single source of truth.

Third, choose an AI collaborator. Choose a familiar tool in the reader's environment; this text does not name a particular model. After choosing, define the four collaboration axes in advance for every work stage.

Fourth, create one pilot part. Start with one of twelve parts—Part 2 or Part 4 is recommended. Select the pilot, write the part README and all chapter READMEs, turn three to five core entries into prose, verify tone, structure, and SSOT quotation patterns, run the pilot consistency check, and make a GO/NO-GO decision for entering Phase 3. The pilot GO is the work's branch point.

Finally, enter Phase 3. This is the stage of turning eleven parts into prose. Work priority runs Parts 1, 2, and 3 (settling identity), then 5, 6, and 4 (the everyday skeleton), then 7, 9, and 10 (cardification), then Part 8 (integration). Each part takes roughly two to three weeks; all eleven take four to six months. Update progress every week, check consistency in every part, and bring every part from ● to ✓.

These are the reader's first five tasks. Phases 4, 5, and 6 follow, and the LOREBOOK built by this text reaches the reader's shelf after nine to fourteen months.

Starting small

The twelve-part standard is recommended, but readers may start smaller. A twelve-part, 450-page LOREBOOK taking nine to fourteen months can be burdensome for an IP at the beginning of operations.

The first path starts with ten parts and roughly 250 pages: 100–200 entries and a first cycle of about six to nine months. Roughly 80 percent of this text's procedure applies unchanged. Some parts, such as Part 7 genre actors and Part 8 dimensional/spatial catalog, are omitted, but the essence of skeleton, prose, and procedure remains.

The second path publishes the ten-part first cycle, then expands to twelve parts in a new v2.0 edition after five or ten years, when material has accumulated. The new-edition cycle from Part 13 applies; because it starts from first-cycle material, the work is lighter.

The third path is for large IPs: begin with twelve or fourteen parts. If the IP has already operated for more than five years and the Vault holds at least 1,500 entries, twelve parts are natural; if it holds more than 600 entries, fourteen parts can also be recommended. Choose the path that fits the IP.

One-installment summary — fourteen stepping stones

This is a one-installment summary to keep open while applying the series to an IP. Part 1 accepts that LOREBOOK is both an IP encyclopedia and guidebook and agrees on a single .md source. Part 2 decides among five variations; Part 3 confirms Librarying Vault input. Part 4 chooses among ten, twelve, and fourteen parts and constructs a one-page twelve-part matrix; Part 5 agrees on one entry's standard form, five-part structure, and eleven to twelve frontmatter fields.

Part 6 uses the two coordinates—nine classifications and worldbuilding axis—to automatically make twelve-part mapping candidates for 1,500 entries. Part 7 decides the part-by-part mapping of seven voices and creates a tone-guide .md. Part 8 establishes a three-beat prose standard—experience, reality, resonance—through dual narration of mechanics. Part 9 decides short-story separation and multilingual policy.

Part 10 advances Phases 0–3 until every part reaches ●–✓. Part 11 advances Phases 4–6 to create the printed and public-web editions. Part 12 decides human/AI division through the four collaboration axes. Part 13 agrees on operations, establishing a single git-tag tree and update history. Part 14 begins the five first tasks.

This summary is the fourteen installments' stepping stone. Reopen one line for each installment while applying it to an IP, and the installment's key decision returns into focus.

First-work checklist

Keep this one-page checklist on the desk after closing the text.

In Phase 0 (input and agreement, two to four weeks), secure a Librarying Vault of 1,000–2,000 .md files; check thirteen-column frontmatter; decide nine classifications and five to seven worldbuilding axes; check that Obsidian graph view works; write the Bible document's eight decisions (10–20 pages); and agree on LOREBOOK type A–E, SSOT hierarchy, and a nine- to fourteen-month schedule and budget.

In Phase 1 (skeleton, one to two weeks), create the root and twelve-part directories, complete 1,500 empty .md files and automatic frontmatter conversion, and initialize _progress.md.

In Phase 2 (pilot part, three to four weeks), select Part 2 or 4, write the pilot README and chapter READMEs, turn three to five core entries into prose, verify the tone guide, and obtain a master GO decision.

In Phase 3 (expansion, four to six months), turn eleven parts into prose by priority, update progress weekly, run consistency checks per part, and commission illustration after body text becomes v_confirmed, until every part reaches ●–✓.

In Phase 4 (consistency, one month), confirm zero dead links, zero SSOT hierarchy violations, and 100 percent consistency with Librarying frontmatter. In Phase 5 (appendices, one month), complete the four required appendices—glossary, index, map book, and chronology compendium—and select recommended appendices by IP. In Phase 6 (packaging, two months), deploy the public web edition, print the publication edition, and pass ISBN, barcode, and legal specifications.

In operations (quarterly and five-year), conduct quarterly automated checks and Librarying synchronization, and consider a new v2.0 edition after five to ten years. Check off one item at a time, and after nine to fourteen months one LOREBOOK will stand on the reader's shelf.

Closing

This text's core is how a person and an AI collaborator build one book with two sets of hands. 1,500 entries fill a twelve-part matrix; seven voices make tone by part; seven Phases arrange nine to fourteen months; and four collaboration axes organize the division in every Phase. This is the MEJE standard for IP operations, and readers apply the same method with their own tools.

One companion appendix volume comes with the work: a key-term index in Korean alphabetical order, seven sets of market examples, a one-page integrated four-axis collaboration matrix, and one sample integrated entry. It is material to keep open when a term is unclear, a market example is needed, human/AI division needs review by Phase, or a model is needed for constructing one entry.

The fourteen installments end here; work in the reader's IP begins here.

Every creator eventually creates a world. Make a person and the world that person inhabits follows; build a city and that city's laws follow. When a work's material accumulates and a world begins to rise among it, one wants to bind that emerging world into a book. May these fourteen guides sit on the reader's desk then, as one volume of stepping stones.

May you meet that one book on your shelf.

Copyright in this work belongs to Kim Dong-eun WhtDrgon and MEJE Works Corp. Without the copyright holders' prior written consent, no part of this work may be reproduced, distributed, transmitted, displayed, performed, broadcast, translated, adapted, or otherwise used.