28 lines
841 B
Markdown
28 lines
841 B
Markdown
# ADR 006 — Genre-Agnostic Core
|
|
|
|
**Status:** Accepted
|
|
|
|
## Decision
|
|
|
|
Core data structures and workflows will not hard-code fantasy or science-fiction concepts.
|
|
|
|
## Context
|
|
|
|
The same application should support swords-and-sorcery, hard science fiction, space opera, mystery, and other interactive-fiction genres.
|
|
|
|
## Alternatives Considered
|
|
|
|
- fantasy-specific schema,
|
|
- separate engine per genre,
|
|
- generic story engine with campaign profiles.
|
|
|
|
## Reason
|
|
|
|
The underlying requirements—characters, locations, relationships, history, facts, scenes, memory, and branches—are common across genres.
|
|
|
|
## Consequences
|
|
|
|
- genre-specific rules belong in profiles/configuration/canon,
|
|
- avoid schema columns such as `spell`, `sword`, `spaceship`, etc.,
|
|
- use generic concepts such as entities, items, vehicles, locations, organizations, and facts.
|