first commit

This commit is contained in:
2026-07-09 11:17:54 -05:00
commit d54599e27d
23 changed files with 894 additions and 0 deletions

15
content/README.md Normal file
View File

@@ -0,0 +1,15 @@
# /content — authored game data
Cross-cutting authored writing. Consumed by **both** sides: the client ships fallback text and quest/story data; the api reads NPC knowledge lists to build prompts. That shared ownership is why it sits at the repo root, not inside either folder.
```
/quests Story skeletons and quest definitions (authored, not AI-generated — §17)
/npcs Per-NPC knowledge lists — the entire content an NPC can draw on (§6)
/fallback Authored degraded-DM text for every AI surface (§13)
```
## Authoring notes
- **NPC knowledge lists are the whole design** (§6). They are the only thing stopping the blacksmith from revealing the twist. Real authoring work — budget for it.
- **Fallback text is content, not error handling** (§13). Written in the DM's voice, lives beside the rest of the writing. Every AI-dependent surface needs one before it ships.
- Story skeletons are authored for now. AI-generated skeletons are v2, out of POC scope (§17).

View File

@@ -0,0 +1,7 @@
# /content/fallback
Authored degraded-DM text (charter §13). When the API is down, the player sees a degraded DM — **not an error**. The DM has a voice; a degraded DM still has that voice.
> The chamber is cold. Something waits in the dark.
Written as content, not error handling. Every AI-dependent surface needs a fallback before it ships. No exceptions.

7
content/npcs/README.md Normal file
View File

@@ -0,0 +1,7 @@
# /content/npcs
Per-NPC knowledge lists — an explicit list of what each NPC knows (charter §6). This is the *entire content* the NPC has to draw on, injected as `knowledge: [...]`. Not a prompt suggestion — the whole design.
POC scope (§17): **two NPCs** with authored knowledge lists.
Companions (Cadwyn, Brannoc) are voiced too but carry more (approval, humiliation log) — see charter §9.

5
content/quests/README.md Normal file
View File

@@ -0,0 +1,5 @@
# /content/quests
Authored story skeletons and quest definitions. The *skeleton* is authored; the *prose* is generated (charter §1).
POC scope (§17): one town, one dungeon (three fights, one boss). AI-generated story skeletons are v2 — out of scope.