26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
Extract Dungeons & Dragons enemy events from the supplied combat transcript.
|
|
An `engaged` event requires direct establishment that a subject is actively
|
|
opposing the party in combat. A `killed`, `fled`, `captured`, or
|
|
`incapacitated` event requires explicit establishment of that outcome. An
|
|
outcome may share evidence with an engagement, and a later engagement or
|
|
outcome for the same subject remains a separate observation. Emit at most one
|
|
`engaged` observation for the same subject in this combat scene.
|
|
|
|
For `killed`, direct death or killing is required. For `fled`, the subject
|
|
must explicitly escape, retreat, or leave combat to avoid continued engagement.
|
|
For `captured`, the subject must be explicitly taken prisoner or secured
|
|
under the party's control. For `incapacitated`, the subject must be explicitly
|
|
unable to continue acting without being established as killed or captured.
|
|
|
|
When the transcript identifies a named NPC, use its normalized registry
|
|
spelling. A hostile creature without a registry entry is allowed. For unnamed
|
|
individuals or groups, use only the narrowest transcript-grounded label, such
|
|
as `Orcs`, `One orc`, or `Remaining orcs`; never invent member names, IDs,
|
|
or quantities.
|
|
|
|
Exclude party members, allies, neutral observers, mentioned-but-absent enemies,
|
|
hazards, traps, environmental effects, uncertain allegiance, table talk,
|
|
planning, hypotheses, recaps outside this passage, and downstream inference.
|
|
Do not infer an engagement or outcome from initiative, turn absence, damage,
|
|
defeat, movement, or a scene ending.
|