[SPEC] Narrative Engine (Ollama Integration)

[Fortinbra]

Spec #13 — Narrative Engine (Ollama Integration)

Spec file: \docs/specs/13-narrative-engine.md\

Summary

Integrates Ollama as the AI Dungeon Master narrative backend via a clean \INarrativeEngine\ abstraction in \DungeonMaster.Core. All AI-generated content (scene descriptions, NPC dialogue, encounter narration, location descriptions, player-action responses) is a proposal subject to Human DM approval before reaching players.

Scope

• \INarrativeEngine\ interface in Core — zero Ollama/HTTP dependencies
• Five narrative methods: scene, NPC dialogue, encounter, location, player-action response
• \OllamaNarrativeEngine\ in Infrastructure — typed \OllamaClient\ wrapping \HttpClient\
• Human DM approval flow: /dm approve\ | /dm edit\ | /dm reject\ | /dm override\
• \Campaign.AutoApproveNarrative\ flag (default false)
• \NarrativeLog\ entity for full audit trail of AI proposals and Human DM decisions
• Management UI: log viewer, auto-approve toggle, model selector, test prompt panel
• Configuration: \OLLAMA_BASE_URL, \OLLAMA_MODEL, \OLLAMA_TIMEOUT_SECONDS\

Implementation agents

• Missy — prompt templates, \OllamaNarrativeEngine, context assembly
• Rory — \OllamaClient\ HTTP, DI registration, Discord /dm\ commands, API endpoints
• Clara — management UI (Blazor)
• Danny — TDD gate (writes failing tests before implementation)

Dependencies

• Spec [SPEC] EF Core Infrastructure & DbContext #11 (EF Core infrastructure)
• Spec feat: Campaign Initialization — Discord channel binding and management UI override #7 (Campaign — \AutoApproveNarrative\ flag)

[Fortinbra]

Spec #13 Narrative Engine implemented and verified by Danny. Core pure (zero HTTP/Ollama imports), Ollama integration defensive, Autopilot flag respected (8/8 infrastructure tests passing). Ready for merge.