Harden D&D scene description extraction
This commit is contained in:
@@ -1,9 +1,44 @@
|
||||
Choose exactly one kind: combat, narrative, recap, or meta. When a chunk is
|
||||
mixed, use this precedence: combat, then recap, then meta, then narrative.
|
||||
Choose exactly one kind:
|
||||
|
||||
The title should identify the central event or subject. The summary should
|
||||
describe only what the accepted chunk establishes. Campaign references may
|
||||
disambiguate names but never add events or lore.
|
||||
- combat: active combat materially organizes the scene, including
|
||||
initiative-like exchanges or sustained hostile action. Planning a fight or
|
||||
discussing a completed fight is not combat by itself.
|
||||
- narrative: current-session in-world play that is not principally active
|
||||
combat, a prior-session recap, or sustained out-of-character session
|
||||
discussion. This includes exploration, travel, dialogue, investigation,
|
||||
in-character planning, and aftermath.
|
||||
- recap: the scene's organizing purpose is to recount events from a previous
|
||||
session for the table. An in-world character recounting history during
|
||||
current play remains narrative.
|
||||
- meta: the scene's organizing purpose is sustained out-of-character
|
||||
discussion about the game or session rather than advancing current in-world
|
||||
play.
|
||||
|
||||
Narrative is the default for actual current-session gameplay that does not meet
|
||||
another definition. When the accepted chunk is mixed:
|
||||
|
||||
1. use combat when active combat is a substantive central activity, even with
|
||||
brief setup, rules clarification, or immediate aftermath;
|
||||
2. otherwise use recap when recounting a previous session is the chunk's
|
||||
primary table purpose;
|
||||
3. otherwise use meta when sustained out-of-character session discussion is
|
||||
primary and in-world progression is no more than incidental; and
|
||||
4. use narrative for all remaining current-session in-world play.
|
||||
|
||||
Brief table talk, dice resolution, rules clarification, jokes, or
|
||||
administrative comments do not make a gameplay scene meta. A short recollection
|
||||
used to orient current action does not make a scene recap.
|
||||
|
||||
The title must be a short, distinguishing phrase rather than a sentence,
|
||||
chapter number, or generic label such as "Scene." It may use names and places
|
||||
established by the transcript or disambiguated by campaign references, but it
|
||||
must not invent a proper noun.
|
||||
|
||||
The summary must briefly state the main activity and material transition or
|
||||
outcome established within the accepted chunk. Do not add analysis, inferred
|
||||
motives, hidden state, future consequences, relationship claims, or facts from
|
||||
outside the chunk. Campaign references may disambiguate names but never add
|
||||
events or lore.
|
||||
|
||||
Do not return identifiers, source identifiers, source ranges, unit identifiers,
|
||||
participants, confidence, or any fields besides kind, title, and summary.
|
||||
|
||||
Reference in New Issue
Block a user