Complete use case catalog organized by functional category. Now split into digestible files by epic.
For product vision, objectives, and epic definitions, see
SYSTEM.md.
MONITOR is a narrative intelligence system that operates in three modes:
| Mode | Description |
|---|---|
| World Architect | Build and maintain fictional worlds from structured/unstructured sources |
| Autonomous GM | Run full solo RPG experiences with turn-by-turn narration |
| GM Assistant | Support human-led campaigns by recording, tracking, and analyzing |
See SYSTEM.md for core objectives (O1-O5) and epics (EPIC 0-9).
Note: The CLI examples in this file describe the intended user-facing workflow surface. The currently wired command set in the repo may be smaller;
packages/cli/src/monitor_cli/main.pyis the implementation source of truth for what is live today.Implementation reality (April 2026): the live play surface is the web chat API in
packages/ui/backend/src/monitor_ui/routers/chat.py, which bootstraps sessions and dispatches intoSceneLoop/WorldBuildingLoop. Historical implementation notes that mention anOrchestratorshould be read as session bootstrap + LangGraph loops, not as a monolithic agent class.monitor playremains the target CLI UX;monitor playtestis the current CLI path for end-to-end autonomous-GM validation.
| Category | Code Range | Description | File |
|---|---|---|---|
| DATA LAYER | DL-1 to DL-26 |
Canonical data access and MCP interfaces | epic-0-data-layer.md |
| PLAY | P-1 to P-20 |
Core gameplay loop — narration, scenes, actions | epic-1-play.md |
| MANAGE | M-1 to M-35 |
World administration — CRUD for all entities | epic-2-manage.md |
| QUERY | Q-1 to Q-11 |
Canon exploration — search, browse, ask | epic-3-query.md |
| INGEST | I-1 to I-13 |
Knowledge import — documents, extraction, curation, synthesis | epic-4-ingest.md |
| SYSTEM | SYS-1 to SYS-12 |
App lifecycle, config, session | epic-5-system.md |
| CO-PILOT | CF-1 to CF-8 |
Human GM assistant features | epic-6-co-pilot.md |
| STORY | ST-1 to ST-8 |
Planning & meta-narrative tools | epic-7-story.md |
| RULES | RS-1 to RS-7 |
Game system definition — stats, skills, mechanics | epic-8-rules.md |
| PACKS | MP-1 to MP-9 |
Multiverse Packs — compose, apply, share worlds | epic-10-packs.md |
| DOCS | DOC-1 |
Documentation publishing & governance | epic-9-docs.md |
The catalog evolves over time; see the rollout plan for the best quick snapshot of current phase planning.
- Every use case implementation must add or update unit tests that cover success and failure paths.
- End-to-end or integration tests should exercise the full flow for cross-layer interactions (e.g., CLI → agents → data-layer) where applicable.
- Pull requests that change code without touching tests should be rejected by automation (see
scripts/require_tests_for_code_changes.pyand CI gate). - Each change must reference at least one use-case ID (DL-, P-, M-, Q-, I-, SYS-, CF-, ST-, RS-, DOC-) in commits/PR body; CI enforces this.
| Epic | Use Cases | File |
|---|---|---|
| Epic 0 — Data Layer | DL-1 to DL-14 | epic-0-data-layer.md |
| Epic 1 — Play | P-1 to P-21 | epic-1-play.md |
| Epic 2 — Manage | M-1 to M-35 | epic-2-manage.md |
| Epic 3 — Query | Q-1 to Q-11 | epic-3-query.md |
| Epic 4 — Ingest | I-1 to I-13 | epic-4-ingest.md |
| Epic 5 — System | SYS-1 to SYS-12 | epic-5-system.md |
| Epic 6 — Co-Pilot | CF-1 to CF-8 | epic-6-co-pilot.md |
| Epic 7 — Story | ST-1 to ST-8 | epic-7-story.md |
| Epic 8 — Rules | RS-1 to RS-8 | epic-8-rules.md |
| Epic 9 — Docs | DOC-1 | epic-9-docs.md |
| Epic 10 — Packs | MP-1 to MP-9 | epic-10-packs.md |
- Data Layer Details — DL-focused companion with inputs/behavior/outputs
- Rollout Plan — MVP, phases, and implementation status