Delve — Feature Implementation Plan

Features are ordered sequentially — each builds on the ones before it. Implement in order.

Foundation

#	Feature	Description	Key Deps
00	Project Foundation	Cargo workspace, DB, Docker, CI, SvelteKit skeleton	—
01	Authentication	Registration, login, sessions, rate limiting	00
02	Character Creation	Species, classes, backgrounds, attribute point-buy	01

#	Feature	Description	Key Deps
03	Items & Inventory	Gear templates, random bonuses, equip/unequip, salvage	02
04	Character Progression	Leveling, feats, subclasses, weapon proficiency, Paragon	02, 03
05	Skill Queue	Queue builder, conditions, validation, multiple saved queues	04
06	Combat Engine	d100 system, simulation engine, encounters, loot resolution	05, 03
07	Quests & Runs	Quest board, run lifecycle, worker resolution, rewards	06

#	Feature	Description	Key Deps
08	Crafting & Gathering	5 crafting + 4 gathering professions, idle timers	03
09	Economy & Marketplace	Auction house, mail, NPC vendors, gold sinks	03
10	Guilds & Social	Guilds, friends, parties, raid lobbies	02, 09
11	PVP System	Arena, matchmaking, stat normalization, ELO, seasons	06, 05
12	Factions & Reputation	7 factions, rep tiers, conflict pairs, vendors	07

#	Feature	Description	Key Deps
13	Notifications	Polling notifications, push (FCM/APNs), preferences	00, 01
14	Dailies, Weeklies & Seasons	Daily bounties, weekly challenges, seasonal events	07, 04
15	Achievements & Collections	Achievements, bestiary, leaderboards, titles	07+
16	Monetization	Patron subscription, purchases, Stripe integration	01, 07, 08
17	Gear Enhancement & Reforging	+1 to +5 upgrades, re-roll random bonuses	03, 08

#	Feature	Description	Key Deps
18	Mobile Wrapping	Capacitor iOS/Android, push, deep links, app store	13, all UI

Features 00-07 constitute the MVP — a playable game loop. Prioritize these.
Features 08-12 add depth. Can be built in parallel by multiple contributors.
Features 13-17 are engagement/monetization layers. Feature 13 (notifications) should be wired in early even if other engagement features come later.
Feature 18 (mobile) can begin as soon as the client UI is stable, but app store submission should wait until the core loop is solid.
Each feature file lists its own technical tasks and tests. Tasks within a feature are ordered but can sometimes be parallelized where noted.
Data-Driven Architecture — READ THIS FIRST. All game content (species, classes, items, conditions, etc.) is defined in TOML data files and referenced by string ID. No Rust enums for game content. No Postgres enums. Adding new content = add a TOML file, restart server.