Game studio · 事例

The timeline contradiction hits the meeting table before a fan posts it to the forums

Example · Hypothetical scenario読むのに5分Consilience Team

これでできることLoad 700-odd lore docs, quest scripts, and character sheets, ask "what do the documents say about the year the mentor died?", and the character sheet that says RE 412 comes back alongside the chapter 7 script that puts him at the RE 414 Harvest Festival — each with its verbatim sentence and note name attached.

Three weeks after launch, two screenshots showed up side by side on the community forums. The character sheet says the mentor Kael died at the Black Tower in the winter of RE 412. The chapter 7 flashback has him standing next to his apprentice at the RE 414 Harvest Festival. The narrative director opens both pages in the internal wiki and finds them exactly as posted. Which one is current, and whether fixing this is a one-year edit or a chase through ten documents — the wiki doesn't say.

This person is the narrative director at a 15-person studio. She has 700-odd lore documents, quest scripts, and character sheets, plus an export of the internal wiki, and two new writers just joined ahead of season 2. This piece follows what happens when that material goes into a Consilience workspace and someone asks "what year did Kael die?" It isn't a real customer story — it's a hypothetical scenario we worked through.

The material: 700-odd documents and 12 years of timeline

Five writers built this world over six years. The one who wrote the earliest lore has already left the studio, and the two season 2 writers joined this week. All of it survives as files. Nobody at the studio has read all 700.

  • 700-odd markdown lore documents, quest scripts, and character sheets, split across three folders: lore/, quests/, characters/.
  • One internal wiki export. Around 240 pages, including the timeline page covering RE 401–413.
  • Scripts for the 12 main chapters plus 34 season 1 side quests. Some flashbacks tag the chapter number and the year together; others just drop a year into the prose.
  • 60-odd character sheets. Birth and death years, allegiances, and relationships, each written out in free prose.
  • 20-odd season 2 lore meeting notes. Decisions that were already overturned last year are mixed in here.

How it works today

Today it runs on human memory and full-text search. The director searches the wiki for "Kael," gets 30-odd pages, and guesses which one is current from the modified date. The character sheet lives in characters/ and the chapter 7 script lives in quests/, so the two documents never appear on one screen.

Contradictions usually surface after launch. A fan pins two screenshots together, and that's when the studio sees the two documents side by side for the first time. Next comes the meeting to scope the retcon. Moving Kael's death to RE 414 means touching his apprentice, the Black Tower, the Harvest Festival, and some of the season 1 side quests — and the only tool for counting how many that is, is full-text search.

The two writers who joined this week have none of these six years of judgment calls. Which wiki pages are live lore and which were scrapped in a meeting last year: there's exactly one person to ask, and it's the director.

How to set it up

The setup has one goal: take "Kael died in 412" and "Kael was at the 414 Harvest Festival," scattered across 700 documents, and gather them under the same person.

Get 700 documents into the workspace

  1. Put the three folders and the wiki export in the workspace

    Drop lore/, quests/, characters/ and the wiki export markdown into the workspace folder and run extraction. Under "Extraction" in the left rail of the knowledge graph (⌘⇧G), coverage climbs as "{done} of {total} added to AI search". Timeline questions only answer correctly once all 940-odd documents are in, so wait for coverage to fill.

  2. Teach "Domain vocabulary" the royal calendar

    In "Domain vocabulary" in the left rail, register this world's terms: royal calendar, Harvest Festival, Black Tower, flashback. Then run "Re-extract everything" from "Extraction" so the extractor reads "RE 412" as a year, and documents you loaded earlier get re-read with the same vocabulary.

  3. Merge Kael's three aliases in "Synonyms"

    Over six years Kael has been called "the mentor Kael," "the Master of the Black Tower," and "Master Kael." When those pairs show up in "Synonyms" in the left rail, a person decides whether to leave them "merged" or "kept apart". The three aliases have to resolve to one person before the next step's question means anything. If something merged wrong, flip the toggle back.

  4. Clear out last year's reversals in "Revisions"

    The 20-odd season 2 meeting notes have decisions that overturned earlier lore mixed in. "Revisions" in the left rail collects the cases where a later note revised an earlier note's decision, and a person confirms or rejects each one. Only what you confirm here gets marked as scrapped lore.

How to ask

The questions you throw at chat about Kael, and the shape of what comes back
"What do the documents say about the year the mentor died?"
→ 3 documents that disagree.
   "In the winter of RE 412, he died at the Black Tower"
     — characters/char_kael
   "The 414 Harvest Festival. Kael lays a hand on his
     apprentice's shoulder"
     — quests/quest_ch7_flashback
   "412 — the Master of the Black Tower dies"
     — lore/wiki_royal_timeline_401-413

"If I change Kael's death to 414, which documents do I
 have to touch?"
→ 11 documents that mention Kael alongside a year.
   Verbatim sentence and note name on every row.
   Includes 3 season 1 side quests.

"Who is written as alive in RE 414?"
→ 9 people. Next to Kael sits a marker that another
   document has him dead in 412.

The wiki stores pages as pages. Extraction pulls facts sentence by sentence, attaches a source note to each one, and gathers them under the same Kael entry. The "winter of 412" sentence from the character sheet and the "414 Harvest Festival" sentence from the chapter 7 script sit in different folders, but on Kael's entry they land on one screen. A person rules on whether that's a contradiction; the screen's job is putting the two sentences side by side to rule on.

The retcon-scope question uses the same structure. That "11" counts sentences where Kael the person and a year are attached to each other, so a list you used to count from memory in a meeting becomes a list with verbatim sentences on it. A script that only ever calls him "the Master of the Black Tower" lands in those 11 too, as long as the aliases are merged.

What changes

BeforeNow
You learn about the contradiction three weeks after launch, when a fan pins two screenshots together"What do the documents say about the year the mentor died?" puts the 412 character sheet and the 414 chapter 7 script on one screen
Search the wiki for "Kael" → 30-odd pages → guess which is current from the modified dateOne Kael entry gathers the sentences that talk about him, each with its verbatim text and note name
Scope the retcon by memory in a meeting"If I change it to 414, which documents do I have to touch?" returns 11 documents with their verbatim sentences
A new writer's only way to know whether lore was overturned last year is to ask the directorThe "Revisions" panel points out which decisions a later meeting note overturned, and only what a person confirms gets marked as scrapped lore

Your original markdown doesn't change. Extraction results only accumulate in the graph, and a bad alias merge gets reversed in "Synonyms", a wrongly confirmed revision in "Revisions".

The timeline contradiction hits the meeting table before a fan posts it to the forums · Consilience