Architecture
Data plugins own disk writes. Display plugins read through accessors. The client writes SavedVariables; those files leave the machine, land in the warehouses, and AI reads them for theorycrafting.
System
High level — two paths off the same files. Top: files ingested straight to the warehouse. Bottom: a resident service exposes the same files through an API, which reads and writes the same database.
In the client
The client stack is three layers. Nothing skips a layer; nothing writes upward. Hover a display plugin to trace what it requires.
Display plugins
14 · render only · own no suite dataSavedVariables
Disk write on logout or /reload only. One DB per data plugin, account-wide or per-character.
DMK core
lib layer · the one root addonConfig (DMKCoreDB), suite profiles — settings plus window layouts, per-character active profile — and the UI, window-manager, and form libraries every plugin builds from. Plugins publish modules through the shared DMK namespace.
One exception at the edge: Questie, the single third-party runtime source — a read-only bridge in DMK_Map, toggle-gated, native API fallback when absent.
Off the client
The export pipeline. The addon never phones home — the files it writes are picked up from disk.
SavedVariables
WTF\Account\<Account>\… files land on logout or /reload. Full paths on Documentation.
Armory + AH ingest
Armory ingest reads the CharData, CharLogs, and RealtimeData files. wow-ah-gen ingests DMKAHDB and clears it after warehouse commit — AHSync never reads its own DB back.
My databases
Character snapshots, activity and gold/xp series, combat events, and AH scans committed as queryable history.
Web + AI
wow-dmk-web is this site. AI reads the warehouse for theorycrafting.
Round trip back into the game: generated DB2 exports (spell data for DamageSimulation; AHCatalog, AHSuffixes, AHLookups for AHSearch) ship inside the addon as static data.
AI theorycrafting
What the models get and what comes back. Placeholder wording — to be replaced with the real pipeline description.
Character snapshots (gear, stats, talents, professions), combat event history and fight breakdowns, gold/xp series, and current AH pricing per item and suffix.
Placeholder — describe what actually runs: models, prompts or jobs, how often, and what questions they answer against the warehouse.
Placeholder — e.g. gear and loadout evaluation against real prices, spell-rank and rotation analysis from logged fights, upgrade paths per character.