Glossary

Reference. Core Holonovel terminology. Every term used across the wiki is defined here on first appearance; this page is the consolidated reference.

Core concepts

Term	Definition
Badge	A server-enforced role: Player, Game Master, Observer, or Editor. The canonical term is "badge"; "hat" is the deprecated earlier name. See also: Badges.
Builder	The AI process that reads a ruleset and the specification, then constructs a running MCP server. The spec describes what the builder must do; the builder does it.
Building a Server	Running the Convert → Build → Synthesis pipeline to produce a ruleset-specific MCP server. See also: Building a Server.
Codex	A server-level persistent library of reusable game artifacts — NPCs, characters, scenes, encounters, lore, factions, countdowns, rooms, things, equipment, spells, relationships, voice profiles, and adventures. Entries survive all Novels and can be imported into any Novel. See also: Codex.
Convergence Loop	The build verification cycle — the builder runs verification workflows, identifies defects, fixes them, and repeats up to three attempts per metric until thresholds are met.
Convert	The workflow that turns PDF, HTML, or web-scraped rulebook source into clean, structurally sound Markdown that the Build workflow can read.
Enrich	Deprecated term. See Synthesis.
Game Master (GM)	The role that runs the world — sets scenes, controls NPCs, manages combat, creates lore, and uses every tool the server provides.
Hat	Deprecated term. See Badge.
Holodeck model	The north-star architectural vision: a Star Trek holodeck program — interactive narrative where the user steps inside as a character, the cast responds with intent, and rules govern every outcome.
Holonovel	The specification document (holonovel.md) that defines how to build an MCP game server from a tabletop RPG rulebook. Also the name of the project.
Lorebook	A keyword-triggered lore collection in interchange format. Export your Novel's lore as a file; import someone else's. See also: Novels (lore export/import).
Lore entry	A single keyword-triggered fact, description, or secret stored in a Novel. Surfaces in badge briefings when trigger keywords match the scene.
MCP	Model Context Protocol — the protocol Holonovel servers use to expose tools, resources, and prompts to AI clients.
Novel	A structured, typed, validated, checksummed save file holding the party, NPCs, scenes, lore, combat state, world model, story journal, factions, secrets — an entire campaign in one file. See also: Novels.
Observer	The badge that lets the AI play both Player and Game Master while you watch. Read-only access with configurable autonomy.
Pattern Buffer	The build-time behavioral model — verifies the covered requirements translate into working tool behavior via structured test scenarios.
Player	The role that acts through the ruleset — makes skill checks, attacks, casts spells, explores. Communicates intent; the engine resolves it.
REQ	A requirement in the Holonovel specification. Each REQ is a one-paragraph contract stating what the server must do, followed by acceptance criteria.
Roster	The permanent character store. Characters saved here survive every campaign and rebuild. Novel-specific changes don't affect roster baselines.
Ruleset	A tabletop RPG rulebook — the source material that the builder reads to construct a server. For example: D&D 5e SRD v5.1; any supported rulebook.
Spec	Short for "specification." The canonical document is holonovel.md — approximately 12,778 lines.
Synthesis	The optional workflow that enriches a server with community GM advice, lore templates, and action patterns. Formerly called Enrichment. Three tiers: Ruleset Wisdom (vendor content), External Synthesis (web research), Internal Synthesis (generated from your Novel state). See also: Synthesis.
Tool	A function the MCP server exposes — dice rolls, character sheets, rules lookup, combat management, world-model navigation. The AI calls tools on your behalf when you describe what you want to do.
World model	The spatial simulation layer — rooms, exits, containers, supports, and doors maintained as a real containment graph, not prose. Conventions drawn from the Inform interactive-fiction language. See also: World and Narrative Model.

Spec notation

Notation	Meaning
REQ-NNN	A requirement number. e.g., REQ-066 defines badge switching.
spec §X.Y	A specification section. e.g., spec §5.5 covers badges and access.
T-NNN	A test identifier. e.g., T146 verifies adventure generation.
GN	A verification workflow gate. e.g., G0a runs structural validation at intake.

See also

• What Holonovel Is — the architecture explained
• Style Guide — how these pages are written
• Tools — the server's full tool catalog

Last updated: 2026-10-12.