Overview
Codex systems fail when they are developer wikis. The entry on dragons reads: "Dragons are large reptilian creatures with wings and fire breath. They are solitary and territorial. They hoard treasure. They are vulnerable to weapons enchanted with coherence-channeling runes." This is an encyclopedia article written by a developer who knows everything. It has no perspective, no voice, no gaps in knowledge, and no reason to exist in the world — who wrote this, and how do they know all of it? The codex is a reference document, not a world artifact.
The Codex Entry System prompt builds lore encyclopedias with three properties: (1) authored perspective — every entry is written by a specific in-universe author (a scholar, a soldier, a merchant, a prisoner) whose knowledge, biases, and gaps shape what the entry contains and what it omits, (2) unlock gating — entries are unlocked by specific player actions (discovering a location, defeating an enemy, finding a document, completing a quest), and the unlock condition is thematically linked to the entry's content (the entry on dragon anatomy is unlocked by finding a dragon skeleton, not by killing 10 goblins), and (3) cross-reference graph — entries reference each other, forming a navigable knowledge graph where following references leads the player to related entries they have not yet discovered, creating a self-directing exploration loop.
What you get: - Codex entry type definitions (scholarly, military, merchant, prisoner, divine) - Author template with perspective, bias, and knowledge gaps - Unlock gate specifications with thematic linkage - Cross-reference graph structure - Entry writing style guide per author type - Codex completion tracking and discovery metrics
Built for: narrative designers, lore writers, and UI designers who need codex systems that players actually read — not codex systems that players ignore because they read like Wikipedia.