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

12
docs/README.md Normal file
View File

@@ -0,0 +1,12 @@
# /docs — cross-cutting docs
Anything affecting **both** client and api, plus planning and roadmap. Side-specific docs live in [`/api/docs`](../api/docs) and [`/client/docs`](../client/docs).
Put here:
- [`roadmap.md`](roadmap.md) — phases, POC scope, what's next
- [`adr/`](adr/) — Architecture Decision Records
- Shared contracts — canon log schema, tag syntax, retry policy (§11, §12)
- Anything spanning the HTTP boundary
The charter itself — [`CLAUDE.md`](../CLAUDE.md) — stays at the repo root. It is the source of truth; these docs elaborate, they do not override it.

15
docs/adr/README.md Normal file
View File

@@ -0,0 +1,15 @@
# Architecture Decision Records
One file per decision: `NNNN-short-title.md`. Record the context, the decision, and the consequences. When a decision conflicts with [`CLAUDE.md`](../../CLAUDE.md), change the charter first (charter §18).
## Index
- _none yet_
<!-- Template:
## NNNN — Title
- **Status:** proposed | accepted | superseded by NNNN
- **Context:** what forced the decision
- **Decision:** what we chose
- **Consequences:** what this makes easy / hard
-->

34
docs/roadmap.md Normal file
View File

@@ -0,0 +1,34 @@
# Roadmap
Source of truth for scope is [`CLAUDE.md`](../CLAUDE.md). This tracks sequencing.
## POC — the one question (charter §17)
> **Does bounded AI dialogue feel alive, or does it feel like a chatbot in a costume?**
Test that before building anything else. ~30 minutes of play.
### POC scope
- One town, **two NPCs** with authored knowledge lists
- One dungeon: **three fights, one boss**
- **Two companions:** Cadwyn, Brannoc
- **Three playable classes:** Sellsword, Assassin, Priest
- Luck fully wired: generation, drift, one shrine, one cursed item
- Full proxy, full role split, full canon log
- Authored fallback text for every AI surface
### Out of scope (charter §17)
AI-generated story skeletons · multiplayer (never) · mobile · credits/payments/auth · companions leaving · positional combat · more than three classes.
## Sequencing — TBD
<!-- Fill in as phases are planned. Suggested spine:
1. Proxy skeleton + role endpoints + Ollama routing + logging
2. Canon log + one Narrator scene end-to-end (proves the loop)
3. One bounded NPC conversation (proves §6 — the core experiment)
4. Luck + Improviser + one shrine + one cursed item
5. Combat (deterministic, seeded) + the dungeon
6. Banter + humiliation log (proves the comedy loop)
-->