Lore Vault — Map of Content

The lore for an asynchronous autobattler set in a fictional dark-medieval France. Start here.

For writing conventions and consistency rules, see CLAUDE. For unresolved questions and gaps, see plot_holes.

---

World

• wisteria — the MacGuffin: 25-year invasive-species crisis, origin, spread, ambient detail
• global_story — how aggregate player action drives the world forward
• geography — the map: Provence-equivalent, the Auronne, the Suaire, the Sère, the Gulf, Le Cloître
• metallurgy — the iron-and-rune economy: mines, the dead Grand-Fourneau, the satellite furnaces, charcoal, faction tension

Zones

• core — abandoned interior, environmental threat
• frontier — lawless ring, PvP threat
• civilised_fringe — fragile institutions, political threat

---

Factions

• guilds — trade and craft, information networks, stake in the future
• lords — fragmenting feudal authority
• church — fractured between institutional and reform positions
• marginal — heterodox and unaffiliated groups; a category, not a faction

---

Systems

• runes — pre-industrial inscribed-symbol effects; the build-complexity engine
• nomenclature — item naming conventions: runes, weapons, registers by manufacturer, Hanseatic gradient
• archivists — the player's persistent role; dispatch beats, pin-map, the office
• recruiters — how runs begin in-world; the courier chain that delivers contracts to villages
• journey — the hex grid, the daily clock, terrain cost, sleep, fog of war
• pvp — bandit paranoia, asynchronous encounter framing, defeat consequences
• economy — food and runes as currency, food as fuel, refugee merchants
• squad — three lives, three people; the run's unified attrition currency

---

Quests

• example_run — a worked example of a baseline guild logistics run; reference for tone, density, and pacing
• tile_encounters — index of reusable encounter templates per hex

---

Meta

• tasks — open work items, active and parked
• client_todo — implementation checklist for the game client, derived from the full vault
• ameliorations — critical design concerns: what the client todo implies is weak or missing
• what_claude_would_do — external design opinion; not canon, a second perspective to argue with
• plot_holes — known unknowns, open questions, deferred decisions
• resolved — archive of resolved questions, with pointers to canonical files
• diegetic_palette — cross-cutting reference for sound, text-as-object, visual, economic, and UI delivery channels
• roadmap — planned future content (alchemists, variants, regions)
• run_design_open — minor run-rundown framings to write when the mechanic ships

---

Folder Layout

/
├── CLAUDE.md            # writing rules, tone, conventions
├── README.md            # this file
├── _meta/               # vault management, not in-world
├── world/               # the setting itself
│   └── zones/
├── factions/            # the four faction archetypes
├── systems/             # mechanical systems with diegetic framing
└── quests/              # worked example runs and quest archetypes

A characters/ folder will be added when content exists.