Skip to content

Worldbuilding Ingest Workflow

The codified process for ingesting / intaking a batch of new world information into the wiki. Triggered when the user uses the words "ingest" or "intake" in a worldbuilding context (this is also referenced from the project CLAUDE.md).

Principles

  1. Stage raw, then integrate. New material lands verbatim in the staging surface (_Worldbuilding_Intake.md) first. Capture before interpreting. Integrate into canonical docs in deliberate passes, not all at once.
  2. New information overrides existing canon. When new info contradicts established canon, the new info wins — but every override is recorded in the Changelog (what changed, old → new, affected docs, ripples).
  3. No silent ambiguity. Anything unclear is either directly resolved (with the choice noted) or flagged as an entry in Open_Questions.md. Nothing ambiguous is left unaddressed.

Steps

  1. Capture — paste/collect the raw material in the staging doc's Raw intake section, unedited.
  2. Triage — fill the staging doc's Triage & integration tracker: for each item, note a summary, the target canonical doc(s), whether it's additive or a retcon, and a status.
  3. Integrate — distribute each item into the canonical docs (Cosmology, Factions, Locations, Devices, Story, WorldbuildingSynthesis, Characters + characters/*, Society, etc.), rewriting raw notes into the wiki's register and normalizing established spellings (e.g. Vanarite, Chiranjeevi).
  4. Log retcons — record every override in the Changelog.
  5. Resolve or flag ambiguities — address directly (noting the call) or add to Open_Questions.md. Mark any questions the batch resolves as resolved.
  6. Update trackers — keep the staging tracker statuses current; when a batch is fully integrated, fold a summary into Worldbuilding_TODO.md → Recently completed and trim/remove the staging content.

Mechanics

  • Work happens on a dedicated branch with its own PR (confirm base/stacking with the user).
  • The staging doc and this workflow doc are kept out of the mkdocs nav (working/process surfaces, not published lore).
  • The Changelog is a durable record (it stays in the wiki); the staging doc's retcon log is transient scratch that feeds it.