# Questie import provenance QuestieDB's initial data and schema came from [Questie/Questie](https://github.com/Questie/Questie). The final recorded migration reference, previously stored in `QUESTIE_COMMIT`, was: **[`454b9d072965ee8f1a881429260fcf1fac8d60f7`](https://github.com/Questie/Questie/tree/454b9d072965ee8f1a881429260fcf1fac8d60f7)** (September 15, 2026, "Bump version to v11.38.0"). This is historical provenance, not a build input or a pin to advance. Imports and adaptations happened over multiple commits; it does not mean every file was first imported at this revision or remains byte-identical to it. QuestieDB now maintains these sources directly. ## Source origins Paths in the right column refer to the Questie repository at the reference above. | QuestieDB source | Origin | | --- | --- | | `src/meta/questMeta.lua` | `questKeys` and `questCompilerTypes` in `Database/questDB.lua` | | `src/meta/npcMeta.lua` | `npcKeys` and `npcCompilerTypes` in `Database/npcDB.lua` | | `src/meta/itemMeta.lua` | `itemKeys` and `itemCompilerTypes` in `Database/itemDB.lua` | | `src/meta/objectMeta.lua` | `objectKeys` and `objectCompilerTypes` in `Database/objectDB.lua` | | `data//` | Raw entity tables in `Database//` | | `src/corrections//` | Providers in `Database/Corrections/`, with consumer-owned behavior excluded | | `src/corrections/manifest.lua` | Provider inventory and Static/Dynamic classifications declared in the retired correction import tool | | `src/corrections/enum/` | Constants extracted from entity schema modules, `Database/QuestieDB.lua`, `Database/Constants.lua`, zone IDs, professions, phasing, and drop-table modules | | `l10n/` | Entity lookups and overrides in `Localization/lookups/` | | `support/` | Zone data, quest XP, drop tables, and faction templates from `Database/` | | `src/derived/RamerDouglasPeucker.lua` | `Modules/Libs/RamerDouglasPeucker.lua` | The schema tables were initially generated by `lua generate.lua meta`. Field names and indices came from the key enums; compiler types supplied storage and normalization classifications. Each raw data file also carries a key enum, which Generation still checks against the owned schema. The materialized `compilerTypes` columns preserve the old type names for provenance and public API compatibility, not for running the old compiler. The correction inventory and constants were initially generated by `tools/questie-sync/port-corrections.lua`. Expansion-dependent constants were evaluated per expansion rather than copied from a single Classic context. ## Prototype lineage The early implementation also drew on these prototypes: - `Getters/GetterDB`: Lua literal serialization, Correction registration/load-order concepts, and the initial field-layout reference. Its intermediate `.lua-table` exports were not build inputs because they already contained corrections from a different pipeline. - `toc-database`: the explicit input configuration, chunked metadata writer, emulator-backed verification, and test organization. - `Questie-toc-pi`: an independent comparison implementation. The merge adopted validation patterns and read-contract fixes, while rejecting its corrupt artifact format. The durable decisions are in [ADR 0003](docs/adr/0003-merged-storage-and-read-contract.md); current storage amendments are in ADRs 0006, 0010, and 0011. These are source and design origins, not runtime dependencies or current workspace instructions. Correction constants were extracted from Questie itself, not copied from a prototype. ## Recovering the migration tools and evidence The [`migration-parity-complete` checkpoint](docs/adr/0014-owned-data-after-migration.md#migration-checkpoint) preserves the import tools, schema derivation, comparisons, and evidence in Git: ```sh git show migration-parity-complete:QUESTIE_COMMIT git show migration-parity-complete:generator/schema.lua git show migration-parity-complete:tools/questie-sync/port-corrections.lua ``` Current build provenance comes from the producing QuestieDB commit and artifact checksums. Keep this historical source reference when changing owned data; record new changes in Git.